Send any event over HTTP
Send structured events over HTTP
Use REST when you need to instrument internal systems, queues, batch jobs, product events, or business workflows that do not emit OpenTelemetry.
Questions this answers
- Instrument systems that do not have an SDK yet
- Connect business events to AI behavior and system telemetry
- Build process monitoring from custom operational events
- Route anomalies and alerts from HTTP event streams
- Attach owner, customer, SLA, and workflow context to custom events
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
Start with the docs
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"
}Where to go next
Does this require OpenTelemetry?
No. REST ingestion is designed for teams that want to send custom telemetry directly over HTTP.
Can I redact content?
Yes. Send only the fields you need, redact payloads before ingestion, and use enterprise sensitive data controls.
Can I track cost?
Yes. Include token usage, dollar cost, model name, workflow, team, or any custom cost attribution fields.
Can I monitor tool calls?
Yes. Tool calls can be sent as events or spans with latency, success, failure, and result metadata.
Can I use this with enterprise security controls?
Yes. REST-ingested data can be governed with the same enterprise controls as other Anosys telemetry.