Hello Team,
Appreciate your support in setting up Nagios xi to send the events data to MoogSoft using Webhook integration.
BR,
Ashok Kanojia
Nagios xi Integration to MoogSoft using Webhook
-
- Posts: 1
- Joined: Thu Sep 26, 2024 4:23 am
-
- Posts: 318
- Joined: Mon Apr 06, 2020 2:49 pm
Re: Nagios xi Integration to MoogSoft using Webhook
Hi @ashokkuma, thanks for reaching out.
Are you looking for assistance with Webhook?
The Slack wizard uses a Webhook plugin (configwizards/eventhandler_notify_slack), if you are looking for examples.
There are also a few Webhook plugins on the Nagios Exchange
Are you looking for assistance with Webhook?
The Slack wizard uses a Webhook plugin (configwizards/eventhandler_notify_slack), if you are looking for examples.
There are also a few Webhook plugins on the Nagios Exchange
Please let us know if you have any other questions or concerns.
-Laura
-Laura
-
- Posts: 144
- Joined: Tue Apr 23, 2019 7:12 pm
Re: Nagios xi Integration to MoogSoft using Webhook
Integration with Moogsoft is not difficult however it will require a modicum of strategy be employed to make xi something of a usable signal source.
Signal Origin Type:
This will be either an alert using the Nagiosxi notification workflow or an event handler implementation. Both options will require a little scripting.
The notification workflow allows you to use basic criteria and controls already available within xi to manage the signal being sent to Moogsoft.
https://assets.nagios.com/downloads/nag ... .75%2C0%5D
The event handler evaluation of the check status results requires deeper programming but, is more powerful in my opinion and can be set at the global level.
https://assets.nagios.com/downloads/nag ... ios-xi.pdf
Signal Payload:
The payload format required by Moogsoft is pretty simple.
https://docs.moogsoft.com/moogsoft-clou ... -apis.html
Populating the payload:
This is where your host and service naming conventions come into play. You can build a descriptive payload to forward to Moogsoft using the Nagios Macros and custom vars to align and set your tags.
Signaling Moogsoft:
This is just an http POST with a json payload as described in the Moogsoft docs.
Happy Monitoring!
--SN
Signal Origin Type:
This will be either an alert using the Nagiosxi notification workflow or an event handler implementation. Both options will require a little scripting.
The notification workflow allows you to use basic criteria and controls already available within xi to manage the signal being sent to Moogsoft.
https://assets.nagios.com/downloads/nag ... .75%2C0%5D
The event handler evaluation of the check status results requires deeper programming but, is more powerful in my opinion and can be set at the global level.
https://assets.nagios.com/downloads/nag ... ios-xi.pdf
Signal Payload:
The payload format required by Moogsoft is pretty simple.
https://docs.moogsoft.com/moogsoft-clou ... -apis.html
Populating the payload:
This is where your host and service naming conventions come into play. You can build a descriptive payload to forward to Moogsoft using the Nagios Macros and custom vars to align and set your tags.
Signaling Moogsoft:
This is just an http POST with a json payload as described in the Moogsoft docs.
Happy Monitoring!
--SN