Use the full traces URL
Exporters add /v1/traces only to the generic OTEL_EXPORTER_OTLP_ENDPOINT. Set OTEL_EXPORTER_OTLP_TRACES_ENDPOINT or the exporter’s own URL option.
Send your application’s recorded executions to Mibo through OpenTelemetry. Evaluate the responses and actions captured in each trace against checks you configure.
Send traces straight to Mibo, or keep your current backend, such as Langfuse, Datadog or LangSmith, and add Mibo through a Collector. The examples below show both setups.
Use OTLP over HTTP with protobuf (recommended) or JSON. Replace the API key placeholder before sending. The documentation covers SDK-specific configuration.
Point the instrumentation you already have at Mibo. Each example sets the full traces URL, your API key and the service name.
Exporters add /v1/traces only to the generic OTEL_EXPORTER_OTLP_ENDPOINT. Set OTEL_EXPORTER_OTLP_TRACES_ENDPOINT or the exporter’s own URL option.
node_call checks match span names. Reply and tool-call checks read gen_ai.output.messages or gen_ai.response.text, and gen_ai.tool.name.
Their documentation records content with OTEL_SEMCONV_STABILITY_OPT_IN=gen_ai_latest_experimental and OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT=span_only. Mibo has not verified these end to end.
Lower the batch size if a request is rejected as too large.
Export an execution as OTLP/HTTP protobuf or JSON. Include the response and actions your checks need.
Select a completed trace. AI drafts a test from its available evidence; review and save the suggested checks.
Send more traces and inspect the results of your configured checks.
Follow exporter configuration, supported fields, batching, and troubleshooting guidance.
Open OTLP docsUnderstand how incoming traces are evaluated asynchronously in production.
Explore production testingTest n8n workflows with the verified Mibo node, on n8n Cloud or self-hosted.
Explore n8n integration