01 / Application observability

Runtime logs, shaped for production decisions.

Helio gives teams a structured place to capture application logs, inspect context, and follow failures from signal to root cause without dragging in a heavy observability stack.

Start sending logs Read the docs

level:error service:billing-api trace:req_8QK2

ingest

HTTP + SDK

window

Last 1h

shape

JSON

14:02:18.922errorbilling-apiPayment provider timeout

14:02:18.104infoapi-gatewayRequest completed in 248ms

14:02:17.881warnworkerRetrying queue job

14:02:16.447debugauth-apiJWT claims validated

Selected event

Payment provider timeout

request id: req_8QK2
trace: checkout.flow
metadata: orderId, provider, retryable

Live ingest, search, and incident context in one project workspace.

02 / System shape

One log path. Several ways in.

The product starts simple: receive runtime events, normalize the details, and make the production story searchable. The interface should feel calm because the system underneath is structured.

Project-scoped ingest

Use an API key per project. Helio resolves the owning workspace, default environment, and service context before a log reaches storage.

Runtime streams

Send logs through the SDK, HTTP endpoint, or cloud collectors as the product grows from app code to infrastructure runtime.

Search with context

Filter by level, time, service, environment, request ID, trace ID, user ID, tags, and JSON metadata without leaving the log flow.

Cloud-ready path

Connect deployed services and pull operational logs into the same project view users already understand.

03 / Connection flow

Connect once. Let the logs arrive with shape.

Helio should feel approachable for a solo developer testing an Express app and structured enough for teams moving toward Cloud Run, VM agents, and production services.

Create a project

ready in minutes

express runtimesdk middleware

import express from "express";
import { helioLogger } from "@zynnode/helio/express";

const app = express();

app.use(helioLogger({
  apiKey: process.env.HELIO_API_KEY
}));

app.get("/todos", async (req, res) => {
  const todos = await loadTodos();
  res.json(todos);
});

Create a project

Name the system you want to observe and keep every runtime source attached to that project.

Generate an API key

Use one key for a service, environment, or deployment path so Helio can infer useful defaults.

Send logs

Use the SDK, HTTP endpoint, or connected runtime collector to make events visible in the dashboard.

04 / Investigation surface

The row stays readable. The context stays close.

Incident work usually fails when logs flatten everything into noise. Helio keeps the event, metadata, identity, and trace hints aligned so the next action is obvious.

selected error

14:02:18.922 / billing-api

Payment provider timeout

request id: req_8QK2
trace id: checkout.flow
user id: usr_1048
environment: production

{
  "orderId": "ORD-123",
  "provider": "stripe",
  "retryable": true,
  "route": "POST /checkout"
}

05 / Start small

Runtime logs, shaped for production decisions.

Payment provider timeout

One log path. Several ways in.

Project-scoped ingest

Runtime streams

Search with context

Cloud-ready path

Connect once. Let the logs arrive with shape.

Create a project

Generate an API key

Send logs

The row stays readable. The context stays close.

Payment provider timeout

Give your application logs a place to make sense.