14:02, 3 alerts grouped
Parcelo is refusing calls
Why
Parcelo did not accept the call: 502 Bad Gateway
What to do
Nothing yet. Tasks retry on their own.
Self-hosted telemetry for Node apps. Adonis and NestJS in one command, any OpenTelemetry stack in one line.
Logs, traces, task runs, issues and business processes, read on one clock.
PARCELO_UNAVAILABLEParcelo answered 502 the first time. The retry 30 s later went through.
PARCELO_UNAVAILABLE, 1.42 s{
"orderId": 7781,
"customer": "c***@acme.fr",
"token": "[REDACTED]",
"sessionCode": "RS6731-B2"
}PARCELO_UNAVAILABLE, 38 eventsE_VALIDATION_ERROR, 6 eventsParcelo did not accept the call: 502 Bad Gateway
Nothing yet. Tasks retry on their own. If it lasts, check the provider's status and lower this kind's concurrency.
PARCELO_UNAVAILABLENothing else to operate. A broken definition shows its error and the rest keeps working.
Everything specific to your app lives in definitions/ and deploys with it. Click a highlighted value to change it.
export const parcelo = defineLogRenderer({ id: "parcelo", match: "parcelo.*", title: "Parcelo", render: (e) => [ ui.numbers({ observed: e.num("parcelo.parcelsObserved"), created: e.num("parcelo.parcelsDelivered"), }), ui.fields(e, "parcelo.", { tones: { refused: }, }), ], row: (e) => `${e.num("parcelo.parcelsObserved")} parcels`,});
The event panel, for any event matching parcelo.*
The log row, in place of raw JSON
// A provider that stops answering is what most// task alerts come down to, so say that first.export const providerDown = defineErrorRenderer({ id: "provider-unavailable", match: (error) => error.code.endsWith("_UNAVAILABLE"), headline: (error) => `${name(error)} is refusing calls`, recovered: (error) => `${name(error)} is answering again`, why: (error) => `${name(error)} did not accept the call`, fix: () => "Nothing yet. Tasks retry on their own.",});
The post in your channel
Why
Parcelo did not accept the call: 502 Bad Gateway
What to do
Nothing yet. Tasks retry on their own.
Alerts within 30 s go out as one post, with the errors behind them.
export const fulfilment = defineProcess({ id: "results-delivery", title: "Order fulfilment", subject: "order", sla: "4h", steps: [ step.task("paynest.payment.ingest", { expectWithin: "30m" }), step.parallel([ step.task("receipts.email", { optional: true }), step.task("parcelo.ship", { label: "Shipment created at Parcelo", expectWithin: , }), ]), ],});
What is stuck, and why
Every step also gets a funnel, its instances, and an MCP tool that reads them.
export const apiErrors = defineAlert({ id: "api-5xx", name: "API 5xx rate", when: { source: "request-error-rate" }, above: , window: "10m", unit: "%", condition: "Server errors above 2% over 10 min",});
The last two hours, against your threshold
POST /mcp speaks MCP over HTTP. Every page and every defineTool becomes a tool. Payloads never leave through it.
With a read token
With a write token, as the signed-in person
Vigie MCP
POST /mcp with a read token
11 tools, every page included
payloads stay on your server
Redaction runs before anything is stored, so nothing downstream ever sees the raw value. Type one in.
One command starts Vigie. ClickHouse comes from an installed binary, Docker, or a download, and ports that are taken move to the next free one.
bunx vigie --seed# the app on http://localhost:5310, ingest on :4318 # --seed sends a day of realistic telemetry # no sign-in, listens on this machine only
deploy/install.sh --domain vigie.acme.dev# Docker, ClickHouse and HTTPS from Caddy # prints the owner's setup code and the first ingest key
node ace add @vigiejs/adonis# traces from @adonisjs/otel, one wide event per request # background work through task()
npx @vigiejs/nestjs init# adds VigieModule.forRoot() and the trace register # @VigieTask() on BullMQ processors and crons
OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318# any OpenTelemetry SDK, any language # a log with method, status and durationMs is a request