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

10.2 CU11 User Status Algorithm – Changed from 10.2 CU5?

Solved825 views6th July 2023
4
Tom Brook [DevOps Member]219 11th April 2023 1 Comment

Hi,

We are currently using CU5 in our production environment and testing version CU8 on one of our production clusters and CU11 in our test environment.

It seems that in CU11, the User Status algorithm has changed.

We use the User Status to filter our alarms back to our Unacknowledged Alarm tab once an acknowledged alarm has cleared. In CU5/8 and previous versions, once an acknowledged alarm has cleared, the User Status changes from acknowledged, to resolved and then unresolved. It is this last change to unresolved that pushes the alarm back in to our Unacknowledged tab so the change in alarm state can be processed accordingly.

In CU11, however, the User Status seems to revert to resolved only, meaning the alarm does not get sent back to the Unacknowledged tab and operators would therefore be unaware that there has been an alarm change event.

Could someone confirm whether the User Status algorithm was changed in CU11 from previous versions, whether this was reverted in later upgrades, and, if not, what other status change could be used via a filter to have an acknowledged, clearable alarm reappear in the Unacknowledged tab. Just using a Status of Clearable would not be sufficient as it would introduce a number of unwanted alarms.

Thank you...

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 6th July 2023
Tom Brook [DevOps Member] commented 4th May 2023

Is there anyone that can answer this.

If not, how do users in CU11 get alarms to reappear in the alarm tab that contains unacknowledged alarms?

3 Answers

  • Active
  • Voted
  • Newest
  • Oldest
0
Michaël Pincket [SLC] [DevOps Advocate]1.74K Posted 19th May 2023 1 Comment

Hi Tom,

Nothing has changed to the Userstatus algorithm. When you have a clearable alarms, the userstatus is remembered from the previous alarm. Maybe you can try to create the following filter:

This would show all unacknowledged alarms and the clearable alarms which have been acknowledged.

Tom Brook [DevOps Member] Posted new comment 19th May 2023
Tom Brook [DevOps Member] commented 19th May 2023

Hi Michael,
Thank you for your answer but it looks like the User Status is handled differently in CU11 as compared to CU8.

In CU8 the system automatically reverts the User Status to Unresolved…

In CU11 it does not do this. The User Status remains Resolved.

The filter you supplied would show all clearable alarms on the Unacknowledged tab which is not what we want. Only ones that require processing after an alarm change to clearable. We have many clearable alarms that we would like to remain on the Active or Intermittent tabs for administrative purposes.

You are viewing 1 out of 3 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