TraceLoop

Integrations

If it emits telemetry, TraceLoop speaks its language.

OpenTelemetry-native ingest, plus 120+ first-party connectors across infrastructure, databases, messaging, languages, alerting and CI/CD. Bring any SDK — or let our agents instrument your stack with zero code changes.

Read Documentation Contact Engineering

Integration Catalog

120+ connectors, six families

Every connector ships with curated dashboards, alert rules and runbook links. Installation is a token and a config block — no bespoke exporters.

Infrastructure

8+
  • ▸Kubernetes
  • ▸Docker
  • ▸AWS EC2
  • ▸Azure VMs
  • ▸GCP Compute
  • ▸Terraform
  • ▸Ansible
  • ▸Nomad

Databases & Storage

8+
  • ▸PostgreSQL
  • ▸MySQL
  • ▸MongoDB
  • ▸Redis
  • ▸DynamoDB
  • ▸Elasticsearch
  • ▸S3
  • ▸ClickHouse

Messaging & Streaming

8+
  • ▸Kafka
  • ▸RabbitMQ
  • ▸SQS
  • ▸SNS
  • ▸NATS
  • ▸Pulsar
  • ▸MQTT
  • ▸EventHub

Languages & Frameworks

8+
  • ▸Node.js
  • ▸Python
  • ▸Go
  • ▸Java
  • ▸Ruby
  • ▸Rust
  • ▸.NET
  • ▸Elixir

Alerting & Incident

8+
  • ▸PagerDuty
  • ▸Opsgenie
  • ▸Slack
  • ▸Microsoft Teams
  • ▸Jira
  • ▸ServiceNow
  • ▸Zendesk
  • ▸Webhooks

CI/CD & Source Control

8+
  • ▸GitHub
  • ▸GitLab
  • ▸Bitbucket
  • ▸Jenkins
  • ▸CircleCI
  • ▸ArgoCD
  • ▸Buildkite
  • ▸Deploy hooks

OpenTelemetry

OTel in, OTel out — no lock-in, ever

TraceLoop is built on OpenTelemetry wire formats. Your instrumentation belongs to you: export traces, metrics and logs back out via OTLP at any time, at full fidelity.

01

Install or point a collector

Drop in the TraceLoop agent for zero-code instrumentation, or point your existing OpenTelemetry Collector at our OTLP endpoint. mTLS and token auth by default.

02

Tag with resource attributes

service.name, deployment.environment, region — the collector picks up Kubernetes and cloud metadata automatically, so topology builds itself.

03

Verify in the workspace

The integrations health page shows handshake, throughput and dropped-span rates per emitter. First spans typically land inside five minutes.

collector config

opentelemetry-collector · otlp/traceloop exporter

mTLS 
# traceloop-collector.yaml
exporters:
  otlp/traceloop:
    endpoint: otel.eu-west-2.traceloop.io:443
    tls:
      cert_file: /etc/otel/client.crt
      key_file:  /etc/otel/client.key
    headers:
      authorization: "Bearer $TRACELOOP_TOKEN"

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [tail_sampling, resource/k8s]
      exporters: [otlp/traceloop]
    metrics:
      receivers: [otlp, hostmetrics, kubeletstats]
      processors: [filter/preaggregation]
      exporters: [otlp/traceloop]
    logs:
      receivers: [otlp, filelog]
      processors: [redaction/pii]
      exporters: [otlp/traceloop]

Integration Health

Know the state of every emitter

The health page tracks handshake, throughput and dropped telemetry per integration — so a silent agent is itself an alert, not a mystery.

integration health

checkout-platform workspace · 24 emitters · last sync 12s ago

23/24 HEALTHY

  • otel-collector · checkout-platform

    182k spans/min · 41k points/min

    HEALTHY

  • kubernetes · prod-eu-west-2

    312 pods discovered · metadata sync 12s

    HEALTHY

  • pagerduty · traceloop-oncall

    last page delivered 14:28 UTC · ack 2m41s

    HEALTHY

  • github · harbourline/checkout

    deploy markers synced · v2.41.3 flagged

    HEALTHY

  • filelog · legacy-billing-host-04

    no data for 6h · agent unreachable

    SILENT

Missing a connector? Contact Engineering — most requests ship as first-party integrations within a quarter, and the OTLP bridge covers you meanwhile.

Your stack is already compatible

Point a collector, paste a token, watch the topology build itself. That is the whole onboarding.

Explore Platform View Integrations Read Documentation Contact Engineering