e-volv

Logs, traces, and the failure graph that explains them

Evolve Observer

Capture from three SDKs or any OpenTelemetry collector, search months of events with a small query language, and let the incident builder name what failed first, how far it spread, and why — then hand it to a playbook.

Capture
3 SDKs

Three SDKs, or any OpenTelemetry collector you already run

Batching, backoff, client-side redaction and drop-oldest under quota, so instrumenting a service never blocks it.

JavaScript / TypeScript

0.1.1
npm install @e-volv/logs

Python

0.1.0
pip install e-volv-logs

Go

v0.1.0
go get github.com/Pactify-Pty-Ltd/e-volv-logs-go

Edge runtimes

`@e-volv/logs/edge` ships in the same package — a fetch-only client for Cloudflare Workers, Vercel Edge and Deno Deploy, where the Node entry cannot run.

Read the docs

OpenTelemetry

OTLP/HTTP ingest from any collector you already run, so a team with existing instrumentation adopts Observer without touching a service.

Read the docs
Search

A query language, not a search box

Level filters, service and attribute matches and full-text phrases over months of events — with live tail over SSE when you would rather watch than query.

Searching months of events with the query language
Errors

Thousands of errors, grouped into the few that matter

Fingerprinted as they land — not on a schedule, and not only when someone opens the page. Merge, split, and an alert when a group you fixed comes back.

Error groups, with their counts and first and last seen
Incidents

One incident, not forty alerts

The builder walks the failing traces, finds the deepest failing spans with no failing child, ranks the roots, and reverses the call graph to work out who else was hit.

The hub graph — how a failure travelled between services
01

Capture

An SDK batches and backs off, redacts at the client, and drops oldest under quota rather than blocking your process. OTLP/HTTP works too, from any collector you already run.

02

Store

Events land in TimescaleDB hypertables with a server-side redaction backstop, compression, and tiered retention: 30 days hot, 90 tiered, 180 for traces and incidents.

03

Group

Every error event and failed span is fingerprinted into an error group as it arrives — not on a schedule, and not only when someone opens the page.

04

Explain

On a burst, the builder finds the deepest failing spans with no failing child, ranks candidate roots, computes observed and predicted blast radius, and an agent writes the explanation.

05

Act

Hand the incident to a playbook — incident-response or auto-root-cause-analysis — and the rest of Evolve takes it from there. That hand-off is why Observer lives inside a control plane rather than beside one.

In the product
8 surfaces

Eight surfaces, one workspace

The same list the product's own side nav carries, in the same order — so this page cannot advertise a screen the app does not have.

Projects

A project per application or service, each with its own key, quota and retention, pooled under one workspace.

Search

A deliberately small query language — level filters, service and attribute matches, full-text phrases — over months of events, not a search box over the last hour.

Tail

Lines as they arrive, streamed over SSE, in the app or from the CLI. The same view at a desk or in a terminal.

Dashboards

Volume, error rate and p95 latency read from per-minute continuous aggregates, so a chart never scans raw rows.

Errors

Thousands of events fingerprinted into the few groups that matter, with merge, split, and an alert when a fixed group comes back.

Incidents

When errors burst, the builder walks the failing traces, ranks the roots by trace share and onset order, and reverses the call graph to compute the blast radius.

Hub

Every project in the workspace on one service graph, sized by volume and bordered by error ratio — where a failure travelled, not just where it landed.

Usage

What you are ingesting, by project, against the quota — before the invoice, not after it.

Price
$300 per user / year

$30 per user / month

Log and trace management for one workspace: capture from the SDKs or OTLP, search with a query language, dashboards, error groups, and incident root-cause analysis. No free version — included with Studio.

  • 50 log projects per workspace
  • 25 GB / month ingest, pooled across projects
  • Tail, search, query language and saved queries
  • Dashboards: volume, error rate, p95 latency
  • Error groups with merge, split and regressions
  • Incidents: failure graph, root cause, affected services
  • AI incident explanations and playbook hand-off
  • OTLP ingest, query API, CLI and MCP server
  • Alert rules and SLOs on log queries
  • Buy on its own or alongside any plan