Explore logs

Open Telemetry › Logs to search every log your Agent keeps: the canister logs Monitor collects from the Internet Computer, and the logs your code sends directly.

Search

Choose a canister, type text to search, and turn levels on or off: Trap, Error, Warn and Info. Each level shows how many lines it has in the range. Drag across the volume chart to zoom into a busy moment.

The side panel narrows further, with exact counts: by canister, level, source (collected or sent by code) and event name.

If a canister doesn’t let the Agent read its logs, it’s listed as not searched, so a short result never looks like a quiet fleet.

From a line to its trace

Open a line to see its fields and the lines around it.

• A line your code sent with a trace ID has Open trace, which opens exactly that trace.
• A collected canister log has no trace ID. Traces at this time opens the traces from five minutes either side.

LumeraQL and patterns

Switch to LumeraQL to write a query:

logs between $start and $end
  | contains body "heap out of bounds"
  | newest
  | take 100

$start and $end follow the page’s time range.

Patterns groups similar lines into one template, with <*> where values change, and counts each group. It’s the fastest way to see what a noisy canister is mostly saying.

Good to know

• Canister logs are collected only when the canister’s log visibility admits the Agent and log collection is on in Monitor.
• Logs are kept for as long as you set in the Logs data connection.
• Send your own structured logs: Logs from your code.

Next

• Traces and the service map
• What Monitor reads