Trace requests across Blocks and your services

Logs, traces and usage metrics for Blocks services and your own, plus uptime checks with email alerts.

Logs, traces, metrics and uptime in one place

Traces across services

Follow one request through every service it touched on a timeline of spans, and jump from a span to the logs it wrote.

Searchable logs

Filter by date and level, search the text, and open the trace a log line belongs to.

Usage metrics

Request counts, errors and average response times for the authentication, IAM, storage and MFA services.

Uptime monitors

Check a URL with HEAD, GET or POST on an interval, or have your job call a heartbeat URL. See 24-hour health bars, uptime over 7, 30 and 365 days, and incidents, with email alerts to the people you choose.

Your own services too

Register a service and add the Blocks package for .NET, Python or Node, and its logs and traces appear next to the Blocks services. It uses OpenTelemetry and works alongside Serilog or NLog.

Ask AI

Ask a question about the logs, traces or metrics on screen and get an answer in plain language.

Bring your own services in

Blocks services report without setup. Your own services report once they're registered and have the package installed.

  1. Register the service

    Add it under My Services in Secrets & Configs to get its credentials.

  2. Install the package

    Add the Blocks package from NuGet, PyPI or npm. It sends OpenTelemetry logs and traces in batches, with retries.

  3. Add uptime monitors

    Create request or heartbeat monitors for your endpoints and choose who gets the email when one fails.

# Uptime monitors for a deployed repository
blocks release monitor list --repo <name|id> --json

Packages and standards

  • OpenTelemetry
  • NuGet (.NET)
  • PyPI (Python)
  • npm (Node)
  • Serilog
  • NLog

Questions about Monitor

Do my own services show up automatically?

No. Register the service under My Services and add the Blocks package for .NET, Python or Node. After that its logs and traces appear with the Blocks services.

What can an uptime monitor check?

A request monitor calls a URL with HEAD, GET or POST on an interval, with a timeout that defaults to 30 seconds. A heartbeat monitor waits for your job to call its URL and alerts you when the call doesn't come.

How are alerts sent?

By email, to the recipients you list on each monitor.

Which metrics are there?

Request counts, error counts and average response times for the Blocks authentication, IAM, storage and MFA services.

Start with a free project

Sign up at os.seliseblocks.com and create a project, or paste one prompt into Claude Code, Codex or Cursor and let your agent set it up through the Blocks CLI.