Get issues — GET /v1/o11y/sentinel/issues/{id}

Returns one grouped issue of the caller's org with its latest occurrence sample.

GET /v1/o11y/sentinel/issues/{id}

O11y → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/o11y/sentinel/issues/{id}`
Method	`GET`
Operation	`get_o11y_sentinel_issues_by_id`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Returns one grouped issue of the caller's org with its latest occurrence sample.

Callers need the viewer role; the runtime's own gate enforces it.

Request

1 field.

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the issue id.

Response

Status	Body	Meaning
`200`	o11y.O11yErrorGettableIssueOut	ok
`202`	Approval	held for approval
`default`	problem-details	refused

200 body — 53 fields.

Field	In	Type	Always	Description
`data`	body	o11y.O11yErrorGettableIssue	—
`data.issue`	body	o11y.O11yErrorIssue	—
`data.issue.assignee`	body	string	—	Assignee is who the issue is assigned to.
`data.issue.count`	body	integer (int64)	—	Count is how many occurrences have landed on the issue.
`data.issue.createdAt`	body	string (date-time)	—	CreatedAt is when the issue was first recorded.
`data.issue.culprit`	body	string	—	Culprit is where it came from — the function or route blamed for it.
`data.issue.environment`	body	string	—	Environment is the deployment the issue was seen in.
`data.issue.fingerprint`	body	string	—	Fingerprint is the grouping key that puts like errors in one issue.
`data.issue.firstSeen`	body	string (date-time)	—	FirstSeen is when the earliest occurrence was recorded.
`data.issue.id`	body	string	—	ID is the issue id.
`data.issue.lastSeen`	body	string (date-time)	—	LastSeen is when the latest was.
`data.issue.level`	body	string	—	Level is the issue's severity, e.g. error, warning, info.
`data.issue.platform`	body	string	—	Platform is the reporting runtime, e.g. go, python, javascript.
`data.issue.regressed`	body	boolean	—	Regressed marks an issue that reopened after being resolved.
`data.issue.release`	body	string	—	Release is the version that produced it.
`data.issue.resolvedAt`	body	string (date-time)	—	ResolvedAt is when the issue was resolved, if it is.
`data.issue.serviceName`	body	string	—	ServiceName is the service that reported it.
`data.issue.status`	body	string	—	Status is the lifecycle state: unresolved, resolved or ignored.
`data.issue.type`	body	string	—	Type is the exception type.
`data.issue.updatedAt`	body	string (date-time)	—	UpdatedAt is when the issue last changed.
`data.issue.value`	body	string	—	Value is the exception value.
`data.latestEvent`	body	o11y.O11yOccurrence	—
`data.latestEvent.culprit`	body	string	—	Culprit is where it came from.
`data.latestEvent.environment`	body	string	—	Environment is the deployment it happened in.
`data.latestEvent.eventId`	body	string	—	EventID is the occurrence's id.
`data.latestEvent.fingerprint`	body	string	—	Fingerprint is the grouping key it was bucketed by.
`data.latestEvent.frames`	body	o11y.O11yOccurrenceFrame[]	—	Frames are the stack, innermost first.
`data.latestEvent.frames[].absPath`	body	string	—	AbsPath is the file's absolute path.
`data.latestEvent.frames[].colno`	body	integer (int64)	—	Colno is the column number.
`data.latestEvent.frames[].filename`	body	string	—	Filename is the file it is in.
`data.latestEvent.frames[].function`	body	string	—	Function is the function the frame is in.
`data.latestEvent.frames[].inApp`	body	boolean	—	InApp marks a frame in the reporting application's own code.
`data.latestEvent.frames[].lineno`	body	integer (int64)	—	Lineno is the line number.
`data.latestEvent.frames[].module`	body	string	—	Module is the module the function is in.
`data.latestEvent.level`	body	string	—	Level is its severity, e.g. error, warning, info.
`data.latestEvent.platform`	body	string	—	Platform is the reporting runtime.
`data.latestEvent.release`	body	string	—	Release is the version that produced it.
`data.latestEvent.serverName`	body	string	—	ServerName is the host that reported it.
`data.latestEvent.serviceName`	body	string	—	ServiceName is the service that reported it.
`data.latestEvent.spanId`	body	string	—	SpanID is the span it belonged to.
`data.latestEvent.tags`	body	object	—	Tags are the reporter's own key/value labels.
`data.latestEvent.tags.*`	body	string	—
`data.latestEvent.timestamp`	body	string (date-time)	—	Timestamp is when the error happened.
`data.latestEvent.traceId`	body	string	—	TraceID is the trace it belonged to.
`data.latestEvent.transaction`	body	string	—	Transaction is the operation it happened in.
`data.latestEvent.type`	body	string	—	Type is the exception type.
`data.latestEvent.user`	body	o11y.O11yEventUser	—
`data.latestEvent.user.email`	body	string	—	Email is that user's email.
`data.latestEvent.user.id`	body	string	—	ID identifies the affected end user.
`data.latestEvent.user.ipAddress`	body	string	—	IP is that user's address.
`data.latestEvent.user.username`	body	string	—	Username is that user's name.
`data.latestEvent.value`	body	string	—	Value is the exception value.
`status`	body	string	—	Status is "success".

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo o11y sentinel issues get <id>

.ts

.py

.go

.rs

.java

import { Configuration, O11yApi } from 'hanzoai';

const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getO11ySentinelIssuesById({ id: 'id' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import O11yApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = O11yApi(client).get_o11y_sentinel_issues_by_id(id='id')

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.O11yAPI.GetO11ySentinelIssuesById(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, o11y_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = o11y_api::get_o11y_sentinel_issues_by_id(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.O11yApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new O11yApi(client).getO11ySentinelIssuesById();

curl https://api.hanzo.ai/v1/o11y/sentinel/issues/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches o11y through the o11y tool, which names its 307 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_o11y_autocomplete_aggregate_attributes"
         }
       }
     }'

O11y API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList events NextList issues — GET /v1/o11y/sentinel/issues