docs: explain PowerShell 5 encoding #11662
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PowerShell 5 is the default version of PowerShell in Windows 10 and
older versions. It does not default to UTF-8 encoding, which can cause
issues with Telegraf trying to parse the file.
Rather than adding lots of weird logic to Telegraf, document the
the requirement to specify the encoding when using PowerShell 5.
Newer versions of PowerShell now use UTF-8 encoding.
Fixes: #11614
Fixes: #4880
Fixes: #6662