On the demo, about 20 of the 89 open alerts are separate Vault service certificates from one PKI mount, all ending on the same day. Akamai CPS certificates and identical CrashLoopBackOff deployments repeat the same way. Real teams mute a tool that pages like this.
docs/scale-and-availability.md already says one cause should open one incident naming its N affected items.
Do: when several conditions of the same kind come from one source (one issuer or mount, one array, one cluster) and would page in the same window, open one incident: "15 certificates from pki_int in vault-prod end within 21 days", listing the items in the detail (with a cap). An item that gets worse on its own (ends sooner, fails) still escalates the group.
On the demo, about 20 of the 89 open alerts are separate Vault service certificates from one PKI mount, all ending on the same day. Akamai CPS certificates and identical CrashLoopBackOff deployments repeat the same way. Real teams mute a tool that pages like this.
docs/scale-and-availability.md already says one cause should open one incident naming its N affected items.
**Do:** when several conditions of the same kind come from one source (one issuer or mount, one array, one cluster) and would page in the same window, open one incident: "15 certificates from pki_int in vault-prod end within 21 days", listing the items in the detail (with a cap). An item that gets worse on its own (ends sooner, fails) still escalates the group.
Done in #50. After grouping by cause, three or more alike problems from one place are one incident that names them, worst first, at the worst one's severity: certificates ending (by issuer, by Vault mount or cluster namespace, and Akamai CPS's), VMs in one cluster in the same state, and workloads whose pods fail the same way. A member that has already paged stays on its own, and a batch that has paged keeps its incident while any of it is left. Certificates that have ended, or are weak or served wrong, are never batched. Documented in formats.md, Batches. In the next release.
Done in #50. After grouping by cause, three or more alike problems from one place are one incident that names them, worst first, at the worst one's severity: certificates ending (by issuer, by Vault mount or cluster namespace, and Akamai CPS's), VMs in one cluster in the same state, and workloads whose pods fail the same way. A member that has already paged stays on its own, and a batch that has paged keeps its incident while any of it is left. Certificates that have ended, or are weak or served wrong, are never batched. Documented in formats.md, Batches. In the next release.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On the demo, about 20 of the 89 open alerts are separate Vault service certificates from one PKI mount, all ending on the same day. Akamai CPS certificates and identical CrashLoopBackOff deployments repeat the same way. Real teams mute a tool that pages like this.
docs/scale-and-availability.md already says one cause should open one incident naming its N affected items.
Do: when several conditions of the same kind come from one source (one issuer or mount, one array, one cluster) and would page in the same window, open one incident: "15 certificates from pki_int in vault-prod end within 21 days", listing the items in the detail (with a cap). An item that gets worse on its own (ends sooner, fails) still escalates the group.
Done in #50. After grouping by cause, three or more alike problems from one place are one incident that names them, worst first, at the worst one's severity: certificates ending (by issuer, by Vault mount or cluster namespace, and Akamai CPS's), VMs in one cluster in the same state, and workloads whose pods fail the same way. A member that has already paged stays on its own, and a batch that has paged keeps its incident while any of it is left. Certificates that have ended, or are weak or served wrong, are never batched. Documented in formats.md, Batches. In the next release.