feat: outage tracker #611

New issue

Closed

opened 2026-03-28 04:26:24 +00:00 by mfreeman451 · 1 comment

mfreeman451 commented

2026-03-28 04:26:24 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #1874
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1874
Original created: 2025-10-24T03:36:28Z

Is your feature request related to a problem?

Track outages across major cloud providers, we can use this data later to correlate outages in a customers environment and create contextual visuals+enriched metadata in a topology map (customer has a networks A, B, C -- C is in AWS and there is an outage, we could indicate that in a network topo map)

Describe the solution you'd like

write scraper framework in golang or python
build as a checker service
configure poller to poll outage service
needs new pkg in core API to handle data
add to bazel
depends on fully mapped service dependencies

Mapping service dependencies deserves its own issue, but at a high level what this means is that we:

Understand where a service lives, either programmatically or implicitly (IPAM, NetBox, Armis, etc)
Understand the relationships between a service and infra layers
Understand where infra lives
Understand connections between hybrid-cloud environments
Understand SLAs
Correlate Business Value to Services (This group of services/infra runs the Corporate Finance system)

Describe alternatives you've considered

TBD -- more research could be done around this, we might not need scrapers, there may be public APIs, etc.

Additional context

Recent AWS outages

Imported from GitHub. Original GitHub issue: #1874 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1874 Original created: 2025-10-24T03:36:28Z --- **Is your feature request related to a problem?** Track outages across major cloud providers, we can use this data later to correlate outages in a customers environment and create contextual visuals+enriched metadata in a topology map (customer has a networks A, B, C -- C is in AWS and there is an outage, we could indicate that in a network topo map) **Describe the solution you'd like** - [ ] write scraper framework in golang or python - [ ] build as a [checker service](https://docs.serviceradar.cloud/docs/custom-checkers) - [ ] configure [poller](https://github.com/carverauto/serviceradar/blob/main/packaging/poller/config/poller.json) to poll outage service - [ ] needs new pkg in core API to handle data - [ ] add to bazel - [ ] depends on fully mapped service dependencies Mapping service dependencies deserves its own issue, but at a high level what this means is that we: - Understand where a service lives, either programmatically or implicitly (IPAM, NetBox, Armis, etc) - Understand the relationships between a service and infra layers - Understand where infra lives - Understand connections between hybrid-cloud environments - Understand SLAs - Correlate Business Value to Services (This group of services/infra runs the Corporate Finance system) **Describe alternatives you've considered** TBD -- more research could be done around this, we might not need scrapers, there may be public APIs, etc. **Additional context** Recent AWS outages

mfreeman451 added the

help wanted

good first issue

labels

2026-03-28 04:26:24 +00:00

mfreeman451 commented

2026-03-28 04:26:24 +00:00

Author

Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1874#issuecomment-3813920034
Original created: 2026-01-28T21:03:05Z

closing, not planned

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1874#issuecomment-3813920034 Original created: 2026-01-28T21:03:05Z --- closing, not planned

mfreeman451 closed this issue

2026-03-28 04:26:25 +00:00