Skip to main content

Demo video: Integrate with Zabbix ►

After watching this video, you will be able to configure an integration to send events from Zabbix into the Moogsoft Cloud.

This demo uses Zabbix version 5.4, which may be different from your instance.  But it should orient you enough to make it easy. Let’s get started!

1_Zabbix.png

Name your integration, then grab the Moogsoft Endpoint and API key.

2_Zabbix.png

You also need a Zabbix media type file, which is available in our docs.

3_Zabbix.png

OK we have everything we need to make this happen.  Let’s go to our Zabbix instance. Import the media type file we just downloaded.

4_Zabbix.png

Then add the API key and the Moogsoft Endpoint.

5_Zabbix.png

This part of the media type definition maps Zabbix field names to Moogsoft fields.

6_Zabbix.png

These fields are required.

7_Zabbix.png

Add optional fields based on your requirements.

8_Zabbix.png

This Javascript uses the mapped parameters to do further refinement, and compose the JSON payload to Moogsoft. You can edit the script to add optional fields.

9_Zabbix.png

Let’s test to make sure it works. Looks good. The media type task is done.

10_Zabbix.png

Next, we need to create a user to receive event notifications using our Moogsoft media type.

11_Zabbix.png

Then add the user to a  group to grant the right level of access. The Moogsoft user won’t need access to the Zabbix front end, so we’ll choose this one.

12_Zabbix.png

The password is required but it won’t be used, so you can enter anything here.

13_Zabbix.png

This user needs to be able to use the Moogsoft media type. This will send event notifications directly to Moogsoft Cloud.

14_Zabbix.png

And this user needs a super admin role.

15_Zabbix.png

The user definition task is done.Now we have the pathway to Moogsoft Cloud all set up. Next we want to add the trigger logic to use that pathway when events happen. We’ll do that by defining an action. You can update existing actions or define custom actions to trigger on specific problems, but here we’ll simply define an action to send all events to Moogsoft.

16_Zabbix.png

If we wanted to restrict the severity of events or filter them in some other way, we could define a condition here.

17_Zabbix.png

Let’s say we want to send all events, so we won’t add a condition. Under Operations, specify what happens when an event, recovery, or update occurs.

18_Zabbix.png

We will send a message to the Moogsoft user using the media type Moogsoft Cloud.

19_Zabbix.png

We’ll repeat these settings for recovery and update events and add the action.

20_Zabbix.png

All set. The action definition task is done. Now we can see our Zabbix event data in Moogsoft Cloud. Thanks for watching!

21_Zabbix.png