regsvc (tilda) image pull failing for at least 116 min — 1 pod
Pod cannot start: regsvc (tilda) image pull failing for at least 116 min — 1 pod. Facts: namespace tilda, workload regsvc, why image pull failing, pending_minutes 116, since 1794905077.
What X-ray is prepared to defend about test26 right now — each one a claim
with its numbers, the evidence to check it, and what normal looks like. Detectors last ran
never.
?A finding is opened by a detector — a statistical test over the stored rollups, or a
live check of a source — and stays ONE row while the condition persists: it updates,
escalates, and resolves itself fifteen minutes after the detector stops seeing it.
Acknowledge to say you have it; snooze to hide it for a while; nothing here is a
threshold somebody configured.
Every card is a claim X-ray can back with numbers you can click through to. Findings rank by severity first, then by an impact score (severity band + the subject's share of the cluster's traffic + how long it has been open), so the top of the page is the thing to look at first.
What this page will not tell you
Pod cannot start: regsvc (tilda) image pull failing for at least 116 min — 1 pod. Facts: namespace tilda, workload regsvc, why image pull failing, pending_minutes 116, since 1794905077.
feedsvc's Neo4j queries per request is 162.4 against the 5 other services' median of 7.3 (31.3 robust MADs above, six-hour window). This compares the service with its peers, not with its own history — the seasonal detector does that.
enrollsvc's Neo4j queries per request is 50.0 against the 5 other services' median of 7.3 (8.6 robust MADs above, six-hour window). This compares the service with its peers, not with its own history — the seasonal detector does that.
A feedsvc query shape on test26 has p95 4.8 s in the second half of the window against 28 ms in the first (172.7×, 3,394 executions). The shape reads: “RETURN EXISTS { MATCH (cfg2:WorkplanCfg) WHERE cfg2.progressPending = true AND coalesce(cfg2.lastViewedAtMs, ?) > (times…”. Slower can mean more data, a lost index, or lock contention — the shape page has the CPU/wait split. Shapes whose p95 stays under a second are never reported: below that nobody notices, whatever the ratio.
patientsvc's p99 latency (ms) is 1.75 s against the 5 other services' median of 530 ms (5.5 robust MADs above, six-hour window). This compares the service with its peers, not with its own history — the seasonal detector does that.
execsvc differs from the other 5 services on 2 measures over six hours: p99 latency (ms) 1.95 s against the peers' 530 ms (6.4 MADs above); p95 latency (ms) 1.48 s against the peers' 257 ms (5.0 MADs above). Peer comparison is structural more often than it is news — a service that does more work per request will sit here for as long as it does — which is why this is informational unless it is about failures.
Pod cannot start: execsvc (tilda) image pull failing for at least 13 min — 1 pod. Facts: namespace tilda, workload execsvc, why image pull failing, pending_minutes 13, since 1794901864.
the whole test26 cluster's request rate is 56.4 req/min on test26, above a normal of 0.5 req/min ± 0.7 req/min for this hour of the week (4 of the last 4 five-minute buckets, z = 75.4, 5 weeks of history). Whether users noticed depends on which endpoints carried it — the service page shows the split.
The background job pubsub.study-smo-binding-test26-enrollsub on test26 failed 5 runs recently (4,845 failure lines; lines within one run count once), detected via its ERROR-severity log lines. A job that logs its failures below ERROR severity — a WARNING carrying an error field — is invisible to the novel-shape detector and to the page's own failed count; this detector reads the error field itself, which is why the finding now appears. The sample failure is in the facts.
docsvc's p99 latency (ms) is 3.64 s against the 6 other services' median of 368 ms (8.1 robust MADs above, six-hour window). This compares the service with its peers, not with its own history — the seasonal detector does that.