Issues & signals

How Duku turns the errors it finds into a short list of distinct problems.

Duku turns run errors into a concise list of distinct problems.

From errors to issues

A run produces errors. Errors with the same signature are collected into a signal. Signals with one underlying cause are collected into an issue.

This keeps a broken endpoint in one issue, not a dozen near-identical rows.

Duku also reviews the screens it captures and reports bugs that are visible on them. See Visual issues.

Issues and signals views

Where grouping is enabled, the Issues page lists one entry per problem, and each entry shows how many signals are behind it. Open an issue and select its signals to see each one. Products without grouping list each error on its own.

Use the Issues to review either view.

Counts

An issue's Signals count is the number of signals behind it. Its Runs count (shown as Affected runs on the issue) is the number of distinct runs that hit it.

The Runs count does not count every error seen during those runs.

Status and priority

Status and priority are set on the issue. They apply to everything grouped into it.

A status you set never changes back automatically.

Use the Issues API to read issues and signals, or write status and priority changes.