Test status 🔗

Test performance KPIs
- Performance KPI chart settings

Test state and current status 🔗

You can use the play and pause buttons in the more menu (⋯) of your tests to pause or resume data collection.

The current status of a test is updated every time you load the Test Overview page in Splunk Synthetic Monitoring. The following table describes the possible status types for each test.

Current status	Description
Pending	Splunk Synthetic Monitoring is still retrieving the status of this test.
Available	The test is functioning properly. If the test is active, data is being collected at the set interval and can be viewed in the Test History page. If the test is paused, it can be unpaused and will resume collecting data.
No Data	The test isn’t currently collecting data.
Failure	The test encountered a failure.

Filter tests 🔗

You can filter by test type, key-value pairs, and more.

This image shows the filter env:prod for all tests on the Synthetic homepage..

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!