Delivery you can rely on
- Logs are acknowledged only after they are durably queued
- If storage is unavailable, logs wait in the queue and are delivered when it recovers
- At-least-once delivery
Early access · Logs, traces and metrics
Send logs, traces and metrics with the tools you already use. Search for anything, and Logthread shows every related event across your services as one timeline, with the first error pinned.
Free plan during early access. Data stored in India.
Product
Search any field without designing labels or indexes up front.
Search for anything. Logthread pulls every related event, across all services, that shares the matched lines' correlation ids, and lays them out as a per-request timeline. The first error is pinned, with a one-line summary.
Live tail streams from Logthread's own ingest pipeline. Pause it, or filter by service, severity or text.
Patterns groups repeated log lines into templates and shows how each one trends.
How it works
Sign up and create a key in onboarding. Keys are write-only and shown once.
Use OpenTelemetry, Fluent Bit, Vector, rsyslog or plain curl. Onboarding gives you copy-paste snippets.
Find any line, then see every related event across your services, in order.
curl -X POST 'https://<your-ingest-endpoint>/v1/ndjson' \
-H "Authorization: Bearer $LOGTHREAD_INGEST_KEY" \
-H 'Content-Type: application/x-ndjson' \
--data-binary $'{"service":"my-app","severity":"INFO","body":"Hello, Logthread"}\n'
export OTEL_SERVICE_NAME="my-app"
export OTEL_EXPORTER_OTLP_ENDPOINT="https://<your-ingest-endpoint>"
export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer%20$LOGTHREAD_INGEST_KEY"
Your endpoint and key appear in onboarding after sign-up.
Delivery, security and data
Ingest keys can send logs, traces and metrics, never read them.
Your logs, traces and metrics are stored in the Mumbai region.
Integrations
Use the open standards you already run. Onboarding has copy-paste snippets for each.
Available today
Everything here is built and running in every workspace during early access.
Search any field with facets, a draggable severity histogram, formatted JSON and surrounding context.
Every related event across services, grouped by correlation id, as one timeline with the first error pinned.
Stream logs as they arrive, filtered by service, severity or text.
Repeated lines grouped into templates, with trends and new-pattern detection.
New-pattern, error-spike, scheduled-query, metric-threshold and span-latency rules, delivered to email, Slack, Teams, Discord, PagerDuty, Opsgenie, FireHydrant, webhooks and 90+ more services, each linking to its evidence.
Parse, filter, sample, deduplicate and route logs before they are stored, with live before/after preview, versions and rollback.
Mask cards, Aadhaar, PAN, emails, phone numbers and secrets in logs at ingest, before storage.
OTLP over HTTP and gRPC for logs, traces and metrics, Prometheus remote write 2.0, JSON lines, syslog over TLS and Fluent Forward over TLS.
Plug-and-play LiveKit server, SIP and Cloud: signed webhooks, Prometheus metrics, logs and agent log drains, grouped by room into one story, with ready-made dashboards.
Ingest by signal, storage and query usage per workspace, daily charts, CSV export and limit warnings.
Write-only ingest keys, roles, invitations, session management and an audit log.
Retention settings and workspace deletion with a grace period.
Send OpenTelemetry traces and metrics, or Prometheus remote write, with the same key. Trace waterfalls linked to their logs, and a metrics explorer with rates and percentiles.
Dashboards of log, metric and trace panels with a shared time range, service filter, auto-refresh and templates.
Read-only SQL over your logs, spans and metrics, with a schema browser, parameters, charts and saved queries.
Download logs, traces, metrics or any SQL result as NDJSON or Parquet, streamed with no row limit.
Manage your OpenTelemetry Collectors from Logthread over OpAMP: live inventory and health, versioned configs targeted by labels, rollout status and one-click rollback.
On the roadmap
These are plans, not features you can use today. Scope and order may change.
Re-ingest a time range from the archive through a pipeline.
Forward logs to other tools such as Splunk, Datadog, Elastic and S3.
FAQ
Nothing from Logthread. You send logs, traces and metrics with standard tools and a Logthread ingest key: OpenTelemetry SDKs and zero-code instrumentation (Node.js, Python, Java, Go, .NET), the OpenTelemetry Collector over OTLP HTTP or gRPC, Prometheus remote write, Fluent Bit, Vector, rsyslog, or plain JSON lines with curl. On Kubernetes, use the OpenTelemetry Collector Helm chart. Onboarding has copy-paste snippets for each.
Logthread is fully managed: there is nothing for you to run or operate. Your data is stored in India, in the Mumbai region. On the free plan, data is kept for 7 days during early access.
Logs are acknowledged only after they are durably queued. If storage is unavailable, logs wait in the queue and are delivered when it recovers. Delivery is at-least-once.
During early access there is a free plan: currently 1 GB/day of ingest, 7-day retention and up to 3 members. These limits may change. Paid plans and pricing will be published before general availability.
Yes. Invite people by email and give each one a role: owner, admin, member or viewer. The free plan allows up to 3 members during early access.
Early access
Logthread is in early access, with a free plan you can sign up for yourself.