Add operator runbooks (open-telemetry#5131)

Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
Co-authored-by: opentelemetrybot <[email protected]>

.cspell/en-words.txt

@@ -107,6 +107,8 @@ recommendationservice
 redis
 relref
 Rexed
+runbook
+runbooks
 Rynn
 semconv
 servlet

content/en/blog/2024/demo-skyscanner/index.md

@@ -6,7 +6,7 @@ linkTitle: Skyscanner using OTel Demo
 date: 2024-02-26
 author: >-
   [Jordi Bisbal Ansaldo](https://github.com/jordibisbal8) (Skyscanner)
-cSpell:ignore: Ansaldo Bisbal Jordi runbooks Skyscanner upskilled Yankova
+cSpell:ignore: Ansaldo Bisbal Jordi Skyscanner upskilled Yankova
 ---
 
 At [Skyscanner](https://www.skyscanner.net), as in many organizations, teams

content/en/docs/kubernetes/operator/troubleshooting/prometheus-alerts-runbooks.md

@@ -0,0 +1,23 @@
+---
+title: Prometheus Alerts Runbooks
+---
+
+## Manager Rules
+
+### ReconcileErrors
+
+|            |                                                                                                                                   |
+| ---------: | --------------------------------------------------------------------------------------------------------------------------------- |
+|    Meaning | The OpenTelemetry Operator cannot succeed in the reconciliation step, probably because of a misconfigured OpenTelemetryCollector. |
+|     Impact | No impact on already running deployments or new correct ones.                                                                     |
+|  Diagnosis | Check manager logs for reasons why this might happen.                                                                             |
+| Mitigation | Find out which OpenTelemetryCollector is causing the errors and fix the config.                                                   |
+
+### WorkqueueDepth
+
+|            |                                                                                                          |
+| ---------: | -------------------------------------------------------------------------------------------------------- |
+|    Meaning | The working queue for the operator is larger than 0.                                                     |
+|     Impact | No impact if the queue depth reverts to 0 quickly. More investigation is needed if the problem persists. |
+|  Diagnosis | Check manager logs for reasons why this might happen.                                                    |
+| Mitigation | This could be caused by many errors. Act based on what the logs are showing.                             |