Several anomalies stand out. There are 501 ERROR entries, 501 ERROR-status entries, and 501 spans with duration over 1s; these counts matching exactly suggests a concentrated incident or synthetic alert stream rather than ordinary background noise. The latest samples are monitor.alert.triggered, occurring repeatedly within seconds around 15:33–15:34 UTC. Facets also show 87 server-side timeout messages and 44 gRPC DEADLINE_EXCEEDED exceptions. Feature-flag data indicates active failure scenarios including productCatalogFailure, cartFailure, emailMemoryLeak, kafkaQueueProblems, adHighCpu, and intlShippingSlowdown. The initial broad time-series query timed out, so this assessment is based on targeted counts and facets.

The recurring metrics check found several worth-reporting anomalies: 501 ERROR entries, 501 ERROR-status entries, and 501 spans longer than 1 second. There were also 87 server-side timeout messages and 44 gRPC DEADLINE_EXCEEDED exceptions. Recent samples show repeated monitor.alert.triggered events around 15:33–15:34 UTC, with active failure scenarios including product catalog, cart, email memory leak, Kafka queue, high CPU, and international shipping slowdown conditions.

The recurring check found reportable anomalies: 168 ERROR-level entries, 205 entries with ERROR status, and 501 spans longer than 1 second. Recent samples are repeated monitor.alert.triggered events, including several within seconds around 15:35 UTC. Error volume is sustained across 49 time buckets rather than appearing as a single isolated event.

No reportable anomalies were found in the current telemetry check. ERROR-level entries, ERROR-status entries, spans over 1 second, sample errors, and the error time series all returned zero results.

The current telemetry shows sustained abnormal activity: 247 ERROR-level entries, 273 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are repeated monitor.alert.triggered events, including five samples between 15:35:25 and 15:36:04 UTC. ERROR activity appears across 76 time buckets, indicating an ongoing pattern rather than an isolated event.

The recurring telemetry check could not complete because the telemetry database is currently starting up. Findings cannot be verified from this run; the previous check reported sustained ERROR activity and long-duration spans, so this is worth reporting as an availability issue.

Telemetry shows sustained abnormal activity: 279 ERROR-level entries, 316 entries with ERROR status, and 501 spans longer than 1 second. Recent samples include repeated monitor.alert.triggered events and otelcol-contrib errors. ERROR activity spans 96 time buckets, indicating an ongoing pattern rather than an isolated event.

No reportable anomalies were found in the current telemetry check. ERROR-level entries, ERROR-status entries, spans longer than 1 second, recent error samples, and the error time series all returned zero results.

Telemetry shows reportable abnormal activity: 27 entries have ERROR status and 501 spans have duration longer than 1 second. No ERROR-level log entries or recent ERROR samples were returned, and the ERROR time-series query had no results.

Telemetry shows reportable abnormal activity: 38 entries have ERROR status and 501 spans have duration longer than 1 second. No ERROR-level log entries or recent ERROR samples were returned, and the ERROR time series had no results.

Telemetry shows reportable abnormal activity: 33 entries have ERROR status and 501 spans have duration longer than 1 second. No ERROR-level log entries or recent ERROR samples were returned, and the ERROR time series had no results.

Telemetry shows sustained abnormal activity: 263 ERROR-level entries, 298 entries with ERROR status, and 501 spans longer than 1 second. ERROR events recur across 91 time buckets, with recent samples from otelcol-contrib arriving roughly every 10 seconds around 15:23 UTC. This indicates an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 263 ERROR-level entries, 298 entries with ERROR status, and 501 spans longer than 1 second. ERROR events recur across 91 time buckets, with recent samples from otelcol-contrib arriving roughly every 10 seconds around 15:23 UTC. This indicates an ongoing pattern rather than an isolated event.

Telemetry shows reportable abnormal activity: 35 entries have ERROR status and 501 spans have duration longer than 1 second. No ERROR-level logs or recent ERROR samples were returned, so the finding is driven by error-status events and long-running spans.

Telemetry shows sustained abnormal activity: 114 ERROR-level entries, 151 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples are repeated otelcol-contrib events arriving roughly every 10 seconds from 15:34:45 through 15:35:25 UTC. ERROR activity appears across 38 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 333 ERROR-level entries, 367 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples are recurring otelcol-contrib events arriving roughly every 10 seconds around 15:33 UTC. ERROR activity appears across 112 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 333 ERROR-level entries, 367 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples are recurring otelcol-contrib events arriving roughly every 10 seconds around 15:33 UTC. ERROR activity appears across 112 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 204 ERROR-level entries, 260 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples are recurring otelcol-contrib events arriving roughly every 10 seconds through 15:35:34 UTC. ERROR activity appears across 69 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 303 ERROR-level entries, 335 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples are recurring otelcol-contrib events arriving roughly every 10 seconds through 15:26 UTC. ERROR activity appears across 102 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 193 ERROR-level entries, 227 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples are recurring monitor.alert.triggered events, with five occurrences between 15:07 and 15:31 UTC. ERROR activity appears across 67 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows reportable abnormal activity: 16 ERROR-level entries, 51 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are recurring monitor.alert.triggered events, with five samples between 15:06 and 15:30 UTC. ERROR activity appears across 13 time buckets, indicating a recurring pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 360 ERROR-level entries, 396 entries with ERROR status, and 501 spans longer than 1 second. ERROR activity recurs roughly every 10 seconds in the latest samples from otelcol-contrib, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 228 ERROR-level entries, 262 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples include recurring monitor.alert.triggered events and otelcol-contrib errors. ERROR activity appears across 77 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows reportable abnormal activity: 10 ERROR-level entries, 43 entries with ERROR status, and 501 spans longer than 1 second. ERROR events recur approximately every 5–6 minutes, with recent monitor.alert.triggered samples through 15:31 UTC. This indicates a recurring pattern rather than an isolated event.

Telemetry shows reportable abnormal activity: 25 ERROR-level entries, 58 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are recurring monitor.alert.triggered events, with five samples between 15:09 and 15:33 UTC. ERROR activity appears across 16 time buckets, indicating a recurring pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 91 ERROR-level entries, 128 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are recurring monitor.alert.triggered events, with five samples from 15:09 to 15:32 UTC. ERROR activity spans 36 time buckets, indicating a recurring pattern rather than an isolated event.

Telemetry shows reportable abnormal activity: 10 ERROR-level entries, 45 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are recurring monitor.alert.triggered events, with five samples between 15:08 and 15:31 UTC. ERROR activity appears across 10 time buckets, indicating a recurring pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 15 ERROR-level entries, 46 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples include recurring otelcol-contrib events roughly every 10 seconds and a monitor.alert.triggered event at 15:35:09 UTC. ERROR activity spans 12 time buckets, indicating a recurring pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 339 ERROR-level entries, 378 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples are recurring otelcol-contrib events arriving roughly every 10 seconds through 15:35:30 UTC. ERROR activity appears across 111 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 151 ERROR-level entries, 185 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples are recurring otelcol-contrib events arriving roughly every 10 seconds through 15:35:28 UTC. ERROR activity spans 54 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 286 ERROR-level entries, 327 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples include recurring otelcol-contrib events roughly every 10 seconds and a monitor.alert.triggered event at 15:34:06 UTC. ERROR activity appears across 97 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 80 ERROR-level entries, 117 entries with ERROR status, and 501 spans longer than 1 second. Recent ERROR samples are recurring otelcol-contrib events arriving roughly every 10 seconds through 15:35:35 UTC. ERROR activity appears across 32 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 173 ERROR-level entries, 207 entries with ERROR status, and 501 spans longer than 1 second. Recent errors include recurring monitor.alert.triggered events and otelcol-contrib errors. ERROR activity appears across 60 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows reportable abnormal activity: 47 ERROR-level entries, 57 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are recurring monitor.alert.triggered events, with samples roughly every five minutes through 15:31 UTC. ERROR activity appears across 28 time buckets, indicating a recurring pattern rather than an isolated event.

Telemetry shows reportable abnormal activity: 10 ERROR-level entries, 20 entries with ERROR status, and 501 spans longer than 1 second. ERROR events recur approximately every 6 minutes, with recent monitor.alert.triggered samples from 15:07 through 15:30 UTC. This indicates a recurring pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 46 ERROR-level entries, 58 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are recurring otelcol-contrib events reporting “Exporting failed. Dropping data.” approximately every 10 seconds through 15:35:27 UTC. ERROR activity appears across 25 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows reportable abnormal activity: 11 ERROR-level entries, 45 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are recurring monitor.alert.triggered events, with samples from 15:10 through 15:32 UTC. ERROR activity recurs across 11 time buckets, indicating a recurring pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 120 ERROR-level entries, 155 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are recurring otelcol-contrib events reporting “Exporting failed. Dropping data.” approximately every 10 seconds through 15:35:30 UTC. ERROR activity appears across 44 time buckets, indicating an ongoing pattern rather than an isolated event.

Telemetry shows sustained abnormal activity: 136 ERROR-level entries, 167 entries with ERROR status, and 501 spans longer than 1 second. Recent errors are recurring otelcol-contrib events reporting “Exporting failed. Dropping data.” approximately every 10 seconds through 15:35:34 UTC. The error time series is persistent across the sampled window, indicating an ongoing data-export problem rather than an isolated event.

Telemetry shows an ongoing data-export failure. There are 129 ERROR-level entries, 170 ERROR-status entries, and 501 spans longer than 1 second. Recent errors from otelcol-contrib report “Exporting failed. Dropping data.” approximately every 10 seconds through 15:35:35 UTC. ERROR activity appears across 47 time buckets, indicating a persistent issue rather than an isolated event.

Telemetry shows an ongoing data-export failure: 58 ERROR-level entries, 95 ERROR-status entries, and 501 spans longer than 1 second. Recent otelcol-contrib errors report “Exporting failed. Dropping data.” approximately every 10 seconds through 15:35:25 UTC. ERROR activity spans 26 time buckets, indicating a persistent issue rather than an isolated event.

Telemetry shows an ongoing data-export failure. There are 170 ERROR-level entries, 203 ERROR-status entries, and 501 spans longer than 1 second. Recent otelcol-contrib logs report “Exporting failed. Dropping data.” approximately every 10 seconds through 15:35:36 UTC. ERROR activity spans 60 time buckets, indicating a persistent issue rather than an isolated event.

The recurring check found reportable abnormal activity: 86 ERROR-level entries, 120 ERROR-status entries, and 501 spans longer than 1 second. Recent errors are recurring monitor.alert.triggered events at roughly six-minute intervals, with the latest sample at 15:30:16 UTC. ERROR activity appears across 34 time buckets, indicating a recurring pattern rather than an isolated event.

Recurring monitor alert activity was detected: 11 ERROR-level entries, 45 ERROR-status entries, and 501 spans longer than 1 second. Recent monitor.alert.triggered errors recur at roughly six-minute intervals, with the latest sample at 15:34:05 UTC. ERROR activity spans 11 time buckets, indicating a recurring pattern rather than an isolated event.