- Budget approval to cover the cost of the public cloud provider: [Yes/No] @hnowlan
- Why the use case cannot be run on the available bare metal or Wikimedia Cloud infrastructure:
- The Icinga meta-monitoring is currently running on a Rackspace VPS. We need to keep it outside our main infrastructure to avoid a situation where a disruption in our environment could impact the meta-monitoring stack itself.
- What kind of data it is going to handle/need:
- Mainly the data exported by: Extended information CGI - https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/cgis.html#extinfo_cgi.
- What is the expected project's timeline (how long is it expected to run, etc..):
- It’s expected to run (at least) until the end of FY 25/26.
- List of users to add to the organization:
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Andrew | T376400 Redesign wikitech-static | |||
| Open | None | T281812 Audit/Assess meta monitoring strategy | |||
| Unknown Object (Task) | |||||
| Invalid | LSobanski | T409076 Public cloud account request for moving meta monitoring off of wikitech-static |
Event Timeline
Comment Actions
Please hold off on working on this task until further notice.
We may have found a way to handle the Icinga meta-monitoring reliably using the same approach as the Prometheus/Thanos meta-monitor.
Comment Actions
I think we can close this ticket as we won't need a public cloud account for this work, can you confirm @tappof?