Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
      • Learn more about Agile
        • Agile Webspace
        • Everything Agile
          • The Agile Manifesto
          • Best Practices
          • Retro Recipes
        • Methodologies
          • The Scrum Framework
          • Kanban
          • Extreme Programming
        • Roles
          • The Product Owner
          • The Agile Coach
          • The Quality & UX Coach (QX)
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Pogram
    • DataMiner DevOps Support
    • Feature Suggestions
  • Swag Shop
  • Downloads
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Solutions
    • Deal Registration
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

How to correlate and group two alarms with an AND condition across different protocols?

Solved502 views7 days agoCorrelation rule
1
A B M Sidddique [DevOps Advocate]371 3rd March 2025 0 Comments

Hi everyone,

I’m trying to set up a correlation rule that triggers only when two specific alarms (from two different elements using different protocols) occur at the same time. Here’s a simplified version of my filter logic:

  1. Condition A: Parameter description (by protocol) = InnotecISG/Production/10.0.2 Wind Speed MMB AND Severity != Normal
  2. Condition B: Is Value matches wildcard expression *RSSI*

I expected to use an AND filter so that the correlation only fires when both conditions happen together. However, when I set it up this way, the correlation doesn’t seem to trigger at all. If I change it to OR, it does trigger—but I get false positives whenever only one condition is met.

I’m also having trouble grouping these two alarms, because they don’t share a common property. The only way that seemed possible was to match on the element name via a wildcard expression, but that doesn’t appear to be supported (or doesn’t work) in my environment. We’ve tested all available grouping methods, and so far the one using “keypoint” seems to work best—but it still doesn’t fully address the AND correlation issue.

My goal is to ensure that these alarms are correlated only when both conditions occur simultaneously (or within a short time window) across these two different elements/protocols. Has anyone dealt with a similar scenario? How did you configure your filters or correlation rule so that both conditions had to be true without missing events or generating false positives?

Any suggestions , or examples would be greatly appreciated!

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 7 days ago

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
0
Wouter Demuynck [SLC] [DevOps Advocate]6.02K Posted 10th March 2025 0 Comments

Hi,

Be aware that the filter in the "alarm filter" section always gets applied to one alarm event/tree at a time. It is used to select which alarm events will be considered for the correlation rule and cannot be used to define that different types of alarms need to be active together.

All alarm events that each match the alarm filter will be tracked for this rule. So the alarm filter is for collecting alarm trees only.

To define when to fire actual actions, the "rule condition" section comes into play. Typically it executes actions as soon as at least one alarm is being tracked by the rule, but conditions can be added to define when actions may be executed.

In your case, what would work is the following:

  • Alarm filter:
    • "Wind speed" alarm
    • OR
    • "RSSI alarm"
  • Condition:
    • Filter condition "Wind Speed"
    • AND
    • Filter condition "RSSI alarm"

This will cause the correlation rule to track all active "Wind Speed" and active "RSSI alarm" alarms in a bucket and then run correlation actions when there is at least one "Wind Speed" alarm in the bucket and at least one RSSI alarm.

Hope this helps

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 7 days ago
You are viewing 1 out of 2 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin