View and Investigate Alerts and Issues

When one of your Alert Policies fires, DropStream records the failure as an Alert and groups related alerts into an Issue. You can browse and investigate both from the Operations area of the sidebar.

Alerts vs. Issues

• An Alert is a single failure occurrence — for example, one order that could not be imported from one store at one point in time. DropStream records an alert for every failure it detects, whether or not you have any Alert Policies configured.
• An Issue is a group of related alerts, created by an Alert Policy whose Monitored Events matched the failure. An issue’s grouping behavior comes from the policy’s Alert Grouping setting.

If no policy matches a particular failure, the alert still appears in the Alerts list — it just won’t be part of an issue and no notification is sent. If one or more policies match, the alert is rolled up into each matching policy’s open issue. An issue closes automatically when no new matching alerts arrive within its policy’s Auto-close Duration.

This is why the Alerts list and Issues list don’t have a one-to-one relationship: the Alerts list shows everything that has failed, while the Issues list shows only the failures that matched something you explicitly chose to monitor.

Browse alerts

In the sidebar, open Operations → Alerts.

Each row shows:

• Alert ID — click to open the alert detail page.
• Severity — the urgency of the failure (for example, Error).
• Type — a short label describing the kind of failure (for example, Import failed or Process fulfillment rules failed).
• Entity — the object affected (Store, Order, Warehouse, and so on).
• Message — a brief description of what went wrong.
• Status — Open while the problem persists; Closed once it has resolved.
• Started — when the alert was first raised.

Use Filter by, the search box, and the Columns button to narrow down what you see. The Default View button saves your current filters and columns as the view that loads when you open this page.

Investigate an alert

Click an alert’s ID to open its detail page.

The detail page shows:

• Error Message — the raw message DropStream received when the failure occurred.
• Details — alert type, when it started, when it closed (if applicable), and total duration.
• Activity Timeline — the sequence of integration and error events surrounding the failure, so you can see what happened before and after. Each entry links to the underlying task.
• Related Task — a shortcut to the task that produced this alert. Click View Task to see its logs. Click Search Event Logs to jump into the Logs view filtered to this alert’s context.
• Similar Alerts — other alerts of the same type on the same entity, so you can tell at a glance whether this is a one-off or a pattern.
• Part of Issue — the issue this alert was rolled up into (see below). Only appears when an Alert Policy’s Monitored Event matched this failure; standalone alerts have no issue.
• Affected Entity — a link back to the store, warehouse, or connection involved.

Browse issues

In the sidebar, open Operations → Issues.

Each row shows:

• Issue ID — click to open the issue detail page.
• Policy — the Alert Policy that opened the issue.
• Status — Open or Closed.
• Open Alerts — how many of this issue’s alerts are still unresolved.
• Total Alerts — the lifetime count of alerts in this issue.
• Entity — the affected entity, when the policy’s grouping scopes the issue to one.
• Started and Duration — when the issue opened and, if closed, how long it stayed open.

Investigate an issue

Click an issue’s ID to open its detail page.

The detail page shows:

• Alerts — every alert rolled up into this issue, with its type, status, message, and time. Click any row to open the alert’s detail page.
• Timeline — when the issue started, when it closed, and its total duration.
• Affected Entities — every store, warehouse, or connection this issue has touched.
• Alert Policy — the policy that opened the issue, including its Incident Grouping setting. Click View Policy to jump to its configuration.

Use the issue view when you want a higher-level picture of an ongoing incident; use individual alert details when you’re debugging a specific failure.