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
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • 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)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Clearing alarms in Generic Syslog Receiver Element

Solved1.23K views26th October 2022alarm syslog
0
André Kaiser [DevOps Advocate]532 18th July 2022 0 Comments

Dear Dojo Community,

we have a couple of Generic Syslog Receiver elements set up in our DMS. Alarms are being triggered on these elements based on specific alarm configurations. To clear an alarm in a Syslog element typically another alarm configuration is used to set it back to alarm state "normal".

There are also a couple of Syslog devices, that send only a Syslog message in case there is an issue, e.g. a PSU failure. When the device state is normal again no “clearing” Syslog message is sent by these devices. Thus the current alarm state of the related alarm remains in the defined severity/state. Masking the alarm is not an option as this would hide a prevent the element from going into alarm state for new incoming alarm syslog messages for this alarm configuration.

Is there an option to manually clear this alarm or is it inevitable, that the source sends a clearing syslog to set the state back to normal again? The "manual override state" in the alarms table has no effect on the current alarm state of the element.

André Kaiser [DevOps Advocate] Selected answer as best 26th October 2022

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
0
Jeeva Suria Rajah [SLC] [DevOps Advocate]1.60K Posted 19th July 2022 1 Comment

Hi Andre,

This is just a rough idea, but if you have an Automation and Correlation Module, you can use this to analyse and process the alarms from the Syslogs.

When an alarm is normalised, you can configure the device to send an Informational Syslog message to DataMiner, and the Correlation can "catch" the message every time it is received. Based on this, the Correlation can be configured to trigger an Automation Script.

In the Automation Script, the newly received Syslog message can be processed where the warning message can be compared with the previous Syslog. The script will set the table to change the severity, which can clear the alarm in DataMiner.

André Kaiser [DevOps Advocate] Selected answer as best 26th October 2022
André Kaiser [DevOps Advocate] commented 28th July 2022

Hi Jeeva,
many thanks for your feedback. The same would be possible with the Alarm Config Table. The issue is simply, that currently we do not get a Syslog from the Device, when an alarm condition went back to normal again. So we are missing the trigger.

A “Manual Aknowledge” of an active alarm would be ideal in such a situation.

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