Feature: OTel Native

Standard signals.

Overview

The Nova OTel-native feature accepts telemetry in OpenTelemetry format directly. Customers ship metrics, traces, and logs without conversion; the SDK they already chose keeps working.

• Standard signals. Metrics, traces, logs in OTel format; the modern instrumentation standard, accepted as-is.
• OTLP receiver. gRPC on 4317, HTTP on 4318; the spec-compliant ingestion endpoints.
• Vendor-neutral. Customer SDK choice preserved; switching observability vendors does not require re-instrumentation.
• OpenTelemetry Collector compatible. Drop-in target for an existing Collector pipeline; filtering and routing stay in customer hands.

The approach

The practical approach: OTLP receiver as the default, Collector-compatible pipeline, semantic conventions honoured end-to-end. The team’s discipline produces standards-compliant observability.

• OTLP receiver. Standard ingestion; no Nova-specific protocol; the customer’s tooling already knows how to talk.
• OpenTelemetry Collector pipeline. Customers use the Collector to filter, sample, and route; Nova receives whatever they send.
• Semantic conventions aware. Honours OTel attribute conventions (service.name, http.route); telemetry stays consistent across vendors.
• Documented integration. Per-language setup guides for Java, Python, Node, Go, .NET; reduces time-to-first-trace.
• Document the conventions. Standard attributes per signal published in the docs; supports debugging and audits.

Why this compounds

OTel-native discipline compounds across customers and integrations. Each instrumented service preserves vendor flexibility; the team’s observability surface grows on industry-standard rails.

• Vendor-neutral. Customer choice preserved; switching vendors costs nothing on the instrumentation side.
• Faster customer adoption. No conversion required; copy the OTLP endpoint, ship telemetry, done.
• Better operational fit. Customer Collector pipeline preserved; existing filtering, sampling, and routing rules keep working.
• Institutional knowledge. Each integration teaches OTel patterns; the team’s observability muscle grows on standards.

OTel-native discipline is an infrastructure investment that pays off across years. Nova AI Ops integrates with OTel as a first-class surface.