nano SIEM
Integrations

OpenTelemetry (OTLP)

Supported in:Self-hosted

Send OpenTelemetry logs, traces and metrics to nano over OTLP/HTTP with an ingest token, and where each signal is stored

Send OpenTelemetry data to nano over OTLP. Logs are parsed and stored as OCSF events you can search. Traces and metrics go to their own ClickHouse tables and feed the Observability pages; they are not normalized to OCSF.

Self-runOpen core
OTLP/HTTP endpointhttps://<ingest-host>/otlp/v1/{logs,traces,metrics}http(s)://<host>/otlp/v1/{logs,traces,metrics} through nginx
EncodingProtobuf only: Content-Type: application/x-protobuf, gzip allowedSame
AuthAuthorization: Bearer <token> (an ingest token)Authorization: Bearer <token>
Raw OTLP portsNot exposedgRPC :4317, HTTP :4318, no token, bound to 127.0.0.1 by default

Every /otlp request is checked against the token's current state, with no cache, so a revoked token stops working on the next request. The edge replaces any identity header the sender sent with the verified one, so OTLP logs land in the token's source and that source's parser runs. Bind the token to the OpenTelemetry logs source (otlp_log, parsed by opentelemetry_logs into API Activity events, class_uid=6003), or to any other push source whose parser understands your log records. Traces and metrics keep their native signal types whatever source the token is bound to.

Search OTLP logs with:

metadata.log_source="otlp_log" | head 20

See Supported sources.

OTLP/HTTP accepts protobuf only. OTLP/JSON isn't supported: from v2.0.8 the /otlp edge answers 415 Unsupported Media Type with a message, and earlier releases answered 500. Set your exporter to the http/protobuf protocol: the Collector's otlphttp exporter with encoding: proto (its default), or OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf for an SDK sending directly. OTLP over gRPC is only on the raw port described below.

Send OTLP

OpenTelemetry Collector

exporters:
  otlphttp/nano:
    endpoint: https://<ingest-host>/otlp
    encoding: proto
    compression: gzip
    headers:
      Authorization: "Bearer ${env:NANO_TOKEN}"

service:
  pipelines:
    logs:
      receivers: [otlp]
      exporters: [otlphttp/nano]

The exporter appends /v1/logs, /v1/traces and /v1/metrics to endpoint. To send one signal only, set logs_endpoint (or traces_endpoint, metrics_endpoint) to the full path instead.

Fluent Bit

[OUTPUT]
    Name        opentelemetry
    Match       *
    Host        <ingest-host>
    Port        443
    Logs_uri    /otlp/v1/logs
    Header      Authorization Bearer ${NANO_TOKEN}
    TLS         On
    TLS.Verify  On

On open core, use your nano host and its port (80, or 443 with the TLS overlay). For Cribl Stream, see Cribl Stream.

Raw OTLP ports (open core)

Vector's opentelemetry source also listens on :4317 (gRPC) and :4318 (HTTP) without a token. The open-core stack binds them to 127.0.0.1; set NANO_OTLP_BIND_ADDRESS in .env to accept them from other hosts.

Where each signal goes

SignalPath through nanoWhere it lands
LogsRouted to the token's source and its parser, like any other push event. trace_id and span_id are kept for correlation.OCSF events in nanosiem.ocsf_logs
TracesOne row per spanThe otel_spans ClickHouse table, in native OTLP shape
MetricsOne row per data pointThe otel_metrics ClickHouse table, in native OTLP shape

Traces and metrics aren't OCSF events, so they don't appear in event search, detections or the OCSF field reference. Open them from Observability, or with the services, trace and metric commands.

Troubleshoot

Need help with these checks? Contact support with the deployment, request ID and time with timezone.

SymptomCauseFix
401Missing, revoked or unbound token, or a token created in the last few secondsSend Authorization: Bearer <token> with an active token bound to a push source. A new token works on every ingest server within a few seconds (each reloads the token list every 2 seconds), so wait about 10 seconds before sending with it.
429 or 503Backpressure, or ingestion is pausedKeep the Collector's sending queue and retry. OTLP/HTTP has no per-sender request-rate limit at the ingest hostname; requests up to 100 MiB are accepted on Self-run.
415 (v2.0.8 and later) or 500 (earlier)The body is OTLP/JSON, or Content-Type isn't application/x-protobufSend protobuf: encoding: proto on the Collector, http/protobuf on an SDK.
404The exporter posts to the app host (Self-run), or to /v1/logs without the /otlp prefixUse https://<ingest-host>/otlp/v1/logs.
Logs land in the wrong sourceThe token decides the sourceUse a token bound to the right source.
Logs land as otlp_log though the token is bound elsewhereThey were sent to a raw OTLP port, not through /otlpSend through /otlp.

What's next

Make each Observability page show data

Logs, traces and metrics are separate signals. Sending logs alone does not create services, traces, host inventory or browser telemetry. Send traces and metrics through /otlp/v1/traces and /otlp/v1/metrics with an ingest token, like logs.

PageSignal to sendRequired identity and measurements
ServicesTracesSet resource service.name; export completed request spans with duration and error status.
TracesTracesKeep valid trace IDs, span IDs and parent IDs for the waterfall.
MetricsMetricsNamed gauge, sum or histogram data points; set service.name to filter by service. Export every 30–60 seconds.
InfrastructureHost metricsResource host.name; system.cpu.utilization and system.memory.utilization as fractions, system.cpu.load_average.1m. Raw node-exporter series are also understood: memory utilization from node_memory_MemAvailable_bytes / node_memory_MemTotal_bytes, load from node_load1, and network rates from physical-interface receive/transmit byte counters. Existing system.* measurements take precedence.
RUMBrowser metrics and/or spansweb.vitals.lcp and web.vitals.inp in milliseconds, web.vitals.cls as a score; pageview spans with attribute page.url. Server request spans alone are insufficient.
SLOsTraces plus a saved SLOThe definition's service must match service.name. A new mirror cannot prove a full historical SLO window: partial coverage is not 100% compliance.
Metric monitorsMetrics plus a saved monitorChoose a metric and filters that receive samples inside the monitor window. No samples means no data, not a zero measurement.

Run this Collector configuration on your trusted application network. Replace <otlp-base> with https://<ingest-host>/otlp (Self-run) or http(s)://<host>/otlp (open core), and NANO_TOKEN with an ingest token. Do not embed ingest credentials in browser code; forward browser telemetry through a trusted collector or application relay.

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 127.0.0.1:4317
      http:
        endpoint: 127.0.0.1:4318
  hostmetrics:
    collection_interval: 30s
    scrapers:
      cpu:
        metrics:
          system.cpu.utilization:
            enabled: true
      memory:
        metrics:
          system.memory.utilization:
            enabled: true
      load: {}
processors:
  resourcedetection:
    detectors: [system]
    system:
      hostname_sources: [os]
  batch: {}
exporters:
  otlphttp/nano-traces:
    traces_endpoint: <otlp-base>/v1/traces
    encoding: proto
    compression: gzip
    headers:
      Authorization: "Bearer ${env:NANO_TOKEN}"
  otlphttp/nano-metrics:
    metrics_endpoint: <otlp-base>/v1/metrics
    encoding: proto
    compression: gzip
    headers:
      Authorization: "Bearer ${env:NANO_TOKEN}"
service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlphttp/nano-traces]
    metrics:
      receivers: [otlp, hostmetrics]
      processors: [resourcedetection, batch]
      exporters: [otlphttp/nano-metrics]

Set OTEL_SERVICE_NAME in each application, point its SDK to the local Collector, and enable both signals in that SDK. Retain TLS and authentication at the network boundary.

After generating traffic, select Last 1 hour in Observability. If a page is empty, check its signal in the table above, the selected filters, Collector export errors and queue depth, and the token. Retryable 429/503 responses indicate backpressure or delayed delivery; retain the Collector's queue and retry. A metric name can remain in the catalog after its recent samples have stopped.

On this page