Skip to content

Commit 35fe7e5

Browse files
authored
Merge branch 'master' into kubectl-job
2 parents 40934f3 + 4602c2e commit 35fe7e5

File tree

2 files changed

+9
-7
lines changed

2 files changed

+9
-7
lines changed

docs/playbook-reference/kubernetes-examples/playbook-failed-liveness.rst

+7-5
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
Track Failed Liveness Probes
22
##############################
33

4-
Lets track failed Liveness Probes and notify the user. Notifications will be sent to all configured :ref:`Sinks <Sinks Reference>`
5-
like Slack, MSTeams, or DataDog. It is also possible to :ref:`route notifications to specific sinks<Routing Alerts to Specific Sinks>`.
4+
Lets track failed Liveness Probes and notify the user. Notifications will be sent to configured :ref:`Sinks <Sinks Reference>`
5+
like Slack or MSTeams. It is also possible to :ref:`route notifications to specific sinks<Routing Alerts to Specific Sinks>`.
66

7-
Defining a Playbook
7+
Define a Playbook to Track Liveness Probes
88
-----------------------------------------------------
99

1010
Add the following YAML to the ``customPlaybooks`` Helm value:
@@ -34,7 +34,9 @@ Apply the following command the create a failing liveness probe.
3434
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/liveness_probe_fail/failing_liveness_probe.yaml
3535
3636
37-
.. details:: Output
37+
You should get a notification in your configured sink.
38+
39+
.. details:: Example Slack Notification
3840

3941
.. image:: /images/failedlivenessprobe.png
4042
:alt: Failed liveness probe notification on Slack
@@ -43,7 +45,7 @@ Apply the following command the create a failing liveness probe.
4345
How it Works
4446
-------------
4547

46-
This playbook uses the :ref:`on_kubernetes_warning_event_create<on_kubernetes_warning_event_create>` trigger, that fires once for each Liveness probe failure.
48+
This playbook uses the :ref:`on_kubernetes_warning_event_create<on_kubernetes_warning_event_create>` trigger, which fires for Liveness probe failures in your cluster.
4749

4850
It uses the :ref:`create_finding <create_finding>` action to generate a notification message, and :ref:`event_resource_events <event_resource_events>` action to gather all other events on the same resource in the near past.
4951

docs/playbook-reference/kubernetes-examples/playbook-job-failure.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
Track Failed Kubernetes Jobs
22
##############################
33

4-
Notify about failed Kubernetes Jobs in Slack, MSTeams, DataDog, or other :ref:`Sinks <Sinks Reference>`.
4+
Notify about failed Kubernetes Jobs in Slack, MSTeams or other :ref:`Sinks <Sinks Reference>`.
55

66
.. image:: /images/failingjobs.png
77
:alt: Failing Kubernetes jobs notification on Slack
@@ -11,7 +11,7 @@ Notify about failed Kubernetes Jobs in Slack, MSTeams, DataDog, or other :ref:`S
1111

1212
If you installed Robusta with the embedded Prometheus stack, you don't need to configure this playbook. It's configured by default.
1313

14-
Defining a Playbook
14+
Defining a Playbook to Track Failed Jobs
1515
------------------------------------------
1616

1717
Add the following YAML to the ``customPlaybooks`` Helm value:

0 commit comments

Comments
 (0)