Skip to content

Commit

Permalink
Merge branch 'master' into kubectl-job
Browse files Browse the repository at this point in the history
  • Loading branch information
Avi-Robusta authored Jan 5, 2025
2 parents 40934f3 + 4602c2e commit 35fe7e5
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 7 deletions.
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
Track Failed Liveness Probes
##############################

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

Defining a Playbook
Define a Playbook to Track Liveness Probes
-----------------------------------------------------

Add the following YAML to the ``customPlaybooks`` Helm value:
Expand Down Expand Up @@ -34,7 +34,9 @@ Apply the following command the create a failing liveness probe.
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/liveness_probe_fail/failing_liveness_probe.yaml
.. details:: Output
You should get a notification in your configured sink.

.. details:: Example Slack Notification

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

This playbook uses the :ref:`on_kubernetes_warning_event_create<on_kubernetes_warning_event_create>` trigger, that fires once for each Liveness probe failure.
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.

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.

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
Track Failed Kubernetes Jobs
##############################

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

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

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

Defining a Playbook
Defining a Playbook to Track Failed Jobs
------------------------------------------

Add the following YAML to the ``customPlaybooks`` Helm value:
Expand Down

0 comments on commit 35fe7e5

Please sign in to comment.