Queue for the week below, handed over from Meera. Repo: /workspace/monitoring. Read README first, the catalog and ownership file are authoritative. Incident data is in incidents/; replay it with bin/range2test if you want to be sure before merging. CI is bin/af-check.
Background: clinical-ops was split off from provider-data on the 18th. prior-auth-svc and fax-ingest are clinical-ops' now, per teams/ownership.yaml, and a few tickets below come out of that.
Queue
SRE-2696: clinical-ops tickets land in provider-data's Jira
Reporter: Annika | opened today | component: ownership
The prior-auth-svc and fax-ingest alerts still say team: provider-data, so clinical-ops' tickets end up in provider-data's project. ownership.yaml was updated on the 18th; the rules weren't.
hannah.p: no rush from our side, but please don't drop it
SRE-2886: page storm during the db failover (claims)
Reporter: Meera | opened last week | component: alerting
18 PagerDuty incidents in three minutes, one per pod of claims-api and adjudication-worker. The PD export, our alert channel and #sre-fyi from that night are in incidents/INC-3766/.
SRE-2223: route clinical-ops
Reporter: Annika | opened yesterday | component: routing
clinical-ops have their PagerDuty service and Slack channel now (receivers pagerduty-clinical-ops, slack-clinical-ops, jira-clinical-ops are there already). Route their alerts per the routing policy in README.
SRE-2763: the member-api error-ratio alert pages on every canary
Four pages this week, each one within a quarter of an hour of a canary going out, each one resolved by itself when the canary was promoted. The load balancer shows 0.2% errors on member-api the whole time. Sandeep has stopped trusting this alert, which is the real problem. Sandeep raised the threshold from 5% to 20% as a stopgap after the last one (INC-3775); see the TODO on the rule. Deploy log, PD export and the pod-level pull are in incidents/INC-3775/.
SRE-2302: payer-integrations: new alerts channel
Reporter: Nikhil | opened 3 days ago | component: routing
payer-integrations' alerts channel is #payer-integrations-oncall from now on (slack-payer-integrations-oncall). The old one is being archived, so nothing may route to slack-payer-integrations after this.
SRE-2258: AdjudicationWorkerQueueBacklogHigh to page
Reporter: Arjun | opened today | component: alerting
We agreed in the ops review that AdjudicationWorkerQueueBacklogHigh should wake someone up. Right now it only posts to Slack.
SRE-2639: ClaimsApiDbConnectionsHigh runbook link 404s
Reporter: Karthik | opened last week | component: alerting
The runbook link on ClaimsApiDbConnectionsHigh goes to the old wiki, which 404s since the migration. There is a runbook for it in the repo.
SRE-2470: ProviderDirLatencyHigh notifications end mid-sentence
ProviderDirLatencyHigh notifications end mid-sentence ("... on"). Please make them say what they're about.
Notes
- Land everything in the repo; rules under
rules/, routing inalertmanager/alertmanager.yml. - Leave alone what the queue doesn't ask for.
promtool,amtool,bin/af-checkandbin/range2testare on the path. Done means the queue is handled andbin/af-checkpasses.