Splunk Observability Synthetic Monitoring - Resolved incident on detector alerts

Available Languages

Updated:September 29, 2026
Document ID:SPLK048587

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Synthetic Monitoring Synthetic Detectors

Description

Splunk has discovered, and fixed, a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring platform.

Synthetic Detectors will be restarted to ensure that the fix is applied to all impacted detectors. In this restart, customers with Synthetic Detectors that have active alerts will receive a notification indicating the detector has stopped.

Example message contents: [‘Rule "Testing Detector Migration" in detector "Testing Detector Migration" was stopped at Mon, 17 Feb 2025 14:36:19 GMT UTC.”]

Additional alerts may also be triggered as a result of incoming data from the detector restart.

We extend our most sincere apologies for any inconvenience this may have caused you.

If you have any questions, please create a Support case on the Splunk Support Portal (select Get Started. > Create a Case > Select Support > Select Splunk Synthetic Monitoring).

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco