Based on threshold reach alert should go to different group

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
grayloglearn
Posts: 222
Joined: Thu Jul 06, 2017 8:55 am

Based on threshold reach alert should go to different group

Post by grayloglearn »

Hi Team,

Can some one help on that how we can configure the service alerts based on threshold reach alert should go to different group.

Ex: Cpu load alert was configured 80% warning 90% critical --> If service got reached to 80 or 90 it will go automatically to respective contact details how we configured in contact details. But

If cpu load reached 80% alert should go to some [email protected]
if cpu load reached 90% alert should go to another [email protected] ,

is it possible in nagios?
User avatar
mbellerue
Posts: 1403
Joined: Fri Jul 12, 2019 11:10 am

Re: Based on threshold reach alert should go to different gr

Post by mbellerue »

This isn't possible via normal means in Nagios. It is assumed that there is a person or team responsible for a host/service, and that person or team will respond to any notification regarding the host/service.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
grayloglearn
Posts: 222
Joined: Thu Jul 06, 2017 8:55 am

Re: Based on threshold reach alert should go to different gr

Post by grayloglearn »

We understand that once they receive alert team/person will takecare.

your answer is we can't configure via nagios right ?
User avatar
mbellerue
Posts: 1403
Joined: Fri Jul 12, 2019 11:10 am

Re: Based on threshold reach alert should go to different gr

Post by mbellerue »

That was my answer, but apparently I am mistaken. There is a way to do what you need to do. It requires the use of escalations.
https://assets.nagios.com/downloads/nag ... ations.pdf

The basic process is this. You create an escalation for warnings and an escalation for criticals for a service. The escalations are set to start with the first notification that gets sent out. This way you can set different contact information for warnings versus criticals.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked