pagerduty
editpagerduty
edit- Version: 3.0.3
- Released on: September 15, 2016
- Changelog
Getting Help
editFor questions about the plugin, open a topic in the Discuss forums. For bugs or feature requests, open an issue in Github. For the list of Elastic supported plugins, please consult the Elastic Support Matrix.
Description
editThe PagerDuty output will send notifications based on pre-configured services
and escalation policies. Logstash can send "trigger", "acknowledge" and "resolve"
event types. In addition, you may configure custom descriptions and event details.
The only required field is the PagerDuty "Service API Key", which can be found on
the service’s web page on pagerduty.com. In the default case, the description and
event details will be populated by Logstash, using message
, timestamp
and host
data.
Synopsis
editThis plugin supports the following configuration options:
Required configuration options:
pagerduty { service_key => ... }
Available configuration options:
Setting | Input type | Required |
---|---|---|
No |
||
No |
||
No |
||
No |
||
string, one of |
No |
|
No |
||
No |
||
No |
||
Yes |
||
<<,>> |
No |
Details
edit
codec
edit- Value type is codec
-
Default value is
"plain"
The codec used for output data. Output codecs are a convenient method for encoding your data before it leaves the output, without needing a separate filter in your Logstash pipeline.
description
edit- Value type is string
-
Default value is
"Logstash event for %{host}"
Custom description
details
edit- Value type is hash
-
Default value is
{"timestamp"=>"%{@timestamp}", "message"=>"%{message}"}
The event details. These might be data from the Logstash event fields you wish to include. Tags are automatically included if detected so there is no need to explicitly add them here.
enable_metric
edit- Value type is boolean
-
Default value is
true
Disable or enable metric logging for this specific plugin instance by default we record all the metrics we can, but you can disable metrics collection for a specific plugin.
event_type
edit-
Value can be any of:
trigger
,acknowledge
,resolve
-
Default value is
"trigger"
Event type
id
edit- Value type is string
- There is no default value for this setting.
Add a unique ID
to the plugin configuration. If no ID is specified, Logstash will generate one.
It is strongly recommended to set this ID in your configuration. This is particularly useful
when you have two or more plugins of the same type, for example, if you have 2 grok filters.
Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
output { stdout { id => "my_plugin_id" } }
incident_key
edit- Value type is string
-
Default value is
"logstash/%{host}/%{type}"
The service key to use. You’ll need to set this up in PagerDuty beforehand.
pdurl
edit- Value type is string
-
Default value is
"https://events.pagerduty.com/generic/2010-04-15/create_event.json"
PagerDuty API URL. You shouldn’t need to change this, but is included to allow for flexibility should PagerDuty iterate the API and Logstash hasn’t been updated yet.