Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds Zenoss event handler as requested by https://github.com/influxdata/feature-requests/issues/72. Fixes #2483.
The handler provides options for Zenoss basic event fields:
summary
'{{ .Message }}'
device
component
severity
eventClass
eventClassKey
collector
message
In addition to the basic fields, custom fields can be set with
customField
option. The value of a custom field can be simple type or a string representation of JSON object. There are also handler options to override Zenoss event-related values set in the configuration:action
,method
,type
,tid
. All these options support templates with the following variables available:Name
,TaskName
,ID
,Message
,Details
,Time
,Duration
,Level
,Recoverable
andTags
.Severity mapping
Alert level is mapped to Zenoss event severity according to mapping specified in the configuration file. Severity can be specified either as a number or a string (see Event severity levels). The default configuration maps
OK
toClear
,Info
toInfo
,Warning
toWarning
andCritical
toCritical
.TICKscript examples:
Default configuration:
Required for all non-trivial PRs