> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/platform/activity-monitoring.md). # Activity Monitoring The Activity tab provides comprehensive analytics and monitoring for all your workflow executions. Track performance, identify issues, and analyse usage patterns across your organisation with detailed run history, powerful filtering, and customisable saved views. > 💡 In projects using the agent-first navigation, this tab is called **Monitor**. The functionality is the same. ### Key Features * Real-time workflow execution tracking * Detailed run history with status monitoring * Advanced filtering, including metrics and session lookups * Saved views with pinning and locked filters * Customisable dashboard with stat cards and charts * User feedback collection and analysis * Run trace analysis for debugging * Export and sharing capabilities ### How to Access Activity Monitoring 1. Navigate to the main Lleverage interface 2. Click on the "Activity" tab in the navigation menu 3. The default "All Activity" view loads, showing the last 30 days of Live (production) runs 4. View your workflow runs in the activity table > 💡 The Activity tab updates in real-time as workflows execute, giving you live insights into your automation performance. ### Understanding the Activity Table #### Table Columns * **Timestamp**: When the workflow run started * **Workflow**: Name of the workflow that was executed * **User**: Who triggered or actioned the workflow * **Status**: Current state of the run * Success - Completed successfully * Failed - Encountered an error * Paused - Waiting, for example on human input * Aborted - Manually stopped * Timeout - Ran out of time * Running - Currently executing * **Type**: How the workflow was triggered * App (Form or Chat interface) * API * Schedule * Integration * Data Table * **Environment**: Live (production) or Builder (test runs from the workflow builder) * **Feedback**: User ratings and comments on the workflow execution * **Run Time**: Duration of the execution > 💡 You can filter directly from the table: column headers for status, type, environment, user, feedback, and action type include a "Filter by" option. #### Choosing What Each Row Represents Use the **Breakdown by** control in the toolbar to switch what the table shows: * **Session**: One row per session (default) * **Execution**: One row per workflow execution * **Action**: One row per individual action The **Group by** control changes the time bucketing of the charts between Day, Week, and Month. ### How to Filter Activity Data Click the **Filter** button to open the filter menu, then pick a category. Active filters appear as chips next to the button. #### Available Filters * **Date**: Last 24 hours, Last 7 days, Last 30 days (default), Since, or a custom range * **Workflow**: Select specific workflows to monitor * **Status**: Success, Failed, Paused, Aborted, Timeout, or Running * **Type**: Filter by trigger type (App, API, Schedule, Integration, Data Table) * **Users**: View runs by specific users or API keys * **Feedback**: Positive, Negative, or Any Feedback * **Action Type**: Filter by the types of actions used in the run * **Environment**: Live or Builder * **Session ID**: Paste a session ID to jump straight to a specific session * **Metrics**: Each metric configured in your project gets its own filter, with operators such as Equals, Contains, and Greater than * **Advanced**: Field-based criteria, such as Duration (ms) #### How to Apply Filters 1. Click the "Filter" button in the filter bar 2. Select a category and choose your options 3. Multiple filters can be combined for precise results 4. The table and charts update automatically as filters are applied 5. Remove a chip to clear that filter > 💡 Combine multiple filters to investigate specific issues, such as all failed API calls in the last 24 hours. Your current filters are reflected in the page URL, so you can share the link with a team member and they'll see the same view. ### How to Use Workflow Feedback #### Understanding Feedback Users can provide feedback on workflow runs to help improve automation quality: * **👍 Thumbs up**: Indicates a positive experience * **👎 Thumbs down**: Indicates issues or dissatisfaction * **💬 Comments**: Additional context about the experience #### How to Filter by Feedback 1. Click on the Feedback filter 2. Select from the available options: * **Positive**: Shows only runs with thumbs up * **Negative**: Shows only runs with thumbs down * **Any Feedback**: Shows all runs with any type of feedback 3. Combine with other filters to analyse specific feedback patterns > 💡 Use feedback filters to identify workflows that may need improvement or to highlight successful automations for replication. ### How to Use Saved Views Saved views appear as tabs at the top of the Activity page. Every project starts with a default **All Activity** view, and you can create as many additional views as you need. #### Creating a Saved View 1. Click the "+" button next to the view tabs 2. Give your view a name and an optional description 3. Choose the filters the view should apply 4. Click "Create" — the view appears as a new tab #### Understanding Locked Filters When a saved view is active, the filters that are part of the view appear as locked chips with a dashed border. They can't be removed or edited directly — hovering shows "This filter is part of the saved view". * You can still **add** filters on top of a locked filter; your additions appear as a separate, editable chip * To change the view's own filters, right-click the view tab and choose **Edit**, or make your changes and click **Update view** in the toolbar to save them into the view > ⚠️ This applies to the default "All Activity" view too: its Date and Environment filters are locked. Add your own filters on top, or create a new view for a different baseline. #### Managing Views Right-click a view tab to: * **Pin to sidebar**: Quick access from the navigation * **Edit**: Change the view's name, description, and filters * **Delete**: Remove the view (the default view can't be deleted) A view remembers more than filters: column layout, grouping, row size, charts, and dashboard layout are all saved with it. When you've changed any of these, click **Update view** to persist your changes. #### Benefits of Saved Views * Quick access to frequently used filter combinations * Consistent monitoring across team members * Foundation for setting up alerts * Time-saving for regular reporting > 💡 Create saved views for common monitoring scenarios like "Daily Failed Workflows" or "High-Volume API Calls". ### Understanding the Monitoring Dashboard The area above the table is a customisable dashboard. By default it shows four stat cards based on your current filters: * **Total Sessions**: Overall workflow sessions * **Successful**: Runs that completed successfully * **Failed**: Runs that encountered an error * **Avg Duration**: Mean execution time #### Charts The **Runs vs Errors** chart is shown by default. Use the edit (pencil) button to add more: * **Timeline**: Visualise run patterns over time * **Successful Runs** and **Failed Runs**: Track outcomes separately * **Avg Duration**: Spot performance trends * **Feedback**: Track ratings over time * **Metric charts**: One available per metric configured in your project Click a bar in any chart to focus the whole page on that time bucket — a "Focus" chip appears in the filter bar, and you can remove it to zoom back out. > 💡 Charts can also be pinned to your project dashboard, so key trends are visible as soon as you open the project. #### Customising the Layout 1. Click the edit (pencil) button in the toolbar 2. Add, move, or resize cards, charts, and the activity table 3. Click "Done editing" to finish, then "Update view" to save the layout into the current view ### How to Analyse Individual Runs #### Viewing Run Details 1. Click on any row in the activity table 2. A detailed view opens showing: * Complete input data provided by the user * Full output returned by the workflow * Execution traces for each step * Error messages if applicable * User feedback if provided #### Using Trace Analysis 1. In the run details, click on "Traces" 2. View the step-by-step execution path 3. See inputs and outputs for each action 4. Identify where failures occurred 5. Understand processing time for each step > ⚠️ Trace analysis is invaluable for debugging complex workflows and optimising performance. ### How to Export Activity Data 1. Apply your desired filters 2. Click the "Export" button in the toolbar 3. Choose "Export CSV" or "Export Excel" > 💡 Exports respect your current filters, making them perfect for reporting on exactly the runs you're looking at. ### Best Practices #### For Performance Monitoring * Regularly review average duration metrics * Investigate workflows with increasing run times * Set up saved views for performance tracking * Monitor failed run patterns for systemic issues #### For Debugging * Use trace analysis for failed runs * Use the Session ID filter to jump straight to a reported session * Compare successful vs failed runs * Look for patterns in failure times or users * Review user feedback for additional context #### For Reporting * Create saved views for standard reports * Export data as CSV or Excel for external analysis * Use charts for stakeholder updates * Track trends over custom date ranges * Include feedback analysis in quality reports #### For Continuous Improvement * Regularly analyse negative feedback * Identify workflows with low satisfaction rates * Use positive feedback to understand best practices * Act on user comments and suggestions > 💡 The Activity tab is your command centre for workflow operations. Regular monitoring helps maintain reliable automation performance and user satisfaction. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lleverage.ai/platform/activity-monitoring.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.