Quickstart

Connect your OpenTelemetry Collector to Logpathio and start seeing correlated signals in 5 steps. Estimated time: 10-15 minutes for an existing OTEL deployment.

Prerequisites

OpenTelemetry Collector v0.90+ installed (see OTEL Collector docs)
A Logpathio account with an API key (Get early access)
Services instrumented with any OTEL SDK (or auto-instrumented)

Step 1: Configure OTEL Collector exporter

Add the Logpathio exporter to your OTEL Collector config. Logpathio accepts OTLP over gRPC (port 4317) or HTTP (port 4318).

exporters:
  otlp/logpathio:
    endpoint: "ingest.logpathio.com:4317"
    headers:
      x-lpi-api-key: "${LPI_API_KEY}"
    tls:
      insecure: false

service:
  pipelines:
    traces:
      exporters: [otlp/logpathio, ...]
    metrics:
      exporters: [otlp/logpathio, ...]
    logs:
      exporters: [otlp/logpathio, ...]

Set LPI_API_KEY as an environment variable — don't hardcode it in the config file. Your API key is available in the Logpathio dashboard under Settings → API Keys.

Step 2: Kubernetes DaemonSet deployment

For Kubernetes environments, deploy the OTEL Collector as a DaemonSet so each node has a local collector. Services export to localhost:4317.

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: otel-collector
  namespace: observability
spec:
  selector:
    matchLabels:
      app: otel-collector
  template:
    metadata:
      labels:
        app: otel-collector
    spec:
      containers:
      - name: otel-collector
        image: otel/opentelemetry-collector-contrib:0.96.0
        args: ["--config=/conf/otel-collector-config.yaml"]
        env:
        - name: LPI_API_KEY
          valueFrom:
            secretKeyRef:
              name: logpathio-credentials
              key: api-key
        volumeMounts:
        - name: otel-config
          mountPath: /conf
      volumes:
      - name: otel-config
        configMap:
          name: otel-collector-config

Step 3: Configure tail-based sampling

Tail-based sampling ensures you always capture traces with errors. Add the tail_sampling processor before the exporter in your pipeline.

processors:
  tail_sampling:
    decision_wait: 10s
    num_traces: 100000
    policies:
      - name: errors-policy
        type: status_code
        status_code: {status_codes: [ERROR]}
      - name: latency-policy
        type: latency
        latency: {threshold_ms: 2000}
      - name: base-rate
        type: probabilistic
        probabilistic: {sampling_percentage: 5}

Step 4: Verify ingestion

After deploying the collector, verify data is flowing using the Logpathio CLI or the dashboard.

terminal

$ lpi verify --workspace my-org
✓ API key valid
✓ OTLP endpoint reachable (ingest.logpathio.com:4317)
✓ Traces received: 847 spans (last 5 min)
✓ Metrics received: 12,439 data points (last 5 min)
✓ Logs received: 3,201 events (last 5 min)
✓ Correlation engine: active
All checks passed. Logpathio is receiving your telemetry.

Step 5: Open the correlation view

Log into the Logpathio dashboard. The correlation view shows your service topology with real-time signal overlays. During a live incident, this view updates every 30 seconds and surfaces the earliest-anomaly service automatically.

For programmatic access to correlation results, see the Correlation Query API.

← Previous Overview Next → API Reference