Log search

What you get

• Everything your apps print, in one place
• A live view as lines arrive
• Search by text or by a field of a JSON line
• Filters by time and by environment
• Secret values hidden as [REDACTED:NAME]
• Lines from Whisk itself, such as restarts

How it works

Apps print to standard output, as the rules ask, with no logging library to set up. Whisk collects every line, labels it with the app and environment, and stores it in Grafana Loki, the open-source log store.

Lines written as JSON can be searched by field, such as level=error, and plain lines by text. Each request carries an id the app adds to its lines, so one request can be followed from start to finish. The value of any declared secret is replaced with its name.

Every search is limited to your own business's apps. The dashboard and the CLI read the same logs, so a person and a coding agent see the same lines. To keep a copy in a service you already use, see bring your own logs.

Example

A project manager at an engineering firm reports that a timesheet would not save. The developer's coding agent searches the last day's error lines for her email address. It finds the validation error and fixes it in the next deploy.

For your coding agent

whisk logs --since 24h --grep level=error
whisk logs -f --env production
whisk logs --grep <request id>

Every flag is in the CLI reference.