Skip to content
Weik.io
Book a demoTry Weik.io

Observability

Every integration sends its logs, metrics and traces through OpenTelemetry, and each line, span and number carries the integration, version, project, environment and agent it came from. Weik.io checks them every 15 seconds and raises a problem when an integration fails, restarts in a loop, grows its memory day after day or stops handling messages. You read all of it in the admin UI or with the weikio CLI, and you can forward it to Azure Monitor, Splunk or any OTLP receiver.

Open the live demoRead the observability docs
Terminal
$ weikio logs finance/erp-invoice-export --env production -f
$ weikio metrics finance/erp-invoice-export --env production
$ weikio traces finance/erp-invoice-export --env production --errors
$ weikio trace 4bf92f3577b34da6a3ce929d0e0e4736
$ weikio problems --env production

What you see

/observability
The Observability overview of production with nothing that needs attention, the messages handled in the last hour, all integrations running and the API calls and errorsThe Observability overview of production with nothing that needs attention, the messages handled in the last hour, all integrations running and the API calls and errorsThe Observability overview of production with nothing that needs attention, the messages handled in the last hour, all integrations running and the API calls and errorsThe Observability overview of production with nothing that needs attention, the messages handled in the last hour, all integrations running and the API calls and errors
The Observability overview counts what runs in production and lists what needs attention, beside the messages, API calls and errors of the last hour.

Problems Weik.io raises

Weik.io checks for these every 15 seconds. Each problem shows on Home, in Observability, on the record's page and in weikio problems:

  • An integration failing, at least 5 messages and 5 % of its messages in 15 minutes
  • An integration that restarts in a loop
  • Memory that grows day after day
  • An integration that stopped handling messages
  • An API failing on the server's side
  • A failed transfer run
  • Storage filling up
  • Telemetry not arriving at the hub
  • A backup overdue
  • Two-factor sign-in switched off for platform administrators

All problems

Your own numbers

Counters and timers written with Camel's micrometer: and opentelemetry-metrics: components show up next to the platform's own numbers, with the same integration, version and environment on them. The video Custom metrics adds a counter to an integration and finds it in the admin UI.

Custom metrics

finance/erp-invoice-export/routes/publish.camel.yaml
- route:
    from:
      uri: direct:export-invoice
      steps:
        - to: "{{erp-url}}/api/invoices"
        - to: micrometer:counter:invoices_processed

How long it's kept

SignalKept
Logs30 days
Metrics90 days
Traces7 days
Audit trail400 days

An admin changes the days for metrics and traces in the hub's configuration, and the log and trace stores keep fewer days when they reach their disk cap.

Your own tools

A platform admin applies one telemetry-forwarding document, and an OpenTelemetry Collector at the hub forwards logs, metrics, traces and the audit trail to your own systems. The docs have complete examples for Azure Monitor, Splunk HEC and an OTLP SIEM, and Settings › Telemetry forwarding and weikio forwarding status show that the records arrive.

Every process of the platform also has a Prometheus page, so your own monitoring can watch the hub and the agents.

Telemetry forwarding

When the link is down

A site keeps up to 4 GiB of telemetry on its own disk while the hub is out of reach, or a tenth of its free disk when that is less. When the link is back it sends the records with their original times, and the live tail shows those late lines too.

Watch it

Open the live demo

The live demo has a failing integration on purpose, so every screen on this page has something to show.

Open the live demoRead the observability docs