Data Actions Performance Summary view
Requires the following permission:
- Integrations > Action > View or Bridge > Actions > View
The Data Actions Performance Summary view displays current and historical metrics and data about data actions. For more information, see About the data actions integrations.
To | Do this |
---|---|
Display the view | Click Performance > Workspace > Other > Data Actions Performance. |
Filter by category |
On the upper left, click the Filter user(s) search icon . Enter a category name. The suggested names appear in the search results. |
Customize the view using interaction filters | On the upper right, click the Toggle filters panel icon ![]() |
Modify the columns that appear in the view | See show, hide, and rearrange columns below. |
Refresh the view | To display the most current data, click Refresh . |
Save the view with your filter and column settings | Click Save . |
Export the data in the view | Click Export . |
View statistics for a specific data action
To see data for a specific data action, in the Action category row, click . The data actions associated with the action category appear under the category row. For more information about a specific data action, see Data Actions Performance Detail view.
Customize the view
To show only certain data, customize the Data actions performance summary view using any combination of filters.
Filter | Description |
---|---|
Response status |
A list of observed HTTP status codes that are returned in response to data action execution. The list varies depending on what is observed within the dataset. |
More information about making these customizations is available in the following sections.
Use the date filter to customize analytics views.
Use presets to filter metrics by date, or configure a custom date range. When filtering metrics for this view, select any custom date range up to 6 weeks.
To use a preset to filter metrics, complete the following steps:
- Click the date to display the date filter.
- In the Presets list, select a preset date option.
Date presets
Presets | Description |
---|---|
Current interval |
Shows data for the current 30-minute time period. Note: Because Detail views include Interval in the data grid, the Current interval preset is not displayed for these views. |
Today | Shows data for the time period that includes the current interval. |
Yesterday | Shows data for the previous day. |
This week | Shows data for a Sunday through Saturday time period. |
Last week | Shows data for the previous week, Sunday through Saturday. |
Previous 7 days | Shows data for the previous seven days. |
This month | Shows data for the current month, with no extra days. |
This month by week | Shows data for the current calendar month starting on Sunday and ending on Saturday, including extra days if the month does not start on Sunday or end on Saturday. |
Last month | Shows data for the previous calendar month with no extra days. |
Previous 3 months | Shows data for the previous 3 months. For example, Nov 1 2022 – Jan 31 2023. |
Previous 30 days | Shows data for the previous 30 days. |
Interval |
Shows data for a 30-minute time period. Note: Because Detail views include Interval in the data grid, the Interval preset is not displayed for these views. |
Day | Shows data for a single 24-hour day. |
Week | Shows data for a Sunday through Saturday time period. |
Month | Shows data for the exact month with no extra days. If the current month is selected, you will see the data up to the current date. |
Month by Week | Shows data for a calendar month starting on Sunday and ending on Saturday, including extra days if the month does not start on Sunday or end on Saturday. |
To use a custom date range to filter metrics, complete the following steps:
- Click the date to display the date filter.
- Select a start date and an end date on the calendar, and click the filter arrow
.
To view data for a different time period using the same date presets, click the arrows on either side of the date display.
For example, to view data for the previous day, click the Day preset, and then click the arrow on the left side of the date.
- When filtering you can select more than one media type. Click the relevant media type to select or deselect the type.
- You cannot select the voice and callback types at the same time.
- If you select voice, the callback option will be deselected, and if you select callback, the voice interaction will be deselected.
The selected media type icon is displayed above the column headers.
To show or hide topic columns, click and then search or scroll to select the columns you want to view.
To rearrange topic columns, click a column header and drag it.
To reset a view to default column settings, click Reset view to defaults .
You can select up to 20 topic columns.
For more information about the metrics shown in the columns, see the Available Columns section in this article.
Data in the view can be displayed in a chart. To view the chart, click the Show/Hide chart icon .
Available columns
Your customizations determine the metric columns that the view shows.
These columns show current data when you use the date filter to show the current date. If you use the date filter to show a past date, then these columns display historical data.
To show or hide columns, click and then search or scroll to select the columns you want to view.
Column | Description |
---|---|
Action Category | The category configured for the action. This is typically the name of the integration that contains the action. |
Action Name | The name given to the data action. |
Executions | The number of attempts to execute this action/category. This includes successful and unsuccessful executions. |
Avg Duration | The average time, in seconds, taken to execute the action/category. |
Min Duration | The minimum time, in seconds, taken to execute the action/category. |
Max Duration | The maximum time, in seconds, taken to execute the action/category. |
Total Duration | The sum of the durations of all executions of this action/category. |
95% Duration | The 95th percentile duration for this action/category, in seconds. This means that 95% of actions completed in this amount of time. This is useful for finding actions with occasionally long execution times. |
99% Duration | The 99th percentile duration for this action/category, in seconds. This means that 99% of actions completed in this amount of time. This is useful for finding actions with occasionally long execution times. |
Errors | The total number of executions that resulted in a non-200 level HTTP result. Some errors may be expected including a 404 response when a lookup does not yield results. |
Error % | Percentage of execution attempts that resulted in any error response. |
Remote Endpoint Errors | Errors due to a non-200 level response from the remote endpoint. This could be expected behavior including a failed lookup returning a 404 response. |
Remote Endpoint Error % | Error % due to a non-200 level response from the remote endpoint. This could be expected behavior including a failed lookup returning a 404 response. |
Processing Errors | Errors due to failures in processing the action configuration. These errors indicate that the action is misconfigured or unable to handle some inputs or results from the remote web service. Test the action with test mode or contact support for additional details |
Processing Error % | Error % due to failures in processing the action configuration. A non-zero percentage indicates that the action is misconfigured or unable to handle some inputs or results from the remote web service. Test the action with test mode or contact support for additional details. |
Authentication Errors | Errors due to an authentication error. A large number of errors likely indicates that the credentials in use are invalid or have expired. |
Authentication Error % | Error % due to an authentication error. A 100% error percentage likely indicates that the credentials in use are invalid or have expired. |
Concurrency Rate Limit Errors | Errors due to too many data action executions attempted concurrently. These errors along with a high value for the 99% duration or 95% duration indicate that the remote endpoint should be investigated for slow responses. Contact support for further troubleshooting |
Concurrency Rate Limit Error % | Error % due to too many data action executions attempted concurrently. A substantial percentage along with a high value for the 99% Duration or 95% Duration indicates that the remote endpoint should be investigated for slow responses. Contact support for further troubleshooting. |
Volume Rate Limit Errors | Errors due to the per-minute data action limit being exceeded. Assuming the rate of data action executions is expected, contact support to request that the volume limit be increased. |
Volume Rate Limit Error % | Error % due to the per-minute data action limit being exceeded. Assuming the rate of data action executions is expected, contact support to request that the volume limit be increased. |
Remote Endpoint 429 Errors | Errors due to the remote endpoint returning a 429 (Rate limited) response. You may consider caching responses from that endpoint to reduce calls to the endpoint or request an increase in your rate limit from that provider. For more information, see Designing Architect flow data actions for resiliency. |
Remote Endpoint 429 Error % | Error % due to the remote endpoint returning a 429 (Rate limited) response. You may consider caching responses from that endpoint to reduce calls to the endpoint or request an increase in your rate limit from that provider. For more information, see Design and implement a data action response cache. |
Success Count | The number of executions that were successful. |
Success Rate | The percentage of executions that were successful. |
Remote Endpoint 4XX Errors | Errors due to the remote endpoint returning a 400-level HTTP status code. |
Remote Endpoint 4XX Error % | Error % due to the remote endpoint returning a 400-level HTTP status code. |
Remote 5XX Errors | Errors due to the remote endpoint returning a 500-level HTTP status code. |
Remote Endpoint 5XX Error % | Error % due to the remote endpoint returning a 500-level HTTP status code. |