Queries in PagerDuty
The pagerduty plugin includes 32 queries:
Name | Description | Queries |
---|---|---|
An escalation policy determines what user or schedule will be notified first, second, and so on when an incident is triggered. | ||
An incident represents a problem or an issue that needs to be addressed and resolved. | ||
Records log entries for the specified incident. | ||
An on-call represents a contiguous unit of time for which a User will be on call for a given Escalation Policy and Escalation Rules. | ||
A priority is a label representing the importance and impact of an incident. | ||
Rulesets allow you to route events to an endpoint and create collections of event rules, which define sets of actions to take based on event content. | ||
An event rule allows you to set actions that should be taken on events that meet your designated rule criteria. | ||
A Schedule determines the time periods that users are On-Call. | ||
A service represents something you monitor (like a web service, email service, or database service). | ||
A service integration is an integration that belongs to a Pagerduty service. | ||
List all of your account's tags. | ||
Members of a PagerDuty account that have the ability to interact with incidents and other data on the account. | ||
Members of a PagerDuty account that have the ability to interact with incidents and other data on the account. | ||
A PagerDuty Vendor represents a specific type of integration. |