PagerDuty also supports other event types that you may want to handle differently, such as adding users to the incident channel when an incident is assigned to them. PagerDuty incidents could be acknowledged or a Jira ticket with the relevant incident information can be created without leaving your Mattermost client.
#MATTERMOST URL ARCHIVE#
For example, on resolution of a ticket, a script could get all the posts in the incident channel, as well as any files that were uploaded, and put them in an archive that’s attached to the incident resolution.īecause Mattermost supports interactive message buttons and slash commands, you can also send hooks out of Mattermost. This recipe just shows a couple of ways you can use a webhook and Mattermost to improve incident notification and organization. To get to them, go to Configuration> Services. But first, you need to add it as an extension to that service. Outgoing webhooks in PagerDuty are linked to monitoring services. But any system that can send an outgoing webhook when an event is triggered could be used as a replacement. PagerDuty is a widely used alerting system. To test that the webhook is working correctly, run this command from inside the PagerDuty Recipe directory: $ curl -vX POST -d -header "Content-Type: application/json"Ĭhange trigger to either acknowledge or resolve to use those incident states. Then edit the configuration to authenticate to your Mattermost server and specify the team name and users who should be notified.įinally, make sure you have webhook installed and run webhook -verbose to start listening for the notifications. Next, make a copy of and rename it conf.yaml. Then edit the execute-command and command-working-directory to use the correct path. To create your own config files, make a copy of and rename it to hooks.json. It includes a webhook configuration, a Ruby script called from the webhook and a sample config file as well as a small Mattermost API library to handle talking to your Mattermost server. The code for this is open source and available here. It should be considered a guide more than a production-ready application.
#MATTERMOST URL HOW TO#
Note: This code is mainly used to illustrate how to access the Mattermost API and connect it to a webhook.
#MATTERMOST URL UPDATE#
This is a very specific solution that will create a channel and invite some people on an incident trigger, update the channel header when the incident status changes and close the channel and output resolution statistics to the Town Hall
This is a simple recipe to help notify people that an incident occurred and keep discussion of the incident organized. But responding to the incident and getting a team together can take a while, and incident discussion can clutter up existing Mattermost channels. Many DevOps teams have incident alerting systems. If there’s a Recipe you want us to cook up in the future, drop us a line on our forum. The goal of these posts is to provide you with solutions to specific problems, as well as a discussion about the details of the solution and some tips about how to customize it to suit your needs perfectly. Here’s the next installment in our Mattermost Recipes series.
0 kommentar(er)
