Stop Information events from being sent to Cube client

Solved1.41K viewsCube
3
2 Comments

For DMAs where there is an excessive number of information events being reported, >200K per day, is there a way to stop these events from being sent to the Cube session. For example, if the Information tab is NOT added to the alarm console will that stop the DMA from sending the events to the Cube? What about if it is added but just not selected as the Active tab? What about Information tabs that are included in other sides of the Cube when those sides are not active?

Thanks

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 11th July 2023
Ruben Vandepitte [SLC] [DevOps Advocate] commented

Hi Jeff,

Which type of information events are generating the bulk of the messages? Are these standard DataMiner information events, or custom events generated by your elements, scripts, etc…?
Jeff Douglass commented

These are standard DM messages generated when a service is edited

2 Answers

8
2.50K 3 Comments

Hi Jeff,
You can configure a user/group setting to filter the alarms that are being sent to Cube: see DataMiner Help -> Filter the alarms before they enter Cube

In the setting you can select a public alarm filter that can look like this:

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 11th July 2023
Jeff Douglass commented

Thanks, I will look into that
Miguel Barquet [SLC] [DevOps Enabler] commented

Thank you Pieter. So regardless of the communication method between Cube client and DataMiner server (Polling vs Eventing), the Client will receive ALL alarms and information events regardless of the filters applied in the Alarm Console. The only way to change this behavior is to filter out some alarms and this can be done in DataMiner Settings -> User Settings -> Alarm Console -> Filter the alarms before they enter Cube
Pieter Van Compernolle [SLC] [DevOps Enabler] commented

Completely true, Miguel.
Security is applied of course, ‘All alarms’ means ‘All alarms that you are allowed to see’.
1
1.56K 0 Comments

Here is an idea, when Cube is configured in Polling method (as opposed as Eventing) information events are not "sent to the Cube session" instead they are retrieved by the Cube. Assuming that the Cube only retrieves the information events based on the Alarm Console tab filter, we could configure a tab that shows only those information events we truly care about, if any. By default, the Alarm Console contains a tab that displays ALL recent information events which is obviously not ideal given the large number of information events.
Please do not hesitate in giving further responses to this thread. I'd like to know if this suggestion will actually work and whether there are other options to accomplish the objective stated by Jeff.
Thanks in advance

Miguel Barquet [SLC] [DevOps Enabler] Edited answer 1st February 2021