Semantically, we've done the following: // name of the client sending the alert. client: "influxdata" // url of the client sending the alert. client_url: the endpoint URL for now (needs to change to rule) // The class/type of the event, for example ping failure or cpu load class: check's name // Logical grouping of components of a service, for example app-stack group: source measurement Co-authored-by: Alirie Gray <alirie.gray@gmail.com> |
||
---|---|---|
.. | ||
http.go | ||
http_test.go | ||
pagerduty.go | ||
pagerduty_test.go | ||
rule.go | ||
rule_test.go | ||
slack.go | ||
slack_test.go |