Use REST when you need to instrument internal systems, queues, batch jobs, product events, or business workflows that do not emit OpenTelemetry.
Send structured HTTP events for custom telemetry that does not fit a standard collector: evals, costs, workflow state, owners, SLAs, and business outcomes.
Custom AI and application events
Business process and outcome events
Eval scores, policy results, and quality signals
Cost, latency, errors, and owner context
Workflow, team, user, customer, and SLA attributes
Use the linked guide to install the collector or SDK, verify the endpoint, and send a small trace or event payload. Once data lands, connect it to dashboards, evals, alerts, and investigations.
POST /events
{
"event": "claim.review.completed",
"workflow": "claims-agent",
"outcome": "approved"
}No. REST ingestion is designed for teams that want to send custom telemetry directly over HTTP.
Yes. Send only the fields you need, redact payloads before ingestion, and use enterprise sensitive data controls.
Yes. Include token usage, dollar cost, model name, workflow, team, or any custom cost attribution fields.
Yes. Tool calls can be sent as events or spans with latency, success, failure, and result metadata.
Yes. REST-ingested data can be governed with the same enterprise controls as other AnoSys telemetry.