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
no logs in sudo journalctl -u otel-collector -l --no-pager -g redaction
tested on otelcol-contrib 0.111.0 and 0.122.0 on Linux Ubuntu 22.04 LTS
It's not very clear what happens, is it the whole log record that is masked/hashed or just the attribute?
but if attribute is easily defined in json/xml, what about string log?
imho, clearer when defined as a regex with (group) match. like '/password=([^\s;]*)/password=REDACTED/'
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm testing on nginx web logs with query like "https://test.example.com/otel-redaction-testing/?visa_credit=4222222222222"
nginx is saving logs in json with fields request, uri and query_parameters where I would expect data to be redacted.
Following config is not working
no logs in
sudo journalctl -u otel-collector -l --no-pager -g redaction
tested on otelcol-contrib 0.111.0 and 0.122.0 on Linux Ubuntu 22.04 LTS
It's not very clear what happens, is it the whole log record that is masked/hashed or just the attribute?
but if attribute is easily defined in json/xml, what about string log?
imho, clearer when defined as a regex with (group) match. like '/password=([^\s;]*)/password=REDACTED/'
Beta Was this translation helpful? Give feedback.
All reactions