Alerts are delivered by someone opening the screen and pressing `Acknowledge`; the dashboard has no email, webhook, Slack, or GitHub channel
Alerts are delivered by showing up. Weboptiva has no outbound alert channel in the dashboard: there is no email recipient list, no webhook URL, and no Slack or GitHub configuration anywhere in the product, and no notification feed that carries these alerts. The only action an alert offers is Acknowledge.
1. Acknowledge an open alert#
On Lab vs real-user, scroll to the regression panel and press Acknowledge on an open alert. The button reads Acknowledging… while the change saves; then the row replaces it with Acknowledged, the acknowledged count beside the header increases, and the open count drops. Acknowledging records that a person has seen the alert — it does not resolve it, does not remove it from the list, and does not change traffic.
2. Know what acknowledging does not do#
An acknowledged alert stays visible, keeps its current and baseline values, and keeps being evaluated. Only a recovered metric resolves it, at which point it disappears from the panel. Nothing is deployed, rolled back, or throttled because an alert opened, and no email, chat message, or webhook call is sent when it does.
3. Confirm the channels that do not exist#
Read the panel header while you are looking for delivery settings: it carries Enable consented field collection and nothing else. The Analytics sections control lists Traffic, Production readiness, Performance outcomes, Performance budget, Resource monitoring, Post-promotion validation, and Lab vs real-user — there is no alerting or integrations page among them, and the Notifications control in the top bar is a workspace-level icon that does not list field regressions.
4. Plan for manual delivery instead#
Because alerts are in-dashboard only, treat the field report as something you read on a schedule and immediately after a release: the Release and Configuration breakdowns exist precisely to make that comparison cheap. If you need a machine-readable signal, the same aggregate figures are available as JSON from the analytics API and summarised on Performance outcomes under Observed field improvement, with the caveat that outcome totals count observed live delivery events and exclude analyzer estimates.
Expected result#
Every open alert has been seen and marked Acknowledged, and you know that no notification left the product — the acknowledgement is the delivery.
The cost of having no outbound channel is simple: nobody is told. If nobody opens the screen, a regression stays unnoticed until the next check, so make the check part of your release routine rather than relying on an alert to interrupt you.