Test performance KPIs 🔗

KPIs measure how well your tests are performing in a variety of circumstances. There are two tabs in this view on the test details page: availability and performance KPIs. The availability tab shows when the test was up and running versus failing, and if an auto-retry run occurred.

Here are some ways you can troubleshoot issues in the performance KPI chart:

Zoom in on a range of time to isolate an issue.
Play or pause windows of time during troubleshooting to and open run results, screen captures, and charts in context with the selected data.
Automatically adjust data density adjusts for zoomed in views or summaries of larger time ranges.
VIew up to 90 days of historical data for related run results.

Performance KPI chart settings 🔗

The Performance KPIs chart offers a customizable visualization of your recent test results.

Option

Default

Description

Time

Last 8 hours

Choose the amount of time shown in the chart.

Segment by

Location

Choose whether the data points are segmented by run location or no segmentation:

- Choose No segmentation to view data points aggregated from across all locations, pages, and synthetic transactions in your test.

- Choose Location to compare performance across multiple test locations.

Locations

All locations selected

Choose the run locations you want to display on the chart.

Filter

All locations selected

If you have enabled segmentation by location, choose the run locations you want to display on the chart.

Metrics

Run duration

By default, the chart displays the Duration metric. Use the drop-down list to choose the metrics you want to view in the chart.

This page was last updated on Dec 14, 2024.

Was this topic useful?

Did you know that you can edit this page? Learn how!

Was this documentation topic helpful?

Enter your email address if you would like someone from the documentation team to reply to your question or suggestion.

Please provide your comments here. Ask a question or make a suggestion.

Comment should have a minimum of 5 characters and a maximum of 1,000 characters.

Feedback submitted, thank you! We resolve documentation feedback based on the severity of the issue reported, as well as an assessment of the potential number of customers who might be affected.

If you have a question about using Splunk software, we encourage you to check Splunk Answers or Splunk community Slack to see if similar questions have been answered, or to post your question for others to answer. If you have an active support entitlement and believe that your situation is caused by a product defect, file a support case in the Support portal https://login.splunk.com/page/sso_redirect?type=portal.

We are currently moving to a new documentation site. Expect a delay in responding to your feedback and applying any updates based on your feedback. Thank you for your patience and understanding while we work to bring you an improved documentation experience!