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
The capturing of this data can be turned off by setting Capture personal data to false.
Here's the flag mentioned in the quote, within Integrations > Elastic APM > Elastic APM:
But the quote isn't accurate, as the capturing of client data such as client.ip cannot be deactivated and as a result such data appear in the logs.
As of now the only way to block such information entering the logs is reducting it using a filter on the client side.
So, the above line can be confusing as a user might expect that by switching the "Capture personal data" to false no personal data such as client.ip will go through the APM server into Kibana.
Summing up, I believe there should be a more explicit explanation of what is not being captured when this flag is deactivated.
Thanks
The text was updated successfully, but these errors were encountered:
Hello,
In the documentation it writes:
Here's the flag mentioned in the quote, within
Integrations > Elastic APM > Elastic APM
:But the quote isn't accurate, as the capturing of client data such as
client.ip
cannot be deactivated and as a result such data appear in the logs.As of now the only way to block such information entering the logs is reducting it using a filter on the client side.
So, the above line can be confusing as a user might expect that by switching the "Capture personal data" to false no personal data such as
client.ip
will go through the APM server into Kibana.Summing up, I believe there should be a more explicit explanation of what is not being captured when this flag is deactivated.
Thanks
The text was updated successfully, but these errors were encountered: