Everr - Every second counts in CI/CD

Overview

The Everr CLI can run a local OpenTelemetry Collector that receives OTLP over HTTP and stores data in a local chDB database. Everr Desktop starts the same collector through its bundled CLI, so the standalone CLI and app use the same local telemetry path.

Any locally running service or app you instrument with OpenTelemetry and point at the local collector will be visible to these commands.

Commands

`everr local start`

Starts the local collector in the foreground.

everr local start

Keep this command running while your local service exports telemetry. Stop it with Ctrl+C.

Useful flags:

--quiet — suppress collector URL output after startup.

`everr local status`

Checks whether the local collector healthcheck is reachable.

everr local status

It exits with code 0 when the collector is running and code 2 when it is stopped.

`everr local query`

Runs read-only SQL against local telemetry.

everr local query "SELECT Timestamp, ServiceName, SpanName FROM otel_traces ORDER BY Timestamp DESC LIMIT 20"

Useful flags:

--format <table|json|ndjson> — default table on TTY, ndjson otherwise.

`everr local endpoint`

Prints the collector URL for the current build.

everr local endpoint

`everr wrap`

Runs a plain command normally and mirrors each stdout/stderr line into the local collector.

everr wrap -- npm run lint

Use this for build and linting tasks that are not OpenTelemetry-instrumented but still need logs in otel_logs. For runtime app debugging, add real OpenTelemetry instrumentation instead. The wrapped command keeps its normal terminal output and exit code, and its logs use service.name = everr-wrap-<cmd>.

The local collector must already be running. If the collector is unavailable, everr wrap exits without running the command. If the wrapped command exits with a non-zero code, everr wrap exits with the same code after forwarding its output and attempting to send its logs.

Pivoting between logs and traces

Find a log of interest, grab its TraceId, and query the matching trace:

everr local query "SELECT Timestamp, TraceId, ServiceName, SeverityText, Body FROM otel_logs WHERE SeverityNumber >= 17 ORDER BY Timestamp DESC LIMIT 1" --format json
everr local query "SELECT Timestamp, SpanName, Duration, StatusCode, StatusMessage FROM otel_traces WHERE TraceId = '<id>' ORDER BY Timestamp ASC"

Everr skills

Everr ships bundled skills for agents that need local telemetry context:

local-telemetry-setup explains how to start the collector and point a local app at it.
local-debugging explains how to query local logs and traces while debugging runtime issues.

everr skills install local-telemetry-setup local-debugging --project

To install every bundled Everr skill instead:

everr skills install --all --project

Use --global when you want the skills available outside the current repository.

Local Telemetry