Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(otel_metrics): use opentelemetry:timestamp/0 (native unit monotonic time) #3

Merged
merged 1 commit into from
Oct 25, 2023

Conversation

SergeTupchiy
Copy link

@SergeTupchiy SergeTupchiy commented Oct 24, 2023

Timestamps are converted to Unix nano timestamps by the exporter.
The previous usage of system_time resulted in treating system_time nanosecond as monotonic time in native time units.

Fixes: emqx/emqx#11802

…onic time)

Timestamps are converted to Unix nano timestamps by the exporter.
Copy link
Collaborator

@zhongwencool zhongwencool left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@SergeTupchiy
Copy link
Author

Thanks @zhongwencool,
this fix was also approved in the upstream repo (open-telemetry#644) but it's hard to predict when it will be merged, so I'll merge this PR and tag a new emqx release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OpenTelemetry exporter uses incorrect timestamp
2 participants