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
added a safeguard for processors that raise exceptions (#1138)
* added a safeguard for processors that raise exceptions
Without this safeguard, exceptions in processors would bubble all the way
up, killing the transport thread. This would then result in the agent
stopping to report any data.
* fix style issue
Copy file name to clipboardExpand all lines: docs/sanitizing-data.asciidoc
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,9 @@ and returns the modified event.
10
10
11
11
To completely drop an event, your processor should return `False` (or any other "falsy" value) instead of the event.
12
12
13
+
An event will also be dropped if any processor raises an exception while processing it.
14
+
A log message with level `WARNING` will be issued in this case.
15
+
13
16
This is an example of a processor that removes the exception stacktrace from an error:
14
17
15
18
[source,python]
@@ -46,7 +49,7 @@ ELASTIC_APM = {
46
49
}
47
50
----
48
51
49
-
NOTE: We recommend to use the above list of processors that sanitize passwords and secrets in different places of the event object.
52
+
NOTE: We recommend using the above list of processors that sanitize passwords and secrets in different places of the event object.
50
53
51
54
The default set of processors sanitize fields based on a set of defaults defined in `elasticapm.conf.constants`. This set can be configured with the `SANITIZE_FIELD_NAMES` configuration option. For example, if your application produces a sensitive field called `My-Sensitive-Field`, the default processors can be used to automatically sanitize this field. You can specify what fields to santize within default processors like this:
0 commit comments