Previously, some customers had requested support in triggering incidents in StatusHub from an external service that we did not directly support e.g. Pingdom, PagerDuty, New Relic, VictorOps, etc.
With this new option, any product/service that supports sending POST requests with a JSON payload can be integrated with Statushub. Such as products like Nagios and services like SolarWinds.
How to enable Generic Hook for a service:
Click on the option "Edit status site". Once there, you will need to select the "Services & Integrations" page on the side menu. Click on the Arrow icon to select the group.
A window listing services will open, click the Pencil icon next to the service you want to integrate with.
The 2nd tab allows you to select and configure monitoring integrations for each service if required.
Then select the Generic Hook button.
After saving changes, the link will be visible below the name of the service in "Services & Integrations" screen:
Please note that your link may be slightly different and you should always refer to "Services & Integrations" section when adding new integration in one of supported 3'rd party services
With this new hook StatusHub will expect the following request:
Method: POST
URL 1: https://hooks.statushub.io/hooks/generic_hook?token=service_token
URL 2: https://hooks.statushub.io/hooks/generic_hook
POST data example:
payload={ "title": "Our service is currently experiencing problems", "message": "We are sorry!", "type": "monitoring", "status": "degraded-performance", "service_token": "some-service-token" }
Please note that there are two URL's and there is "service_token" parameter. This gives the flexibility of specifying StatusHub service either by URL or by JSON payload depending on what suits the situation. If both will be provided, token used in URL will have priority over token specified in payload.
Note: The title is free form text. TYPE and STATUS need to be chosen from the lists shown below.
- degraded-performance
- down
Here is a screenshot from SolarWinds showing example config:
Comments
0 comments
Article is closed for comments.