Webex Teams is an application for continuous team collaboration with Cisco video meetings, group messaging and file sharing. Topics or teams are organized in so-called Spaces. You can also use such a space to receive alerts from Checkmk. For the actual connection a webhook must be created in Webex Teams.
2. Installing the extension package
In order to be able to receive notifications from Checkmk in Cisco Webex Teams, first you have to install the appropriate extension package. This extension packge was added to Checkmk in the Feature Pack 2 and delivered within Checkmk 1.6.0p12. If you are running at least this patch level, you can install the extension via WATO > Extensions Packages and clicking the install button next to cisco_webex_teams_notifications.
3. Configuring Cisco Webex Teams
The prerequisite for receiving alerts from Checkmk in Webex Teams is therefore that at least one area (Space) is set up. This can be done in a few seconds and is described in the Webex help: Webex Teams — Create a Space.
For a first test, at any rate it is certainly a good idea to set up a dedicated area with an appropriate name just for Checkmk.
In Webex Teams the Incoming Webhooks app must now be activated or connected. You can find this app in the Webex App Hub.
Click on Connect on this page. (If you are not logged into Webex Teams with the browser you are using, the Cisco Webex login screen will appear first).
After a short waiting period, at first it looks as if not much has changed — but now, at the end of the input and selection fields, you can specify both a name for the webhook and the area to be used in Webex Teams. Finally click on Add.
Next, copy the Webhook URL created in this way by clicking on the corresponding icon.
4. Configuration in Checkmk
The activation in Checkmk is limited to the specification of the webhook URL copied above:
For the Notification Method select Cisco Webex Teams.
Enter (insert) the copied Web Hook URL.
Optionally, you may specify URL prefixes to control links on your Checkmk GUI within the notification. Instead of specifying the webhook URL directly here, you can also use WATO’s password store and read the URL from one of its entries.
For testing you can use the Fake check results and Custom notification commands.