Connect OTLP/HTTP or an OpenTelemetry Collector and keep your telemetry standards-based from day one.
Bring OTLP traces, spans, metrics, logs, infrastructure context, AI spans, custom attributes, and workflow identifiers into the same investigation record.
Traces, spans, metrics, and logs
Agent, model, tool, and application spans
Kubernetes, infrastructure, backend, and service context
Latency, errors, evals, cost, and custom attributes
Business process events and workflow identifiers
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.
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.anosys.ai/otel
OTEL_SERVICE_NAME=checkout-agent
OpenTelemetry docs
This page is for teams that want OpenTelemetry, but AnoSys also supports SDKs, REST APIs, JavaScript, pixels, files, and cloud storage.
Yes. You can control what attributes and payloads are sent and combine OpenTelemetry with AnoSys enterprise security controls.
Yes. Cost can be sent as telemetry attributes or captured through supported LLM and agent integrations.
Yes. Tool calls can be represented as spans with tool name, latency, success, failure, and result metadata.
Yes. OpenTelemetry data can be governed with enterprise access, audit, and sensitive data controls.