WEBVTT

00:00:00.030 --> 00:00:03.905 position:50% align:center size:88%
Let's follow the alert and incident
recorded on October eighth.

00:00:03.955 --> 00:00:07.070 position:50% align:center size:88%
We will inspect the saved evidence on the
current platform.

00:00:07.550 --> 00:00:11.525 position:50% align:center size:88%
This saved signal was received and cleared
on October eighth.

00:00:11.625 --> 00:00:15.125 position:50% align:center size:88%
Alert correlation now includes Service
dependencies.

00:00:15.200 --> 00:00:18.300 position:50% align:center size:88%
Open the panel to read the workspace
relationships.

00:00:18.375 --> 00:00:21.350 position:50% align:center size:88%
This workspace has no dependencies
recorded.

00:00:21.425 --> 00:00:24.233 position:50% align:center size:88%
Close the panel, then open the retained
alert.

00:00:26.560 --> 00:00:30.285 position:50% align:center size:88%
Read the incident's severity and priority
beside its title.

00:00:30.360 --> 00:00:33.035 position:50% align:center size:88%
The sender marked this service mission
critical.

00:00:33.110 --> 00:00:36.135 position:50% align:center size:88%
That declared criticality can raise
priority.

00:00:36.210 --> 00:00:38.760 position:50% align:center size:88%
A priority is not a diagnosis.

00:00:38.835 --> 00:00:41.195 position:50% align:center size:88%
This incident has no assignee recorded.

00:00:43.120 --> 00:00:46.445 position:50% align:center size:88%
Open Ingestion to inspect the original
signal.

00:00:46.520 --> 00:00:49.695 position:50% align:center size:88%
Its service label links the signal to this
incident.

00:00:49.770 --> 00:00:52.745 position:50% align:center size:88%
The source clear is dated October eighth.

00:00:52.820 --> 00:00:56.624 position:50% align:center size:88%
The retained record shows what arrived,
without claiming a live fault.

00:00:59.160 --> 00:01:03.510 position:50% align:center size:88%
The October eighth delivery receipts
record one exact replay.

00:01:03.585 --> 00:01:07.010 position:50% align:center size:88%
That repeat created no second alert or
incident.

00:01:07.085 --> 00:01:11.735 position:50% align:center size:88%
This incident still has one stored alert
and one investigation.

00:01:11.810 --> 00:01:15.651 position:50% align:center size:88%
A repeated delivery differs from a new
condition on the same service.

00:01:17.840 --> 00:01:21.940 position:50% align:center size:88%
Open the recorded investigation and
inspect what it established.

00:01:22.015 --> 00:01:26.140 position:50% align:center size:88%
The recorded investigation had no live
datasource to inspect.

00:01:26.240 --> 00:01:29.315 position:50% align:center size:88%
Read its actual outcome and the evidence
limits.

00:01:29.365 --> 00:01:32.315 position:50% align:center size:88%
The incident was closed as an expected
test.

00:01:32.415 --> 00:01:35.035 position:50% align:center size:88%
No remediation or recovery is claimed.

00:01:37.080 --> 00:01:40.655 position:50% align:center size:88%
Open Documentation and read Send your
first alert.

00:01:40.730 --> 00:01:45.255 position:50% align:center size:88%
Use a stable service label and prepare the
intake credential privately.

00:01:45.355 --> 00:01:49.230 position:50% align:center size:88%
Cloud alarms send their detections through
the supported webhooks.

00:01:49.305 --> 00:01:53.059 position:50% align:center size:88%
The lakehouse supplies evidence; it does
not create these alerts.