Repository navigation
Add PagerDuty services for bootstrap, content and route-origin - #42
Merged
Merged
Conversation
These priority services on the k3s boxes are paged today through the needle service, so an incident doesn't say which service is down. Give each its own service and Events API v2 integration, with prevent_destroy like the others, and expose their keys as sensitive outputs for the hub's Alertmanager. Box-level alerts stay on needle. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Terraform plan:
|
The names now say what each service is (Delegated routing (needle), Routing origin (route-origin), IPFS bootstrap peers (bootstrap), IPFS website hosting (content), IPNI indexers (cid.contact), Service Worker Gateway (inbrowser.link)), and each description says what it does before who pages it. Renaming the three existing services is an in-place update; their integration keys don't change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3 of 4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
bootstrap, content and route-origin, the other priority services on the k3s boxes (sing1, lith1, chic1), are paged today through the needle service by the hub's Alertmanager (ipni/infra, lith1), so an incident doesn't say which service is down.
This gives each its own PagerDuty service on the IPNI escalation policy, with an Events API v2 integration (
prevent_destroy, like the others) and its routing key as a sensitive output:bootstrap_integration_keycontent_integration_keyroute_origin_integration_keyBox-level alerts stay on needle.
Every service is also named and described by what it does, so a page says it at a glance:
swgindexersneedleroute_originbootstrapcontentRenaming the three existing services is an in-place update; their integration keys (and the Cloudflare connection on the gateway) don't change. Nothing pages the new services until Alertmanager routes to them; that follows in ipni/infra once this is applied (keys in
alertmanager-secrets, routes inkube-prometheus-stack.yaml, and the Paging docs).Expected plan
pagerduty_service, 3pagerduty_service_integration), 3 to change (name and description ofswg,indexers,needle), 0 to destroy.Checklist
inbrowser.devbeforeinbrowser.link(no zone changes)🤖 Generated with Claude Code