This repository was archived by the owner on Oct 23, 2024. It is now read-only.
Fix Timezone field mistmatch #2120
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dani Louca <[email protected]>
dloucasfx
requested review from
keitwb,
jeffreyc-splunk,
mstumpfx,
asuresh4,
rmfitzpatrick and
a team
as code owners
emaderer
approved these changes
Feb 28, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
There is a mismatch between the telegraf struct->field
GrokConfig->Timezonehttps://github.com/signalfx/telegraf/blob/signalfx-agent/plugins/inputs/logparser/logparser.go#L29 and the SA telegraflogparser config struct->fieldConfig → TimeZone(note the upper case Z), this is causing the Timezone setting to NOT be set in telegraf and defaulting to UTC.Signed-off-by: Dani Louca [email protected]