Summarize Processing Failures

Returns aggregate counts for Event recovery rows. Use this endpoint to build the summary cards in the recovery workbench.

GET /v1/projects/:project_id/usage/unconsumed-events/summary

Authentication

Authorization: Bearer <api-key>

Requires usage read access.

Path Parameters

Field	Required	Description
project_id	Yes	Project that owns logs.

Request Body

Empty. This GET endpoint accepts filters only through query parameters.

Query Parameters

Field	Required	Description
raw_event_id	No	Filter to one source raw event.
subject_type	No	Filter by extracted subject type.
subject_id	No	Filter by extracted subject ID.
reason_code	No	Filter by recovery reason code.
start_time	No	Start time as Unix seconds, processed_at.
end_time	No	End time as Unix seconds, processed_at.

Example

curl 'http://127.0.0.1:8080/v1/projects/proj_gateway/usage/unconsumed-events/summary?reason_code=processing_failed&start_time=1778580000&end_time=1778666400' \
  -H 'Authorization: Bearer <api-key>'

Response

{
  "total_count": 12,
  "reason_counts": [
    {
      "value": "processing_failed",
      "count": 9
    }
  ],
  "subject_type_counts": [
    {
      "value": "user",
      "count": 7
    }
  ],
  "extractor_rule_set_counts": [
    {
      "value": "ers_llm_gateway",
      "count": 5
    }
  ]
}

Notes

• Counts are grouped by the stored failure-log columns.
• Use List Processing Failures for the row-level table.