http
or https
URL. For https
URLs the certificate must be valid.application/json
. The User-Agent header will begin with pgDash-Webhook
. The connection will be closed after a successful request.alerts
array described below is empty). As per the previous rule, another notification will be sent only when this state changes, that is, when an alert rule is triggered.version
- integer - the version of the JSON object's schema. Currently always 1. Note that backwards-compatible changes, like adding a new property might be done without incrementing this version number.server
- string - the name of the server whose alert status has changed.reported
- integer - the timestamp of the pgmetrics report which caused the change in the alert status. The timestamp is represented as the number of seconds since epoch (1 Jan 1970).alerts
- array of objects - the list of warning or critical alerts, each as an object with properties as below. Note that if the alerts just cleared and the state went back to normal, this array will be empty. For each separate object that triggered a rule, there will be a separate entry in this array (example if the rule is "Table size is greater than 100 MiB" and two tables qualify, there will be two entries in this array that have the same "text" property.)type
- string - one of warn
or crit
indicating a rule type of warning or critical respectively.text
- string - a description of the alert rule, example "Number of backends is greater than 40", "Database size is greater than 1 GiB".value
- string - the current value which triggered the rule, example "43", "1.4 GiB"objname
- string - the name of the object involved in the alertobjlink
- string - a URL to the object involved in the alertquery
- string, optional - if this is a query-level alert, the full SQL query textversion
- integer - the version of the JSON object's schema. Currently always 1. Note that backwards-compatible changes, like adding a new property might be done without incrementing this version number.server
- string - the name of the server involved.prevreport
- integer - the timestamp (as seconds since epoch 1 Jan 1970) of the previous report which was the basis for the change.currreport
- integer - the timestamp (as seconds since epoch 1 Jan 1970) of the current report which has changed since the previous one.changes
- array of objects - the list of changes. Each entry is a JSON object with the following properties:item
- string - a description of the changeprev
- string, optional - the previous value, if applicablecurr
- string, optional - the current value, if applicable