Skip to content
Weik.ioDocs
2026.2
Try Weik.io

Observability

Weik.io 2026.2

Read logs, metrics, traces, problems, the audit log and recent activity from the command line.

On this page

Every integration, agent and hub process sends its logs, metrics and traces to the hub over OpenTelemetry, and these commands show them with the same filters the admin UI uses. Each command shows only what your grants allow, and a command that finds nothing prints nothing on standard output and one line on standard error.

weikio problems lists what needs attention, with the command that shows more about each row, and each kind of problem has its own page under Problems.

Commands on this page#

Command What it does
weikio logs Print the logs of an integration in one environment.
weikio agent logs Show the agent’s own log lines.
weikio platform logs Read the log lines of a hub process.
weikio platform metrics Print a part of the platform’s figures over a window.
weikio audit query List audit records, newest first.
weikio audit show Print the audit records and log lines of a correlation id, oldest first.
weikio problems List the problems you can see.
weikio activity List the recent changes to the projects you may read, newest first.
weikio metrics Show the metrics of an integration, an API or an environment, or chart one metric over a window.
weikio traces List the traces of an integration, an API or an environment, newest first.
weikio trace Print one trace as its steps.
weikio platform health Print whether the backend is alive and ready, and every part of the platform with a platform admin key.

The flags every command accepts, such as --env, --project, -o and --context, are on the CLI reference page and are left out of the tables below.

weikio logs#

Print the logs of an integration in one environment. -f follows new lines until Ctrl-C. --top-errors groups the window’s errors by exception and route, --histogram counts lines per interval and level, and --build prints a version’s build output.

Terminal
weikio logs <p>/<n> [--env E] [-f] [--since] [--from --to] [--level] [--agent] [--correlation-id] [--query] [--limit] [--before | --after] [--histogram [--interval]] [--top-errors] [--build --version]
Argument or flag What it does
<integration> Integration as project/name.
-f, --follow Print new lines as they arrive, until Ctrl-C.
--since <since> How far back to read, such as 10m.
--level <level> Show only lines at this level or above: trace, debug, info, warn, error or fatal.
--query <query> Full-text query over the lines, in the log store’s query language.
--limit <limit> Number of lines to read, at most 5,000.
--before <before> Read lines older than the one with this _id.
--after <after> Read lines newer than the one with this _id.
--from <from> Start of the window, as a time or as how long ago.
--to <to> End of the window, as a time or as how long ago.
--agent <agent> Show only the lines written by the agent with this ID.
--correlation-id <correlation-id> Show only lines with this correlation id.
--histogram Print line counts per interval and level instead of lines.
--interval <interval> Width of one histogram interval, such as 5m or 1h.
--top-errors Print the most common errors of the window, one row per exception and route, instead of lines.
--build Print a version’s build output instead of the log lines.
--version <version> Which version’s build output to print.

Who can run it: any API key. The lines are narrowed to what your read grants open.

API: GET /api/v1/logs, GET /api/v1/logs/tail, GET /api/v1/logs/histogram, GET /api/v1/logs/top-errors.

Terminal
$ weikio logs finance/erp-invoice-export --env production --since 15m --level warn --limit 2
You see
14:31:02.118 UTC WARN  fetch-invoices  agent-fi-02  HTTP 429 from https://erp.example.internal/api/invoices/pending, retrying in 30 s
14:31:32.204 UTC WARN  fetch-invoices  agent-fi-02  HTTP 429 from https://erp.example.internal/api/invoices/pending, retrying in 60 s

To read older lines, run:
  weikio logs finance/erp-invoice-export --env production --since 15m --level warn --limit 2 --before GNf5pJG7hYAAyvg9zpCA
Terminal
$ weikio logs finance/erp-invoice-export --env production --since 6h --histogram --interval 1h
You see
HOUR        INFO   WARN   ERROR
09:00 UTC   612    0      0
10:00 UTC   598    0      0
11:00 UTC   601    0      0
12:00 UTC   604    2      0
13:00 UTC   590    14     1
14:00 UTC   211    38     0

weikio agent logs#

Show the agent’s own log lines.

Terminal
weikio agent logs <id|name> [-f] [--since] [--level] [--query] [--limit] [--before | --after]
Argument or flag What it does
<agent> Agent name or ID.
-f, --follow Print new lines as they arrive, until Ctrl-C.
--since <since> How far back to read, such as 10m.
--level <level> Show only lines at this level or above: trace, debug, info, warn, error or fatal.
--query <query> Full-text query over the lines, in the log store’s query language.
--limit <limit> Number of lines to read, at most 5,000.
--before <before> Read lines older than the one with this _id.
--after <after> Read lines newer than the one with this _id.

Who can run it: a platform administrator.

API: GET /api/v1/logs, GET /api/v1/logs/tail.

Terminal
$ weikio agent logs agent-fi-02 --since 10m
You see
14:40:02.001 UTC INFO  Deployment 'production/finance/erp-invoice-export (01k5xb7q2r4t6v8w0y2z4a6c8e)' is restarting, because its version changed from 1.1.0 to 1.0.0.
14:40:04.214 UTC INFO  Deployment 'production/finance/erp-invoice-export (01k5xb7q2r4t6v8w0y2z4a6c8e)' stopped process 4188 within its 70 s stop deadline.
14:40:05.870 UTC INFO  Deployment 'production/finance/erp-invoice-export (01k5xb7q2r4t6v8w0y2z4a6c8e)' started as process 4210 (version 1.0.0, Camel 4.22.1). It counts as starting until its health check replies.

weikio platform logs#

Read the log lines of a hub process.

Terminal
weikio platform logs backend|apim [-f] [--since] [--level] [--query] [--limit] [--before | --after]
Argument or flag What it does
<process> backend or apim.
-f, --follow Print new lines as they arrive, until Ctrl-C.
--since <since> How far back to read, such as 10m.
--level <level> Show only lines at this level or above: trace, debug, info, warn, error or fatal.
--query <query> Full-text query over the lines, in the log store’s query language.
--limit <limit> Number of lines to read, at most 5,000.
--before <before> Read lines older than the one with this _id.
--after <after> Read lines newer than the one with this _id.

Who can run it: a platform administrator.

API: GET /api/v1/logs, GET /api/v1/logs/tail.

weikio platform metrics#

Print a part of the platform’s figures over a window.

Terminal
weikio platform metrics backend|apim|agent <id>|hub [--since D] [--top] [-o json]
Argument or flag What it does
<part> backend, apim, agent or hub.
<id> The agent’s ID or name when part is agent.
--since <since> How far back the figures reach, such as 6h or 7d, by default an hour.
--top With hub, list the metric names and services with the most metrics.

Who can run it: a platform administrator.

API: GET /api/v1/platform/health, GET /api/v1/platform/metrics, GET /api/v1/platform/series.

weikio audit query#

List audit records, newest first. The audit log keeps 400 days of records: every change, every secret reveal and delivery, agent enrolments and revocations, backups and restores, and every read of the audit log itself.

Terminal
weikio audit query [--since 24h] [--from --to] [--actor A] [--action ACTION] [--target-kind K] [--target ADDRESS | --target-id ID] [--outcome ok|denied|refused|error] [--project P | --project-id ID] [--env E | --env-id ID] [--limit N] [--before SEQ | --after SEQ]
Argument or flag What it does
--since <since> How far back to read, such as 24h.
--from <from> Start of the window.
--to <to> End of the window.
--actor <actor> Show only records by this actor, such as user:<id> or api-key:<id>.
--action <action> Show only this action, as -o json prints it, such as SecretRevealed.
--target-kind <target-kind> Show only targets of this kind, such as deployment.
--target <target> Show only the target at this address, such as production.finance.erp-invoice-export.
--target-id <target-id> Show only the target with this ID, including a deleted one.
--project-id <project-id> Show only the project with this ID, including a deleted one.
--env-id <env-id> Show only the environment with this ID, including a deleted one.
--outcome <outcome> Show only ok, denied, refused or error.
--limit <limit> How many records to read, at most 1,000.
--before <before> Read records older than this seq.
--after <after> Read records newer than this seq, or 0 for the oldest.

Who can run it: a platform administrator, or a project’s admin for the records of their projects.

API: GET /api/v1/audit?from&to&actor&action&targetKind&targetId&targetUid&outcome&correlationId&project&projectUid&environment&environmentUid&limit&before&after.

Terminal
$ weikio audit query --since 24h --action SecretRevealed
You see
TIME                   ACTOR               ACTION                                         TARGET                                     OUTCOME   IP          REASON
2026-09-16 14:36 UTC   ville@example.com   Not allowed to reveal a secret in production   Secret finance/erp-api-key in production   denied    10.1.4.31   -
2026-09-16 09:02 UTC   anna@example.com    Revealed a secret in devtest                   Secret finance/erp-api-key in devtest      ok        10.1.4.22   -

weikio audit show#

Print the audit records and log lines of a correlation id, oldest first. A correlation id ties one CLI call to its audit records and the hub’s log lines.

Terminal
weikio audit show <correlation-id>
Argument or flag What it does
<correlation-id> The correlation id.

Who can run it: a platform administrator, or a project’s admin for the records of their projects.

API: GET /api/v1/audit?correlationId=&limit=1000, GET /api/v1/logs?whole=true&order=oldest.

weikio problems#

List the problems you can see. Each row has a figure, such as 42 of 310 failed in 15 min, and a detail that ends with the command that shows more. Each kind has its own page under Problems.

Terminal
weikio problems [--env E] [--project P]

Who can run it: any API key. You see the rows of what you may read.

API: GET /api/v1/summary/problems?environment=&project=.

weikio activity#

List the recent changes to the projects you may read, newest first. The same list is the Recent activity panel of the admin UI.

Terminal
weikio activity [--project P] [--env E] [--integration I] [--api A] [--from T --to T] [--limit N] [--before SEQ | --after SEQ]
Argument or flag What it does
--limit <limit> How many changes to read, at most 1,000.
--before <before> Read changes older than this seq.
--after <after> Read changes newer than this seq, or 0 for the oldest.
--integration <integration> Show only the changes to this integration, written as project/name or as a name.
--api <api> Show only the changes to this API, written as project/name or as a name.
--from <from> Start of the window, as a time or as how long ago.
--to <to> End of the window, as a time or as how long ago.

Who can run it: any API key. You see the changes in the projects you may read.

API: GET /api/v1/activity?project=&environment=&integration=&api=&from=&to=&limit=&before=&after=, GET /api/v1/users/_emails?ids=.

weikio metrics#

Show the metrics of an integration, an API or an environment, or chart one metric over a window. --name charts one metric over the window, an integration’s own counter included, and --query accepts a MetricsQL expression over what you may read.

Terminal
weikio metrics <p>/<n> [--env E] [--since D | --from T --to T]
Argument or flag What it does
<integration> Integration as project/name.
--api <api> API as project/name, or project/name@version for one version.
--name <name> Draw one metric: a figure such as messages, failed or memory, a stored metric name, or the integration’s own counter, such as invoices.processed.
--agg <agg> How a stored metric or own counter in --name is aggregated over each step: rate, increase, last, max, min, avg, p50, p95 or p99.
--by <by> What to split by: route, agent or version for a chart, status, version, route or subscription for an API, or integration or api for an environment. An integration’s own counter splits by agent, version or one of its attributes.
--step <step> Time each point of a chart covers, such as 5m.
--query <query> A MetricsQL expression to draw, over the metrics you can read.
--since <since> How far back to read, such as 10m.
--from <from> Start of the window, as a time or as how long ago.
--to <to> End of the window, as a time or as how long ago.

API: GET /api/v1/metrics, GET /api/v1/metrics/names, GET /api/v1/metrics/metadata, GET /api/v1/metrics/summary.

weikio traces#

List the traces of an integration, an API or an environment, newest first. --errors lists only failed traces and --min-duration only slow ones.

Terminal
weikio traces <p>/<n> | --api <p>/<api>[@<v>] | --env E [--project P] [--errors] [--min-duration D] [--route R] [--limit N] [--before P | --after P] [--since D | --from T --to T]
Argument or flag What it does
<integration> Integration as project/name.
--api <api> API to list traces for, as project/name, with @version for one version.
--errors List only failed traces.
--min-duration <min-duration> List only traces that took at least this long, such as 500ms or 2s.
--route <route> List only traces that ran in this route, by its id or by the endpoint it reads from.
--limit <limit> Number of traces to list, at most 1,000.
--before <before> List the traces that started before the one at this position (the command at the end of a page gives it).
--after <after> List the traces that started after the one at this position.
--since <since> How far back to read, such as 10m.
--from <from> Start of the window, as a time or as how long ago.
--to <to> End of the window, as a time or as how long ago.

Who can run it: any API key. The traces are narrowed to what your read grants open.

API: GET /api/v1/traces.

weikio trace#

Print one trace as its steps.

Terminal
weikio trace <trace-id|traceparent|message-id> [-o json]
Argument or flag What it does
<trace> The trace id, a traceparent header or a message id.

Who can run it: any API key. The steps are narrowed to what your read grants open.

API: GET /api/v1/traces/{id}, GET /api/v1/traces?exchangeId=.

weikio platform health#

Print whether the backend is alive and ready, and every part of the platform with a platform admin key. Without a key it shows whether the backend is alive and ready. With a platform administrator’s key it also lists every part of the platform, such as the backend nodes, the APIM instances and the agents, with each part’s version, uptime, CPU, memory, disk and when it was last seen.

Terminal
weikio platform health [--server URL] [--watch] [-o json]
Argument or flag What it does
--watch Draw the health again every 30 s, with the platform’s latest warnings and errors under it, until interrupted.

Who can run it: nothing for the first line. The parts of the platform need a platform administrator.

API: GET /healthz, GET /readyz, GET /.well-known/openid-configuration, GET /api/v1/platform/health, GET /api/v1/logs.

Terminal
$ weikio platform health
You see
Server:     https://hub.example
Liveness:   ok
Readiness:  ok
Issuer:     https://hub.example

Exit codes#

The commands on this page exit with the codes in the exit code table: 0 on success, 1 when the hub refuses a change, 2 for a usage error, 3 when the key is missing or not allowed, 4 when something isn’t found, 5 for a conflicting change, 6 when the hub can’t be reached and 8 when a document isn’t valid.

See also#