PAGERDUTY_POST_INCIDENT_METRICS

This endpoint retrieves analytics metrics for responder teams based on incident data in PagerDuty. It allows for detailed filtering and customization of the data set, enabling users to analyze team and responder performance across various dimensions such as time range, urgency, priorities, and specific teams or responders. The endpoint is particularly useful for generating reports, assessing team efficiency, and identifying trends in incident management. It should be used when comprehensive analytics on responder team performance are needed, especially for large-scale or complex incident management scenarios. However, it's important to note that the endpoint has a maximum time range of one year for analysis, and the results are limited to the data the requestor has access to within the PagerDuty system.

Available from 1 provider (1 remote)

Input Schema

            {
  "type": "object",
  "properties": {
    "order": {
      "enum": [
        "asc",
        "desc"
      ],
      "type": "string",
      "title": "Order",
      "description": "The order in which the results were sorted; asc for ascending, desc for descending. "
    },
    "order_by": {
      "type": "string",
      "title": "Order By",
      "description": "The column that was used for ordering the results."
    },
    "time_zone": {
      "type": "string",
      "title": "Time Zone",
      "description": "The time zone to use for the results and grouping."
    },
    "filters__urgency": {
      "enum": [
        "high",
        "low"
      ],
      "type": "string",
      "title": "Filters  Urgency",
      "description": "Any incidents whose urgency does not match the provided string will be omitted from the results. "
    },
    "filters__team__ids": {
      "type": "array",
      "items": {
        "type": "string",
        "properties": {}
      },
      "title": "Filters  Team  Ids",
      "description": "An array of team IDs. Only incidents related to these teams will be included in the results. If omitted, all teams the requestor has access to will be included in the results. "
    },
    "filters__priority__ids": {
      "type": "array",
      "items": {
        "type": "string",
        "properties": {}
      },
      "title": "Filters  Priority  Ids",
      "description": "An array of priority IDs. Only incidents with these priorities will be included in the results. If omitted, all priorities will be included in the results. "
    },
    "filters__responder__ids": {
      "type": "array",
      "items": {
        "type": "string",
        "properties": {}
      },
      "title": "Filters  Responder  Ids",
      "description": "An array of responder IDs. Only incidents related to these responders will be included in the results. If omitted, all responders the requestor has access to will be included in the results. "
    },
    "filters__priority__names": {
      "type": "array",
      "items": {
        "type": "string",
        "properties": {}
      },
      "title": "Filters  Priority  Names",
      "description": "An array of user-defined priority names. Only incidents with these priorities will be included in the results. If omitted, all priorities will be included in the results. "
    },
    "filters__date__range__end": {
      "type": "string",
      "title": "Filters  Date  Range  End",
      "description": "Accepts an ISO8601 DateTime string. Any incidents with a created_at greater than or equal to this value will be omitted from the results. The maximum supported time range in conjunction with date_range_start is one year. "
    },
    "filters__date__range__start": {
      "type": "string",
      "title": "Filters  Date  Range  Start",
      "description": "Accepts an ISO8601 DateTime string. Any incidents with a created_at less than this value will be omitted from the results. The maximum supported time range in conjunction with date_range_end is one year. "
    }
  }
}