Anonymous_User Absent Member.
Absent Member.
844 views

AppManager - Systems Monitoring Module


We are in need of verifying which module supports to Real-Time
notification of server down and not a notification since last reboot.
The NT_SystemUpTime module monitors systems that have been operaational
since the last reboot and raises an event if the system is REBOOTED
during the interval.

Is there a better module that monitors/detects a server is offline,
disconnected or turned-off in RealTime and sends a notification?

Thanks.


--
rnasa2
------------------------------------------------------------------------
rnasa2's Profile: https://forums.netiq.com/member.php?userid=6184
View this thread: https://forums.netiq.com/showthread.php?t=49076

0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: AppManager - Systems Monitoring Module


The "AMHealth" module should do this. Assuming you are on AM8. Is it not
doing what you want?

The AMHealth module is designed to alert you if an agent goes "down" for
any reason. That might be a system failure, or a failure of the
AppManager agent itself. Basically the job
"AMHealth_Heartbeat[Win]/[UNIX]" runs on the agent and sends a data
point and event back to the QDB. If that is missing then you will get an
alert about it. The time period that elapses is basically related to the
schedule of the job - so if the job runs every 5 minutes we would expect
the data point/event to be present and no more than 5 minutes old. If
the job runs every minute, it is expected to be no more than 1 minute
old.

Out of the box, these jobs are part of a policy that affects all agents
in AM8 QDBs. You can modify that policy (so you can change the default
schedules from 5 to 1 minute). Or remove it completely and set up your
own policy/policies. For example you may decide that you don;t need to
do this for all servers, so you might set up a Management Group for
"important" servers where you run every minute, for other servers where
you run every 5 minutes and then not run on other servers where you
don;t need that level of notification.

The "Uptime" jobs are jobs which rely on the agent being "up" in order
to notify you because they run on the agent. So they are useful for
notifying you that a reboot happened, and keeping data to show uptime
stats. But less useful in your scenario for notifying you that the
system is currently down.

Agents will also "grey out" when they are down, but this happens after
around 15 minutes when the MS picks up on the fact that an agent is
unresponsive when it does it's normal "check" cycle of agents.

If the AMHealth and "grey out" options are not what you are looking for,
you can also use "MachineDown". But you need to plan the use of this if
you are checking a number of servers... this runs on SERVERA and checks
SERVERB (and C, D etc.). It does this sequentially and it involves a
registry check (for windows machines). Due to the RPC timeouts involved
- if servers it checks are in fact down, the job can start to take a
long time to execute. So you would not want to run this and have it
checking 500 servers...


--
Andy Doran
Software Engineer Consultant (NetIQ)
------------------------------------------------------------------------
andy_doran's Profile: https://forums.netiq.com/member.php?userid=3937
View this thread: https://forums.netiq.com/showthread.php?t=49076

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AppManager - Systems Monitoring Module


rnasa2;236094 Wrote:
> We are in need of verifying which module supports to Real-Time
> notification of server down and not a notification since last reboot.
> The NT_SystemUpTime module monitors systems that have been operational
> since the last reboot and raises an event if the system is REBOOTED
> during the interval.
>
> Is there a better module that monitors/detects a server is offline,
> disconnected or turned-off in Real-Time and sends a notification?
>
> Thanks.


If, however, you are using AppManager version 7, then you can still use
the Machine Down KS that Andy mentioned, but the AMHealth module is for
version 8 only. But an alternative is my Server Down KS which you can
download from http://community.netiq.com/media/p/11751.aspx. Rather than
ping every machine, my KS looks for gaps in collected data from each
agent on the basis that if data has recently been received then both the
server and the agent must be up. Only servers which have not returned
data for a defined period are checked, so it is, I feel a more efficient
mechanism than pinging everything every few minutes.


--
Alain Salesse | Senior Technology Consultant | Alain.Salesse@NetIQ.com
------------------------------------------------------------------------
Alain.Salesse's Profile: https://forums.netiq.com/member.php?userid=3958
View this thread: https://forums.netiq.com/showthread.php?t=49076

0 Likes
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.