You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/setup-robusta/additional-settings.rst
+34-38Lines changed: 34 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,65 +144,61 @@ To **enable** interactivity, set the following in your `generated_values.yaml` f
144
144
Censoring Logs
145
145
----------------
146
146
147
-
Pod logs gathered by Robusta can be censored using regexes. For example, a payment processing pod might have credit card numbers in its log. These can be sanitized in-cluster.
147
+
Pod logs gathered by Robusta can be censored using `Python regular expressions <https://www.w3schools.com/python/python_regex.asp>`_. For example, a payment processing pod might have credit card numbers or other sensitive information in its logs. These can be automatically sanitized before they appear in notifications.
148
148
149
-
This feature applies to the following Robusta actions:
149
+
**How to Enable Log Censoring for All Logs**
150
150
151
-
- :code:`logs_enricher`
152
-
- :code:`report_crash_loop`
151
+
To censor sensitive information in all logs, add the following to your Helm values file:
153
152
154
-
To censor logs, define a `python regex <https://www.w3schools.com/python/python_regex.asp>`_ for expressions you wish to filter.
153
+
.. code-block:: yaml
155
154
156
-
For example:
155
+
globalConfig:
156
+
regex_replacement_style: SAME_LENGTH_ASTERISKS # Alternative: NAMED
0 commit comments