Nagios integration with Service-now

[Beena_Jogin]

Hi Team,

we have installed the Nagios XI 5.7.2 version and need to integration with service now.

 Nagios XI is possible to perform the event managements
 Which is best method to integration between Nagios and service now , please share the docs.


Thanks & Regards,
Raghavendra

[capgemtools]

Hello Raghavendra,

we have recently integrated XI with Service Now. You will need to use the nagios connector at service now end and fetch the events from XI. To do this you will need to create a normal user at XI end and use its api key (you will find it in users profile) in service now connector to fetch the events. I do not have docs on this but below is the link we followed.

https://docs.servicenow.com/bundle/orla ... ector.html

[benjaminsmith]

Thanks @Sandeep,

Also, make sure the user created for Service Now integration has API access and can see all hosts and services in the permission settings.

user-perms.png

[Beena_Jogin]

Thanks Sandeep.

But we are not using the service now event management modules in service now instance.

Need to send Nagios events with webservices with necessary field values and filteration of events

[benjaminsmith]

Hi,

Take a look at the following guide on our KB. This setup has the option to add field mappings between Nagios and Service Now.

Nagios XI - Integrating ServiceNow

If that's not going to meet your requirements, please provide a few more specifics and/or screenshots so we can better understand your requirements. We know more about Nagios XI than Service Now

Thanks!
Benjamin

[Beena_Jogin]

Hi Benjamin,

Thank for information.

Please share the offline packages for mentioned modules becuase server dont have internet access, if possible to share , i will install and get back you .

# yum install -y perl-DBI perl-XML-Simple perl-SOAP-Lite perl-Config-IniFiles perl-Digest-MD5-File
#cpan

Regarding requirments:-
1> Need to Map the Nagios fields with service now
2>Events should create the indicent in service-now with respective Assgiment group with urgency /priority level (HIgh, medium or low)
3> Duplicate alerts should be aviod like host itself is down then no need to trigger the server health parameters(CPU, Memory, services etc ), it should only one ticket instead of mutpile of tickets.
4>how to aviod floods of events ?

Thanks
Raghavendra

[lmiltchev]

Please share the offline packages for mentioned modules becuase server dont have internet access, if possible to share , i will install and get back you .

Most likely you would need to set up some local repos on the offline server in order to install all of the prerequisites. Unfortunately, we don't have a guide on that, so it is out of scope of Nagios support.

1> Need to Map the Nagios fields with service now

What is the specific issue that you are currently having? Have you reviewed the "Field Mapping" section in the KB article listed below?

https://support.nagios.com/kb/article/n ... w-552.html

2>Events should create the indicent in service-now with respective Assgiment group with urgency /priority level (HIgh, medium or low)

ServiceNow is NOT one of our products. We do provide integration, however if something is not present in our integration guide, this means it is out of scope of Nagios Support. You may try getting more help from the ServiceNow support.

3> Duplicate alerts should be aviod like host itself is down then no need to trigger the server health parameters(CPU, Memory, services etc ), it should only one ticket instead of mutpile of tickets.

If the host is in hard non-OK state, notifications for services on this host won't be sent out. This is by design. Read more about Nagios notifications here:

https://assets.nagios.com/downloads/nag ... tions.html
system

4>how to aviod floods of events ?

There are many ways to avoid flood of events in XI. Most of the time a flood of notifications is caused by a mis-configured system. Make sure that you set the parent-child relationships correctly on your Nagios XI server. For more information, see this:

https://assets.nagios.com/downloads/nag ... ility.html

Also, you can tweak some of the check settings, e.g. increasing "

Please share the offline packages for mentioned modules becuase server dont have internet access, if possible to share , i will install and get back you .

Most likely you would need to set up some local repos on the offline server in order to install all of the prerequisites. Unfortunately, we don't have a guide on that, so it is out of scope of Nagios support.

1> Need to Map the Nagios fields with service now

What is the specific issue that you are currently having? Have you reviewed the "Field Mapping" section in the KB article listed below?

https://support.nagios.com/kb/article/n ... w-552.html

2>Events should create the indicent in service-now with respective Assgiment group with urgency /priority level (HIgh, medium or low)

ServiceNow is NOT one of our products. We do provide integration, however if something is not present in our integration guide, this means it is out of scope of Nagios Support. You may try getting more help from the ServiceNow support.

3> Duplicate alerts should be aviod like host itself is down then no need to trigger the server health parameters(CPU, Memory, services etc ), it should only one ticket instead of mutpile of tickets.

If the host is in hard non-OK state, notifications for services on this host won't be sent out. This is by design. Read more about Nagios notifications here:

https://assets.nagios.com/downloads/nag ... tions.html
system

4>how to aviod floods of events ?

There are many ways to avoid flood of events in XI. Most of the time a flood of notifications is caused by a mis-configured system. Make sure that you set the parent-child relationships correctly on your Nagios XI server. For more information, see this:

https://assets.nagios.com/downloads/nag ... ility.html

Also, you can tweak some of the check settings, e.g. increasing "max_check_attempts", some of the warning and critical thresholds, etc.

Hope this helps.

[Beena_Jogin]

HI Team,

I'm getting 400 error in log for service now integration

8/10/2020 10:47:57 Config loaded.
8/10/2020 10:47:57 Connecting to: https://inf.nagio.interface.user:xxxxxx ... nt.do?WSDL
8/10/2020 10:47:58 Connection to Service-Now Failed: 400 Bad Request

please let me know if required change any settings.

Regards
Raghavendra

[tgriep]

You said that the Nagios server is offline but it needs to have access to the internet to push the Service Now tickets to the ServiceNow server.
Can the Nagios server connect to the ServiceNow server?

There is a config.ini file for service now that has the URL that you set to connect to.

Code: Select all

sn_url = <URL for Service Now>

Can you ping the Service Now host and is port 443 open which is used to communicate to the Service Now server?

[Beena_Jogin]

Able to ping the service now instance and port 443 has been opened , but still getting the 400 bad request

[root@LMMISEAD]# ping poc1.osnow.de
PING poc1.osnow.de (139.1.152.51) 56(84) bytes of data.
64 bytes from 139.1.152.51 (139.1.152.51): icmp_seq=1 ttl=241 time=8.02 ms
64 bytes from 139.1.152.51 (139.1.152.51): icmp_seq=2 ttl=241 time=8.28 ms
64 bytes from 139.1.152.51 (139.1.152.51): icmp_seq=3 ttl=241 time=8.51 ms
^C
--- poc1.osnow.de ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 8.022/8.276/8.517/0.202 ms

[root@ LMMISEAD]# nmap poc1.osnow.de 443

Starting Nmap 6.47 ( http://nmap.org ) at 2020-10-13 17:19 UTC
setup_target: failed to determine route to 443 (0.0.1.187)
Nmap scan report for poc1.osnow.de (139.1.152.51)
Host is up (0.011s latency).
Not shown: 998 filtered ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https

Nmap done: 1 IP address (1 host up) scanned in 4.08 seconds
[root@ LMMISEAD]#


[root@ LMMISEAD]# nmap poc1.osnow.de -p 443

Starting Nmap 6.47 ( http://nmap.org ) at 2020-10-13 17:22 UTC
Nmap scan report for poc1.osnow.de (139.1.152.51)
Host is up (0.0080s latency).
PORT STATE SERVICE
443/tcp open https

Nmap done: 1 IP address (1 host up) scanned in 0.12 seconds