The Logs section offer a window into the application's activity timeline. This log captures a series of actions, timestamps, and user details, providing a comprehensive record for users to review and understand the flow of activities. The flexibility to filter logs by date, user, model, instance, and actions ensures a targeted exploration of specific events.
This tool proves invaluable for users seeking transparency and detailed insights into the inner workings of Pyplan. Uncover the story behind your application's usage by navigating through the Logs section.
Easily explore logs with our simple filters that make it straightforward to find and understand specific log entries, helping you derive insights effortlessly.
Start Date and End Date: Tailor your log exploration by defining a specific time frame, allowing for a focused review of activities within the designated period (You can filter a maximum of 7 days).
User: Isolate and analyze activities associated with a particular user, providing insights into individual interactions and contributions within the app.
Instance: Trace the sequence of events specific to a chosen instance, unraveling a detailed narrative of activities associated with that particular application environment.
Action: Refine your analysis by selecting a specific action type, enabling a targeted investigation into particular operations performed within the app.
Model (App): Hone in on activities related to a specific model or application, offering a contextualized perspective on the logs and facilitating a comprehensive review within the chosen framework.
Upon applying filters in the logs table, a comprehensive record of activities within the data analytics app unfolds. Each row signifies a distinct action, with corresponding details encapsulated in the following columns:
Date: Displays the chronological timestamp of each log entry, providing a precise record of when the corresponding action occurred.
User: Identifies the user associated with each log entry, helping trace actions back to specific individuals.
App: Indicates the application involved in the logged action, offering insights into the context of the activity.
Action: Specifies the action taken.
Query: Provides details on the query associated with the log entry, offering transparency into the data retrieval or manipulation processes.
Body: Offers a snapshot of the content or payload associated with the log entry, providing additional context or information related to the recorded action.