VerOps
Get started
PlatformObserve

Logs and metrics

Logs and metrics arrive over OpenTelemetry and are stored in ClickHouse beside your traces. Search logs by text and filter them by service, level and time; chart metrics by label; and use SQL when a question needs more than a filter.

Get started Read the documentation
Ingest
OTLP logs and metrics over HTTP
Store
ClickHouse, per organisation
Long ranges
5-minute, 30-minute and daily rollups
Query
Explorers, dashboards, SQL, API

Logs

  • Search and filter

    Search log messages by text, then narrow by service, severity level and time range.

  • From a log line to its trace

    When a log record carries a trace ID, open the trace from the log row and see the request around the message.

  • Export

    Download the current result set as CSV, with timestamp, level, service, message, trace ID and host.

  • Host log files on request

    The machine agent can read a log file on a host when the platform asks, with regex filtering and size limits, so you can look at a file that is not shipped anywhere.

    Documentation

Metrics

  • Metrics Explorer

    Pick a metric, filter and group by its labels, and save the chart as a dashboard widget.

  • Rollups for long time ranges

    Samples are also aggregated into 5-minute, 30-minute and daily rollups, so a chart covering weeks or months reads far less data.

  • Data Explorer

    Build a query visually or write SQL against your own telemetry, chart the result, export it to CSV and share a permalink.

    Documentation

  • Cloud metrics

    Pull AWS CloudWatch and Azure Monitor metrics into the same store, so cloud resources sit on the same dashboards as your services.

    Documentation

Control what you keep

  • Ingestion filters

    Drop noisy logs, spans or metrics at the gateway before they are stored. Rules are set per organisation under Settings.

  • API keys per source

    Create, rotate and revoke ingest keys. Keys are stored as hashes and shown once.

  • Read it back over the API

    The public API reads metrics, logs, alerts and inventory, and accepts your own custom metrics and events.

    Documentation

  • Resource attributes

    Standard OpenTelemetry attributes such as service.name, host.name and k8s.* decide whether data shows up as a service, a server, a container or a pod.

    Documentation

How data gets in

  1. 01

    Create an API key

    Under Settings, then API keys. The key identifies your organisation, so you never send a tenant ID.

  2. 02

    Point OpenTelemetry at VerOps

    Any OpenTelemetry SDK or Collector works. Use OTLP over HTTP with protobuf or JSON.

    OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.verops.io
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS=authorization=Bearer%20$VEROPS_INGEST_KEY
  3. 03

    Check it arrived

    Open Logs or Metrics Explorer and filter by your service name. Collector recipes cover hosts, containers and Kubernetes.

Documentation

Read more in the docs

Try it on your own systems

Create a workspace, or tell us about your environment and we will walk you through it.

Get started Talk to sales