feat(internal): Add support for parsing a timestamp in a TimeZone #17080
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.
Summary
This PR adds new options in Time parsing for metrics.
The new options:
are similar to corresponding
unix
timestamp parsing with the only difference is that thetimestamp_tz
time is parsed in a Timezone which is set via Timezone-related configuration options.
The motivation is to cover cases when metrics are collected from devices which do not have a concept of Timezone, UNIX time etc but still return time as "number of seconds since UNIX time but in Local timezone".
Please take a look at a discussion in #16875
Checklist
Related issues
resolves #16875