Aggregates a project's captured errors into a table — the caller names the…
Aggregates a project's captured errors into a table — the caller names the filters, the groupings and the aggregations, and gets back the columns and rows…
POST /v1/o11y/sentinel/discover
| Address | https://api.hanzo.ai/v1/o11y/sentinel/discover |
| Method | POST |
| Operation | post_o11y_sentinel_discover |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Aggregates a project's captured errors into a table — the caller names the filters, the groupings and the aggregations, and gets back the columns and rows they asked for.
The project is mandatory and is checked against the caller's own org before it scopes anything, so a project id belonging to someone else reads as absent rather than as data.
Request
11 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
aggregations | body | string[] | — | Aggregations are the measures to compute per group. |
filters | body | o11y.O11yFilter[] | — | Filters narrow the scan; each is a field, an operator (eq, neq, like) and a value, and they combine with AND. |
filters[].field | body | string | — | Field is the column to test. |
filters[].op | body | string | — | Op is how to test it: eq, neq or like. |
filters[].value | body | string | — | Value is what to test it against. |
groupBy | body | string[] | — | GroupBy are the columns to group the rows by. |
limit | body | integer | — | Limit caps how many rows come back. |
orderBy | body | string | — | OrderBy is the column or aggregation to sort the rows on. |
orderDir | body | string | — | OrderDir is asc or desc. |
period | body | string | — | Period is the window to read, relative to now — 1h, 24h, 7d, 14d, 30d. |
project | body | string | yes | Project is the project to read, as its id. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | o11y.O11yDiscoverOut | ok |
200 body — 4 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | o11y.O11yTable | — | |
data.columns | body | string[] | — | Columns names each position in a row. |
data.rows | body | object[][] | — | Rows are the result rows, each as long as Columns. |
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.postO11ySentinelDiscover({ 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).post_o11y_sentinel_discover(project="<project>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.O11yAPI.PostO11ySentinelDiscover(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::post_o11y_sentinel_discover(&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).postO11ySentinelDiscover();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 -X POST https://api.hanzo.ai/v1/o11y/sentinel/discover \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"project": "<project>"
}'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"
}
}
}'How is this guide?