Pushover is a simple service to send messages from various sources to Apple or Android mobile devices, where they appear as notifications. On the desktop, the messages can be received via the browser. The connection is established via two API keys for a group and an app/source.
1. Configuring Pushover
In Pushover you need to create both a group, even if you only have one 'group', and an app explicitly for Checkmk — each receives their own API key:
Create a new group with at least one member via Create a Group in Pushover.
Copy the displayed Group API key.
Create an app with any name via Create an Application/API Token.
Copy the displayed App API key.
2. Configuring Checkmk
You have already learned how to set up Checkmk notifications in general in the article on notifications.
In Checkmk it is now sufficient to specify the two keys copied above:
Create a new notification rule with Setup > Events > Notifications > Add rule.
For the Notification Method choose Push Notifications (using Pushover).
Enter the copied App API key under API Key.
-
Enter the copied Group API key under User / Group Key:
You can optionally activate the Priority and Select sound Pushover functions. You can use the priority function to override rest periods configured in Pushover — and then accompany such notifications with appropriate sounds.
When using the following Contact selection box, note the following two points:
When selecting contacts, make sure that the notifications are only sent to one contact, e.g. by selecting a single user. With the notification methods for ticket systems etc., the contact selection only serves to specify that notifications are sent. However, the notifications are not sent to the selected user, but to the ticket system. Note that a contact selection via contact groups, all contacts of an object or similar usually generates several identical notifications for an event, which then end up in the ticket system twice, three times or even more often.
If the first point is fulfilled, but the user is used in several notification rules for the same method, then only the last rule applies in each case. It is therefore advisable to create a separate functional user for each of these notification rules.
You can find out how to test the new notification method in the article on notifications.