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

Will a FillArray with history set option provide an update to the alarms in the table?

Solved1.41K views25th February 2021alarms QAction table
11
Michiel Saelen [SLC] [DevOps Enabler]5.63K 24th February 2021 0 Comments

When performing a table update with the protocol.FillArray function with the history set option from a QAction, do we expect the alarm to have an update or to be marked as unread again?

If the value changes of the alarmed cell, but the alarm state remains the same, do we expect an update on the alarm?

If the value remains the same, do we expect an update on the alarm?

Michiel Saelen [SLC] [DevOps Enabler] Selected answer as best 25th February 2021

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
5
Wouter Demuynck [SLC] [DevOps Advocate]5.93K Posted 25th February 2021 0 Comments

As far as I know, there’s not that much difference between alarm generation for parameters that are being set using history sets and parameters that are being set without, except for the timestamp of the alarm:

In both cases, values are being provided by the driver sequentially, each with a newer timestamp than the previous update. The logic applied is the same as for non-historyset parameters:

If a value update causes an alarm template limit to be breached, a new alarm is created with that value and the associated timestamp.

If a next value comes in, the alarm will not be updated unless the severity changes (escalate/drop/clear). If the severity doesn’t change, the value displayed in the alarm remains the initial value which caused it to enter the current severity.

Michiel Saelen [SLC] [DevOps Enabler] Selected answer as best 25th February 2021
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