Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Keep a monitor threshold data despite server or agent restart

Keep a monitor threshold data despite server or agent restart

Hi,

Here is an idea to keep a monitor threshold data despite server or agent restart. This feature will provide an ability not to get duplicate alerts in case if the thresholds were reset when agent's services were restarted or server was restarted during some maintenance. For example, keep thresholds in the memory an store them in the state file during stopping of agent processes and restoring to the memory during starting of an agent. Clean a  state file only in case of agent cleanstart.

4 Comments
ScottKnox Respected Contributor.
Respected Contributor.
Status changed to: Waiting for Votes

This Idea is now open for review, comments and voting.  Please provide your insights

Respected Contributor.. kononenkoni Respected Contributor..
Respected Contributor..

Hi @ScottKnox,

Could you please maybe move this idea to OpsB Idea Exchange?  It is mostly related to operations manager Linux, operations agent, etc,.

binuj Respected Contributor.
Respected Contributor.

This is an issue that i am also experincing. Once a server is restarted the old alarms remains while the new alarm is raised and duplicated. The new event does not acknowledge the old event in OMI or even duplicates in the same event but creates a new event.

In case i have a file system alarm and after restart if the file system is stillabove threshold it raises a new event

binuj Respected Contributor.
Respected Contributor.

We are also facing the same issue.

Is the event corelation at the OMi server level or at the agent level? If it is at the OMI server level based on the event key it should not create duplicate issue.

Even for DB monitoring when the DB is shut down the alarms related to process etc do come. BUt after the server reboot and the DB is brought up all the critical alarms related to DB is still active which has to be manually closed

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.