Skip to content

observe_issues_histogram

Count the events of an error tracking issue per bucket over a window, so a reader can see when it started and whether it is still going.

Tool

observe_issues_histogram

Count the events of an error tracking issue per bucket over a window, so a reader can see when it started and whether it is still going.

Count the events of an error tracking issue per bucket over a window, so a reader can see when it started and whether it is still going. Bucket width is derived from the window; quiet buckets come back as zeros, never as gaps.

Behavior

HTTP
GET /observe/issues/:id/histogram

Arguments

Name
Type
Required
Description
id
string
•
Identifier of the issue
window
string
—
How far back to count, e.g. "1h", "24h", "7d". Up to 30d, default "24h"

Response

Field
Type
Always
Description
to
string
•
ISO 8601 end of the last bucket, exclusive
from
string
•
ISO 8601 start of the first bucket
window
string
•
The window that was counted, e.g. "24h"
buckets
array
•
Every bucket of the window, oldest first. Quiet buckets are zeros, never gaps
bucketSeconds
number
•
Width of one bucket in seconds, derived from the window

Try it

Count the events of an error tracking issue per bucket over a window, so a reader can see when it started and whether it is still going.

When to use

Count the events of an error tracking issue per bucket over a window, so a reader can see when it started and whether it is still going. Bucket width is derived from the window; quiet buckets come back as zeros, never as gaps.

Example

Ask your agent something like this:

Count the events of an error tracking issue per bucket over a window, so a reader can see when it started and whether it is still going.

The agent will invoke observe_issues_histogram with these arguments:

{
  "id": "<id>"
}

Esc

Start typing to search the docs.

↑↓navigate↵select