This project provides guidance for those wonderful operations members who are technically "on the hook" for all Cyberia-related production services, _especially_
Informational alerts are free to be ignored, but indicate curious happenings in our infrastructure. Operations members are not expected to look at or react to these.
#### Critical alerts
```
labels:
severity: critical
```
Critical alerts are those that indicate a failing of one or more of our services.
When a **critical alert** fires, we should respond with a **sense of urgency**.
If a critical alert fires and there was no associated outage, it is our shared responsibility to _eliminate that alert_. All critical alerts must be actionable. If a critical alert can be resolved by a cronjob, it should be resolved by a cronjob and removed as an alert.
## Incidents
Don't panic. If you are feeling overwhelmed, please contact another operations member about the issue at hand.
We will communicate in the #ops:cyberia.club Matrix channel. If that channel is down, we will communicate via [cafe.cyberia.club/ops](https://cafe.cyberia.club/ops)
Communicate your activity. If you are bouncing a machine, please notify #ops that you are bouncing a machine. If you are reloading a service, tell #ops so that people don't step on each others toes. This is also important to establish a timeline.
