Creating different rules with different signals under the same detector.

Available Languages

Updated:October 1, 2026
Document ID:SPLK054752

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 Application Performance Monitoring Splunk Infrastructure Monitoring Splunk Synthetic Monitoring

Description

How can multiple rules be created under the same detector using different SignalFlow programs? It has been observed that when two rules are created on the same Plot A, modifying one rule causes the SignalFlow for the other rule to change as well.


Investigation

Please note that when creating two rules under the same detector, each rule must be configured to alert on a different plot or signal.


Resolution

Follow the steps below to create multiple rules within the same detector.

Example: Two rules, "WorkflowNamePlaceOrder" and "WorkflowNameAddToCart," are created under the same detector, "Test_Detector." The workflow.name value is different for each rule.

Create a detector and configure two rules.

First rule :

WorkflowNamePlaceOrder
- Create the first signal
- Configure the rule to alert on Plot A

Second rule: 

WorkflowNameAddToCart
- Create the second signal
- Configure the rule to alert on Plot B

Ensure that each rule under the detector is configured to alert on a different plot. This allows multiple rules with different SignalFlow logic to be created within the same detector.


DetectorsAndAlerts

Revision History

Revision Publish Date Comments
1.0
01-Oct-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco