Work with notifications and contextual investigations

Move from an alert to an investigation

Notifications draw attention to completed work and detected issues without requiring you to watch every page. Their short summaries are meant to tell you where to look, not to provide a complete diagnosis.

Opening a notification starts or reopens a conversation tied to that alert while leaving the current page visible. You can ask Vega for an explanation, compare it with the underlying measurements and health evidence, and later return to the same conversation through Chat history.

For the underlying source evidence, see Review measurements, asset health, and events.

Review notifications

1. Select the bell in the top-right navigation.
2. Check the unread badge; values above 99 are displayed as 99+.
3. Read each notification’s title, summary, and time.
4. Select the notification row or Ask AI to open its contextual conversation.

An unread notification has a blue marker and highlighted background. Opening its row marks it as read. New notifications can arrive while Vega is open and may also appear briefly as an information message.

The list can include measurement synchronization results, detected health issues, completed analyses, and other account events. The available types depend on the account and enabled product features.

Investigate in the contextual conversation

When you open a notification, Vega keeps the current page in place and opens Chat beside it. The first visible question includes notification context such as the issue, component, and relevant date when those details are available.

1. Read the prefilled question and Vega’s answer.
2. Compare the explanation with the notification summary.
3. Ask for the exact component, timestamps, detector facts, and measurement coverage used.
4. Keep the source page visible while checking those details.
5. Ask follow-up questions in the same panel.

For a health issue, useful follow-ups include:

Which measured facts support this finding, and which possible causes are still hypotheses?

Show the affected period and tell me whether coverage was complete.

What should I check in Inventory, Health, and the Event Log before taking action?

Vega looks for an existing chat associated with the notification. Reopening the same notification therefore continues that conversation when one already exists instead of deliberately creating a duplicate.

Move the conversation to a full page

Use Open as full page in the contextual chat header after the conversation has been created. This opens the same chat on its normal route; it does not start a new investigation.

Closing the contextual panel does not delete the conversation. Find it later in Chat history.

Manage the notification list

• Select Mark all as read in the notification header to clear all unread markers.
• Select Delete all to remove every notification from the inbox.

There is no per-notification delete action in the current panel. Deleting notifications does not imply that the related health finding, event-log record, or saved chat has been removed. Treat those as separate records.

Verify before acting

A notification is a signal, not a complete diagnosis. Before changing operations or escalating an incident:

1. Confirm that the active account and named site are correct.
2. Open the component’s Measurements and Health tabs.
3. Check the same date in the Event Log.
4. Verify whether missing data or a synchronization failure could explain the signal.
5. Ask Vega to separate observations, interpretation, and recommended checks.
6. Record the conclusion in the operational system your organization uses.

Follow Verify Vega’s answers before acting for a complete validation workflow.