Icon

04_​Remove_​Personal_​Information_​from_​KNIME_​Server_​Log_​Files

Remove Personal Information from KNIME Server Log Files

Masks IPs, email addresses, and usernames in KNIME Server Logs for all standard cases.

How it's used
Most conveniently, it's executed as a Data App on KNIME Server where the logs are stored and the workflow will fetch logs automatically.
You can also execute the workflow locally and enter the server credentials manually to access the current server logs.
In case the server is not reachable or you have a set of logs already, you can execute the workflow locally and provide the logs as a zip file.
Please remember that this is a workflow you can modify and extend to your specific needs.

What it does
With this Data App, KNIME Server log files can be depersonalized in a way such that IPs, email addresses, and usernames are masked. Emails and IP addresses (IPv4 and IPv6) are both detected via regex and any match will be masked (see linked websites below). Usernames are determined from
- KNIME Server internal DB
- Foldernames in the /Users folder
- Usernames that occur in the localhost access logs.
There can be no guarantee that this workflow removes "all personal information" , since an organization may have naming protocols for different aspects of KNIME that KNIME can know nothing about. The list of search/replace criteria can therefore be extended by providing a CSV File containing a column "username" to extend the list.

Usernames and IP addresses found in the localhost_access logs will receive a mapping throughout all logs (Eva Musterfrau -> , Max Mustermann -> , ... and 127.0.0.2 -> , 127.0.0.3 -> , ...), everything else that matches will be masked with a generic tag (personal@example.com -> , generic@example.com -> , ...).

Possible processed log files
- localhost_access
- localhost
- catalina
- the executor log (KNIME log) can also be processed but is very large and not usually needed for support purposes, therefore processing this log is by default NOT done unless the setting is overwritten.

Remove Personal Information from KNIME Server Log FilesFor Analytics Platform/Executor 4.6.5 and above Masks IPs, email addresses, and usernames in KNIME Server Logs for all standard cases.How it's usedMost conveniently, it's executed as a Data App on KNIME Server where the logs are stored and the workflow will fetch logsautomatically. You can also execute the workflow locally and enter the server credentials manually to access the current server logs.In case the server is not reachable or you have a set of logs already, you can execute the workflow locally and provide the logs as a zipfile. Please remember that this is a workflow you can modify and extend to your specific needs. What it doesWith this Data App, KNIME Server log files can be depersonalized in a way such that IPs, email addresses, and usernames aremasked. Emails [1] and IP addresses (IPv4 and IPv6) [2] are both detected via regex and any match will be masked. Usernames aredetermined from - KNIME Server internal DB - Foldernames in the /Users folder - Usernames that occur in the localhost access logs.There can be no guarantee that this workflow removes "all personal information" , since an organization may have naming protocolsfor different aspects of KNIME that KNIME can know nothing about. The list of search/replace criteria can therefore be extended byproviding a CSV File containing a column "username" to extend the list.Usernames and IP addresses found in the localhost_access logs will receive a mapping throughout all logs (Eva Musterfrau -> , MaxMustermann -> , ... and 127.0.0.2 -> , 127.0.0.3 -> , ...), everything else that matches will be masked with a generic tag(personal@example.com -> , generic@example.com -> , ...).Possible processed log files include - localhost_access - localhost - catalina - the executor log (KNIME log) can also be processed but is very large and not usually needed for support purposes, thereforeprocessing this log is by default NOT done unless the setting is overwritten.[1]: IPv4 and IPv6 Regex from https://regex101.com/library/ZjrE6t?amp%3Bpage=7&filterFlavors=javascript&filterFlavors=pcre&orderBy=MOST_RECENT&page=24[2]: Email Regex from https://emailregex.com If running locally,open the interactive viewIf running locally,open the interactive view Results Page Settings Process Logs Remove Personal Information from KNIME Server Log FilesFor Analytics Platform/Executor 4.6.5 and above Masks IPs, email addresses, and usernames in KNIME Server Logs for all standard cases.How it's usedMost conveniently, it's executed as a Data App on KNIME Server where the logs are stored and the workflow will fetch logsautomatically. You can also execute the workflow locally and enter the server credentials manually to access the current server logs.In case the server is not reachable or you have a set of logs already, you can execute the workflow locally and provide the logs as a zipfile. Please remember that this is a workflow you can modify and extend to your specific needs. What it doesWith this Data App, KNIME Server log files can be depersonalized in a way such that IPs, email addresses, and usernames aremasked. Emails [1] and IP addresses (IPv4 and IPv6) [2] are both detected via regex and any match will be masked. Usernames aredetermined from - KNIME Server internal DB - Foldernames in the /Users folder - Usernames that occur in the localhost access logs.There can be no guarantee that this workflow removes "all personal information" , since an organization may have naming protocolsfor different aspects of KNIME that KNIME can know nothing about. The list of search/replace criteria can therefore be extended byproviding a CSV File containing a column "username" to extend the list.Usernames and IP addresses found in the localhost_access logs will receive a mapping throughout all logs (Eva Musterfrau -> , MaxMustermann -> , ... and 127.0.0.2 -> , 127.0.0.3 -> , ...), everything else that matches will be masked with a generic tag(personal@example.com -> , generic@example.com -> , ...).Possible processed log files include - localhost_access - localhost - catalina - the executor log (KNIME log) can also be processed but is very large and not usually needed for support purposes, thereforeprocessing this log is by default NOT done unless the setting is overwritten.[1]: IPv4 and IPv6 Regex from https://regex101.com/library/ZjrE6t?amp%3Bpage=7&filterFlavors=javascript&filterFlavors=pcre&orderBy=MOST_RECENT&page=24[2]: Email Regex from https://emailregex.com If running locally,open the interactive viewIf running locally,open the interactive view Results Page Settings Process Logs

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: Lukas.Siedentop
Created at: 2024-02-23
On NodePit since: 2024-03-01
Last update: 2024-04-27
Created with KNIME version: v4.6.5
Tags: Workflow ApplicationKNIME Server

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!