Skip to content

Commit c563d92

Browse files
committed
more fixes
1 parent 9822092 commit c563d92

13 files changed

Lines changed: 16 additions & 215 deletions

File tree

docs/conf.py

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,9 @@
213213
"how-it-works/alert-builtin-enrichment.html": "/master/playbook-reference/builtin-alert-enrichment.html",
214214
"setup-robusta/installation/extend-prometheus-installation.html": "/master/setup-robusta/installation/standalone-installation.html",
215215
"playbook-reference/defining-playbooks/index.html": "/master/playbook-reference/index.html",
216-
"configuration/alertmanager-integration/alert-custom-prometheus.html": "/master/configuration/alertmanager-integration/embedded-prometheus.html#creating-custom-prometheus-alerts"
216+
"configuration/alertmanager-integration/alert-custom-prometheus.html": "/master/configuration/alertmanager-integration/embedded-prometheus.html#creating-custom-prometheus-alerts",
217+
"configuration/alertmanager-integration/index.html": "/master/configuration/index.html",
218+
"notification-routing/notification-routing-examples.html": "/master/notification-routing/index.html"
217219
}
218220

219221

docs/configuration/alertmanager-integration/index.rst

Lines changed: 0 additions & 82 deletions
This file was deleted.

docs/notification-routing/notification-routing-examples.rst

Lines changed: 0 additions & 79 deletions
This file was deleted.

docs/notification-routing/routing-with-scopes.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -324,7 +324,7 @@ Here is the complete list of attributes that can be used in ``include`` / ``excl
324324
+---------------------+-----------------------------------------------------------+------------------------------------------+
325325
| ``annotations`` | Same as Kubernetes selectors: a comma-separated list of | Can refer to both Kubernetes resource |
326326
| | ``key=val`` pairs with AND between them. e.g. | annotations and Prometheus alert |
327-
| | ``app.kubernetes.io/name=prometheus``. Supports regex in | annotations. Prometheus values |
327+
| | ``app.kubernetes.io/name=prometheus``. Supports regex in | annotations. Prometheus values |
328328
| | the value. | are prioritized when both exist. |
329329
+---------------------+-----------------------------------------------------------+------------------------------------------+
330330
| ``namespace_labels``| Labels on the Kubernetes namespace containing this object.| Same matching syntax as ``labels``. For |

docs/playbook-reference/actions/scans.rst

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,4 @@ These actions can be triggered:
99
* On demand, via the Robusta UI.
1010
* On demand, via :ref:`cli command <Manual Triggers>`.
1111

12-
There are two built-in KRR and Popeye, you can find more details below.
13-
14-
* :ref:`Cost Savings (KRR)`
15-
* :ref:`Kubernetes Misconfigurations (Popeye)`
12+
There are two built-in: KRR and Popeye.

docs/playbook-reference/defining-playbooks/builtin-playbooks.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The following default playbook handles all Prometheus alerts that Robusta receiv
2525
2626
There are additional enrichments for specific alerts. For example:
2727

28-
To define additional playbooks for your own alerts, refer to the :ref:`Enhanced Prometheus Alerts` tutorial.
28+
To define additional playbooks for your own alerts, refer to the :doc:`Custom Alert Enrichment </playbook-reference/prometheus-examples/index>` guide.
2929

3030
Default Prometheus Silencing
3131
--------------------------------
@@ -34,4 +34,4 @@ Robusta uses *silencer* actions to flag false positive alerts and prevent them f
3434

3535
Silencers are just regular actions that call a special silencing API in their code.
3636

37-
To define your own silencers, refer to the :ref:`Silencing Prometheus Alerts` tutorial.
37+
To define your own silencers, refer to the playbook actions documentation.

docs/playbook-reference/defining-playbooks/playbook-basics.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Playbook Basics
55

66
A playbook is an automation rule for detecting, investigating, or fixing problems in your cluster.
77

8-
For a gentle introduction, see :ref:`What are Playbooks?<how-it-works-index>`
8+
For a gentle introduction, see :doc:`Playbook Overview </playbook-reference/overview>`
99

1010
Overview
1111
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

docs/playbook-reference/triggers/kubernetes.rst

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,7 @@ These triggers work even when Prometheus is not connected to Robusta. They're tr
99

1010
.. details:: Related Tutorials
1111

12-
* :ref:`Track Failed Kubernetes Jobs`
13-
* :ref:`Track Failed Liveness Probes`
14-
* :ref:`Track Kubernetes Changes`
12+
* :doc:`Kubernetes Change Notifications </playbook-reference/kubernetes-examples/kubernetes-change-notifications>`
1513

1614

1715
Crashing Pod Triggers
@@ -81,7 +79,7 @@ The following triggers are available for crashing Pods:
8179
* If A `name` is defined without a `namespace` than all containers with that name prefix will be ignored for this trigger.
8280
* If A `namespace` is defined without a `name` than all containers in that namespace will be ignored for this trigger.
8381

84-
An example playbook using :ref:`oomkilled_container_graph_enricher<oomkilled_container_graph_enricher>`:
82+
An example playbook using ``oomkilled_container_graph_enricher``:
8583

8684
.. code-block:: yaml
8785

docs/playbook-reference/triggers/prometheus.rst

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
Prometheus and AlertManager
22
#############################
33

4-
Robusta can :ref:`improve your existing Prometheus alerts <Enhanced Prometheus Alerts>`. It can also execute
5-
:ref:`Remediation Actions <Automatic Remediation>` in response to alerts.
4+
Robusta can improve your existing Prometheus alerts. It can also execute automated remediation actions in response to alerts.
65

76
Prerequisites
87
---------------
9-
AlertManager must be connected to Robusta. Refer to :ref:`Integrating AlertManager and Prometheus`.
8+
AlertManager must be connected to Robusta. Refer to the :doc:`Send Alerts </configuration/index>` documentation.
109

1110
Triggers
1211
-----------

docs/setup-robusta/installation-faq.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Yes, using the cli is optional. It auto-generates helm values, but you can also
1717
helm repo add robusta https://robusta-charts.storage.googleapis.com && helm repo update
1818
helm show values robusta/robusta
1919
20-
2. Modify those values to your heart's content. Refer to the :ref:`Integration Guide <Integrations Overview>` for details.
20+
2. Modify those values to your heart's content. Refer to the :doc:`Send Alerts </configuration/index>` documentation for details.
2121

2222
3. Do a ``helm install``.
2323

@@ -52,7 +52,7 @@ Verify success by checking that Robusta pods are running:
5252

5353
Does Robusta support Thanos/Cortex/Mimir/VictoriaMetrics?
5454
============================================================
55-
Any Prometheus-compatible solution is fine. Just follow instructions under :ref:`Integrate with Existing Prometheus`
55+
Any Prometheus-compatible solution is fine. Just follow instructions in the :doc:`Send Alerts </configuration/index>` documentation.
5656

5757
Can I use Robusta with DataDog?
5858
============================================================

0 commit comments

Comments
 (0)