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 Template – Condition ‘all rows’

Solved745 views27th September 2024alarm condition alarm template
2
James Stokell [DevOps Advocate]493 17th May 2024 3 Comments

Hello dojo people,

I’ve got an issue with the alarm template conditions.

I’m trying to specify that if there is a row in a different parameter table that shows the redundancy config state as ‘true’ then it evaluates if the secondary input is ‘locked’ or not.  If the redundancy state is ‘false’ then there is no secondary input setup and so I don’t want to evaluate the input as we expect it to not be ‘locked’.

The redundancy config only has one row per element, so in order to apply this alarm template to multiple devices I used the ‘all rows’ option for the condition, but this never triggers the condition, so both inputs are always evaluated.

If I force it to ‘single row’ and put in the key that matches one element, the condition triggers and the parameter is not evaluated, just as I’d expect.

So the curve-ball here is that I apply the alarm template to the child elements of an ateme decoder which auto creates these child elements, I suspect this is where the problem may lie, as I guess the child elements are doing a filter from the parent? It could be completely unrelated though.

Attached is a screenshot of the table with the config row I want to base the condition on.  dm-filter.PNG

Thanks all!

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 27th September 2024
Alberto De Luca [DevOps Enabler] commented 20th May 2024

Child elements (DVE) or parent should not matter, as long as you use only one type of element for the alarms (either the parent or the child – normally I apply Alarm templates to DVEs)

Marieke Goethals [SLC] [DevOps Catalyst] commented 26th August 2024

Hi James,
I see that this question has been inactive for some time. Do you still need help with this? If not, could you select Steve’s answer to indicate that the question is resolved?

Marieke Goethals [SLC] [DevOps Catalyst] commented 27th September 2024

As this question has now been inactive for a long time, I will close it. If you still want more information, could you post a new question?

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
2
Steve Purcell [SLC] [DevOps Advocate]1.71K Posted 17th May 2024 0 Comments

Hi James,  I believe what you are trying to do should work, however, your key values may not match.  When I tested it seems that the All Rows uses the Primary Key not the Display Key, when using Single Row, you can decide whether Primary (gold key) or Display Key (grey key) used, then set row index accordingly:

Following are my results comparing top table to bottom table.  Note I have the Primary Key displayed by right clicking the column header and showing column. In my case, when set to ‘standby’ the value in the top table is interpreted for alarming, when bottom table is ‘active’ the corresponding row in the top table is not evaluated and greyed out.

If using the All Rows, verify that your primary keys match between the tables.

If using Single Row, verify the Display key index is entered correctly.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 27th September 2024
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