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
    • 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
      • 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)
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Program
    • DataMiner DevOps Support
    • Feature Suggestions
  • Downloads
  • Swag Shop
  • PARTNERS
    • Business Partners
    • Technology Partners
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

Correlation – Trigger on cumulative alarm durations within a sliding time window

101 views17 hours agoCorrelation correlation engine Correlation rule trigger
5
Conan Van Hove [SLC] [DevOps Advocate]843 2 days ago 0 Comments

Hi, currently the correlation module does not allow to configure a rule which would collect (in a sliding window) the cumulative durations of a certain alarm which appears/disappears successively (so an alarm is raised and is active for some time and then is cleared, but then a bit later it appears again and so on) and if the cumulative time during that sliding window (for example half an hour) exceeds a specified time (for example 5 minutes) then the condition is met and an action can be performed (for example raise the alarm severity).

A typical use case would be to monitor the cumulative down-time of an interface and only if it remains down for a specified cumulative time during a certain period this is considered as a critical event.

Is this a feature which could be considered to be implemented on the Correlation engine?

Or would there be other ways to configure this with the existing functionality (so without for example having to make changes on a connector)?

Pieter Van Compernolle [SLC] [DevOps Enabler] Answered question 17 hours ago

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
1
Pieter Van Compernolle [SLC] [DevOps Enabler]3.79K Posted 17 hours ago 0 Comments

Hi Conan,

It feels like you want to monitor 'the availability' of your interfaces. Maybe there are more parameters that can impact the availability and you want to create a service for it? In that case you can create SLA's to monitor the availability via outage configuration.

Pieter Van Compernolle [SLC] [DevOps Enabler] Answered question 17 hours ago
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

© 2026 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