Quickstart

Connect your first service and see root cause analysis results in under 10 minutes.

1 — Create your account

Go to devloomx.com/register and sign up with your work email. No credit card required — Starter tier is free.

After confirming your email you'll land in the onboarding wizard. Choose your primary stack: Prometheus/Grafana, OTEL, or Custom (HTTP POST). This determines the default ingestion endpoint shown in your workspace.

2 — Connect your first source

Each workspace has a unique ingestion endpoint and bearer token. Find them at Settings → Ingestion.

Prometheus remote_write

Add this block to prometheus.yml:

remote_write:
  - url: https://ingest.devloomx.com/v1/metrics/<workspace-id>
    bearer_token: <your-token>
    remote_timeout: 30s
    queue_config:
      max_samples_per_send: 5000

Reload Prometheus: kill -HUP $(pidof prometheus) or via your systemd unit.

OpenTelemetry Collector

Add a Devloom exporter to your otel-config.yaml:

exporters:
  otlphttp/devloom:
    endpoint: https://ingest.devloomx.com/v1/otel/<workspace-id>
    headers:
      Authorization: Bearer <your-token>

service:
  pipelines:
    metrics:
      exporters: [otlphttp/devloom]
    logs:
      exporters: [otlphttp/devloom]
    traces:
      exporters: [otlphttp/devloom]

3 — Verify ingestion

In your workspace, go to Ingestion → Status. You should see a green indicator and metrics count climbing within 60 seconds of reloading your Prometheus or OTel collector.

Confirm using the CLI check command:

# Install the Devloom CLI
npm install -g @devloom/cli

# Authenticate
dlm auth login

# Verify last 5 minutes of ingestion
dlm ingestion verify --window 5m

You'll see output like:

Workspace:  my-workspace (ws_abc123)
Metrics:    14,822 series ingested in last 5m
Logs:       38,100 lines ingested in last 5m
Status:     HEALTHY

4 — RCA configuration

Devloom starts correlating immediately after ingestion begins. Default settings work for most services. You can tune:

  • Confidence threshold (default 0.72): minimum correlation score before flagging a root cause candidate. Higher = fewer but more precise results.
  • Blast radius depth (default 2): how many dependency hops to trace when a cause is identified. Increase for deeply nested microservices.
  • Causal model: choose between ml-correlation (default), rule-based, or hybrid.

Configure via Settings → RCA Engine or with the CLI:

dlm config set rca.confidence_threshold 0.80
dlm config set rca.blast_radius_depth 3
dlm config set rca.model hybrid

5 — Remediation

When Devloom identifies a root cause with high confidence, it generates a remediation diff — a concrete set of config/code changes to resolve the issue.

To use one-click remediation, connect your deployment pipeline under Settings → Integrations → CI/CD. Supported: GitHub Actions, GitLab CI, ArgoCD.

Each remediation includes:

  • Root cause summary with confidence score and evidence trail
  • Suggested config diff (yaml / HCL / shell depending on the affected system)
  • Expected impact after applying (estimated MTTR reduction)
  • One-click apply or export as runbook markdown

Account & billing

Devloom plans are based on connected service count — the number of distinct named services emitting telemetry to your workspace. Log lines, spans, and metric series volume don't count against your limit.

Plan Service limit Retention Seats Price
Starter 3 services 7 days 1 Free
Pro 25 services 30 days 5 $49/mo
Team 100 services 90 days Unlimited $199/mo

Upgrade at any time from Settings → Billing. Downgrades take effect at your next billing cycle. Annual billing saves 2 months (equivalent to ~17% discount). No contracts on any plan.

API reference →