One thing to add to Catalin's reply.
When you click on the Events tab in OneClick, you are request the historical events from the Archive Manager (DDM) database for the model(s). By default, the last 4 hours of events.
If there is an event that asserts an alarm but is not logged to the DDM database, you will not see that event in the Events tab.
The only time you would see an event in the Events tab that is not configured to be logged is if you have clicked on the Events tab and the event was generated at that time. You will see that event. However, if you navigate out of the Event tabs to some other view in OneClick away from that model and then go back to that Events tab for that model, you will not see the event anymore.
Joe
Original Message:
Sent: Nov 07, 2024 04:28 AM
From: Catalin Farcasanu
Subject: Number of important alarms and number of important events do not match
Event is different than alarm. Not all events create alarms. On a OC view, the events tab is related to the selection being made în the OC interface.
This is similar with the view for alarms. Alarms are displayed, according to the selection being made in the OC interface.
Alarms are the one that are important, and not events. Events can be in the number of millions and cannot be managed in the OC interface.
Furthermore, by default, the Events that can be displayed in the OC interface span for a period of 45 days. If you have alarms that are active in OC for more than 45 days, you will not find their corresponding events in the Events tab.
Events are relevant in troubleshooting scenarios and in reporting analysis. You can have reports on the number of events, the devices that have the most events and so on. These reports can help you in optimization of your environment.
------------------------------
Cătălin Fărcășanu
Senior Consultant
SolvIT Networks
Original Message:
Sent: Nov 07, 2024 03:22 AM
From: MARUBUN SUPPORT
Subject: Number of important alarms and number of important events do not match
Hi Team,
Product
DX NetOps Spectrum
[Question]
When we select an alarm with a severity of "Critical" on the "Alarms" tab on the OneClick screen, the following two values are different.
- The number displayed on the "Alarms" tab.
- The number of events displayed when filtering by severity "Critical" on the "Events" tab.
Does this mean that the values are different due to the product specifications?
If so, I would appreciate it if you could introduce any documents (manuals, Knowledge, etc.) that explain this.
Thanks,