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
Access log anonymizing can be a super helpful feature to have in Tango. Usually, there are needs to pass/show access logs to 3rd-parties, but not always it's possible to show customer/visitor data
Expected behavior
A new CLI command that would process the data according to passed anonymizer params and would save the access log file in the same raw format (not CSV as Tango normally does).
Benefits
zero effort to make access log data anonymized
possibility to share access log data with 3rd-parties without fear to have legal issues
Additional information
The following data seems to be useful to anonymize:
visitor IPs
access URIs
user agents
timezone
It may be useful to add the ability to replace some specific lines in the access logs (like googlable vendor names).
Also, anonymized of data should show visitor actions as close as possible to the original file. This means that would be great to keep for IP and URI, User-Agent of the visitor the same along with the whole access log.
Example1. If we anonymize IP 1.1.1.1 to 250.2.3.50, IP 250.2.3.50 should be used everywhere where we need to close information about IP 1.1.1.1.
Example2. If we want to hide information about URI "/automobile-windows" and anonymize it to "/category100", then we need to use "/category100" everywhere where it comes to the original URI.
Such a strategy helps to keep relations in the access log and pass it to other parties.
The text was updated successfully, but these errors were encountered:
Description
Access log anonymizing can be a super helpful feature to have in Tango. Usually, there are needs to pass/show access logs to 3rd-parties, but not always it's possible to show customer/visitor data
Expected behavior
A new CLI command that would process the data according to passed anonymizer params and would save the access log file in the same raw format (not CSV as Tango normally does).
Benefits
Additional information
The following data seems to be useful to anonymize:
It may be useful to add the ability to replace some specific lines in the access logs (like googlable vendor names).
Also, anonymized of data should show visitor actions as close as possible to the original file. This means that would be great to keep for IP and URI, User-Agent of the visitor the same along with the whole access log.
Example1. If we anonymize IP 1.1.1.1 to 250.2.3.50, IP 250.2.3.50 should be used everywhere where we need to close information about IP 1.1.1.1.
Example2. If we want to hide information about URI "/automobile-windows" and anonymize it to "/category100", then we need to use "/category100" everywhere where it comes to the original URI.
Such a strategy helps to keep relations in the access log and pass it to other parties.
The text was updated successfully, but these errors were encountered: