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

“Alarm history exceedes XXX alarms” notices but alarming is not active

Solved2.48K views19th October 2023alarm notice
3
Daniela Prada [SLC] [DevOps Advocate]456 31st August 2023 0 Comments

We have multiple elements running the Bridge Technologies VB Probe Series, but despite having alarming disabled for the CC Error Rate in the Service PIDs table, we're consistently getting notices indicating that the Alarm history for this parameter has exceeded 100 alarms.

The only thing I see different is that the parameter has the following configuration:

<Alarm>
   <Monitored disabledIf="7019,0">true</Monitored>
    <Normal>0</Normal>
</Alarm>

From what I understand, this condition is only applied if the alarm is enabled in the template.

What could be the cause of all these notices?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 19th October 2023

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
0
Wouter Bogaert [SLC] [DevOps Advocate]969 Posted 26th September 2023 0 Comments

Hi Daniela,

I see you have trending enabled on this parameter. Can you check if you find any suggestion events for this parameter?

Just add a new alarm tab showing the current suggestion events.

If you find suggestion events in there, you will quickly see if you have entries in there with large alarm trees for that parameter.

If you don't have any current entries, you can of course check the history around the time of the notice.

Hope this helps.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 19th October 2023
You are viewing 1 out of 1 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