JIRAlert implements Alertmanager's webhook HTTP API and connects to one or more JIRA instances to create highly configurable JIRA issues. One issue is created per distinct group key — as defined by the group_by parameter of Alertmanager's route configuration section — but not closed when the alert is resolved. The expectation is that a human will look at the issue, take any necessary action, then close it. If no human interaction is necessary then it should probably not alert in the first place. This behavior however can be modified by setting auto_resolve section, which will resolve the jira issue with required state.
If a corresponding JIRA issue already exists but is resolved, it is reopened. A JIRA transition must exist between the resolved state and the reopened state — as defined by reopen_state — or reopening will fail. Optionally a "won't fix" resolution — defined by wont_fix_resolution — may be defined: a JIRA issue with this resolution will not be reopened by JIRAlert.
Get JIRAlert, either as a packaged release or build it yourself:
$ go get github.com/prometheus-community/jiralert/cmd/jiralert
then run it from the command line:
$ jiralert
Use the -help flag to get help information.
$ jiralert -help
Usage of jiralert:
-config string
The JIRAlert configuration file (default "config/jiralert.yml")
-listen-address string
The address to listen on for HTTP requests. (default ":9097")
[...]
JIRAlert expects a JSON object from Alertmanager. The format of this JSON is described in the Alertmanager documentation or, alternatively, in the Alertmanager GoDoc.
To quickly test if JIRAlert is working you can run:
$ curl -H "Content-type: application/json" -X POST \
-d '{"receiver": "jira-ab", "status": "firing", "alerts": [{"status": "firing", "labels": {"alertname": "TestAlert", "key": "value"} }], "groupLabels": {"alertname": "TestAlert"}}' \
http://localhost:9097/alertThe configuration file is essentially a list of receivers matching 1-to-1 all Alertmanager receivers using JIRAlert; plus defaults (in the form of a partially defined receiver); and a pointer to the template file.
Each receiver must have a unique name (matching the Alertmanager receiver name), JIRA API access fields (URL, username and password), a handful of required issue fields (such as the JIRA project and issue summary), some optional issue fields (e.g. priority) and a fields map for other (standard or custom) JIRA fields. Most of these may use Go templating to generate the actual field values based on the contents of the Alertmanager notification. The exact same data structures and functions as those defined in the Alertmanager template reference are available in JIRAlert.
In the configuration file, the password field is used to authenticate with the JIRA API. You can directly provide the password in this field. However, for added security, you can also use an environment variable to store your password. If you prefix the password field with ENV:<super-secret-token>, JIRAlert will read the password from an environment variable named <super-secret-token>.
To enable Alertmanager to talk to JIRAlert you need to configure a webhook in Alertmanager. You can do that by adding a webhook receiver to your Alertmanager configuration.
receivers:
- name: 'jira-ab'
webhook_configs:
- url: 'http://localhost:9097/alert'
# JIRAlert ignores resolved alerts, avoid unnecessary noise
send_resolved: falseJIRAlert imports net/http/pprof to expose runtime profiling data on the /debug/pprof endpoint. For example, to use the pprof tool to look at a 30-second CPU profile:
go tool pprof http://localhost:9097/debug/pprof/profileTo enable mutex and block profiling (i.e. /debug/pprof/mutex and /debug/pprof/block) run JIRAlert with the DEBUG environment variable set:
env DEBUG=1 ./jiralertJiralert is an open source project and we welcome new contributors and members of the community. Here are ways to get in touch with the community:
- Issue Tracker: GitHub Issues
JIRAlert is licensed under the MIT License.
Copyright (c) 2017, Alin Sinpalean