Returns one captured error event of a project, by its id.

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

O11y → · All API references → · Six flows, four surfaces →


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

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

Request

2 fields.

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the event id.
`project`	query	string	yes	Project is the project the event belongs to, by its id.

Response

Status	Body	Meaning
`200`	o11y.O11ySentryEventOut	ok

200 body — 33 fields.

Field	In	Type	Always	Description
`data`	body	o11y.O11yEvent	—
`data.culprit`	body	string	—	Culprit is where it came from — the function or route blamed for it.
`data.environment`	body	string	—	Environment is the deployment it happened in.
`data.eventId`	body	string	—	EventID is its own id.
`data.fingerprint`	body	string	—	Fingerprint is the grouping key that puts like errors in one issue.
`data.frames`	body	o11y.O11yFrame[]	—	Frames are the stack, innermost first.
`data.frames[].column`	body	integer	—	Column is the column number.
`data.frames[].file`	body	string	—	File is the file it is in.
`data.frames[].function`	body	string	—	Function is the function the frame is in.
`data.frames[].line`	body	integer	—	Line is the line number.
`data.frames[].own`	body	boolean	—	Own marks a frame in the reporting application's own code rather than in a dependency or the runtime.
`data.handled`	body	boolean	—	Handled says whether the application caught it.
`data.level`	body	string	—	Level is its severity, e.g.
`data.message`	body	string	—	Message is the human-readable message.
`data.orgId`	body	string	—	OrgID is the org that owns it.
`data.platform`	body	string	—	Platform is the reporting runtime, e.g.
`data.projectId`	body	string	—	ProjectID is the project it was captured for.
`data.receivedAt`	body	string (date-time)	—	ReceivedAt is when it arrived here.
`data.release`	body	string	—	Release is the version that produced it.
`data.serverName`	body	string	—	ServerName is the host that reported it.
`data.serviceName`	body	string	—	ServiceName is the service that reported it.
`data.spanId`	body	string	—	SpanID is the span it belonged to.
`data.tags`	body	object	—	Tags are the reporter's own key/value labels.
`data.tags.*`	body	string	—
`data.timestamp`	body	string (date-time)	—	Timestamp is when the error happened, as the reporter recorded it.
`data.traceId`	body	string	—	TraceID is the trace it belonged to.
`data.transaction`	body	string	—	Transaction is the operation it happened in.
`data.type`	body	string	—	Type is the exception type.
`data.userEmail`	body	string	—	UserEmail is that user's email, when attached.
`data.userId`	body	string	—	UserID identifies the affected end user, when the reporter attached one.
`data.userIp`	body	string	—	UserIP is that user's address, when attached.
`data.value`	body	string	—	Value is the exception value.
`status`	body	string	—	Status is "success".

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

import { Configuration, O11yApi } from 'hanzoai';

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

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_events_by_id(id='id', project='project')

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

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

use hanzo_cloud::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_events_by_id(&cfg, Default::default()).await?;

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

ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));

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

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

curl https://api.hanzo.ai/v1/o11y/sentinel/events/<id>?project=%3Cproject%3E \
  -H "Authorization: Bearer $HANZO_API_KEY"

The door reaches o11y through the o11y tool, which names its 340 operations with its own verbs — this one among them, under a name only the door 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": "get_o11y_alert_last"
         }
       }
     }'

O11y API · All Hanzo APIs · Interactive reference

Returns one captured error event of a project, by its id.

Request

Response

Examples

On this page