Troubleshooting Sanitization
This guide describes and helps users sanitize provided files to hide information for privacy.
On this page
Some users may wish to hide their domain in files provided during troubleshooting. While this is discouraged, if a user decides to perform this action it’s critical for these purposes that you hide your domain in a very specific way. Most editors allow replacing all instances of a value, utilizing this is essential to making troubleshooting possible.
General Rules
- Only replace the purchased portion of domains:
- For example if you have
auth.abc123.com
andapp.abc123.com
they should becomeauth.example.com
andapp.example.com
, i.e. replace all instances ofabc123.com
withexample.com
.
- For example if you have
- Make sure value replaced is replaced with a unique value:
- For example if you replace
abc123.com
withexample.com
DO NOT replace any other value other thanabc123.com
withexample.com
. The same rule applies to IP addresses, usernames, and groups.
- For example if you replace
- Make sure the value replaced is replaced across logs, configuration, and any references:
- For example if you replace
abc123.com
withexample.com
in your configuration, make exactly the same replacement for the log files.
- For example if you replace
- Make sure this consistency is followed for all communication regarding a single issue.
Multiple Domains
Replacement Value: example#.com
(where #
is a unique number per domain)
In instances where there are multiple domains it’s recommended these domains are replaced with example1.com
,
example2.com
, etc.