Incident Metrics - Personal Dimension
DevelopingPOST
/insight/incident/metrics/responderRequest
Timestamp in seconds, incident trigger time must be greater than this
Timestamp in seconds, incident trigger time must be less than or equal to this. Maximum time span is 6 months, if aggregate_unit is day, maximum time span is 31 days.
Default timezone Asia/Shanghai, used for results and grouping timezone. Must be in tzdata format. Please refer to this list for acceptable values.
Member ID list
Sort field, continuously adding
Result sort order; true means ascending, false means descending, default is descending.
Time unit for aggregating metrics. If no value provided, metrics will be aggregated for the entire period.
If yes, metrics will be aggregated by work time, rest time and sleep time
{
"start_time": 0,
"end_time": 0,
"team_ids": [
0
],
"channel_ids": [
0
],
"severities": [
"Info"
],
"time_zone": "string",
"responder_ids": [
"string"
],
"order_by": "total_incident_cnt",
"asc": true,
"aggregate_unit": "day",
"split_hours": true
}
Request samples
Responses
Total time spent by responders participating in incident processing. One person's processing time is the time difference from acknowledgment to incident closure (close_time-ack_time), may include snooze time. If no one acknowledges, this value is 0.
Triggered incident count
Acknowledged incident count
Reassigned incident count
Average processing time. One person's processing time is the time difference from acknowledgment to incident closure (close_time-ack_time), may include snooze time. If no one acknowledges, this value is 0.
Average first acknowledgment time (ack_time-start_time).
Timestamp in seconds, whether to display depends on if data is aggregated by time granularity. When aggregate_unit is day, this value will be set to timestamp of day start (00:00) according to time_zone
Work time (workdays 8am~7pm)
Member ID
Member name