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

lwc: add timestamp accessor #1542

Merged
merged 1 commit into from
Apr 19, 2023
Merged

lwc: add timestamp accessor #1542

merged 1 commit into from
Apr 19, 2023

Conversation

brharrington
Copy link
Contributor

When mapping to time series data points, we need to know the timestamp for an event. For events like spans that have a start and end, the end time is used. This is similar behvavior to a timer which would get updated at the end when the latency is known.

When mapping to time series data points, we need to know
the timestamp for an event. For events like spans that
have a start and end, the end time is used. This is similar
behvavior to a timer which would get updated at the end when
the latency is known.
@brharrington brharrington added this to the 1.8.0 milestone Apr 19, 2023
@brharrington brharrington merged commit eb0b86d into Netflix:main Apr 19, 2023
@brharrington brharrington deleted the lwc-ts branch April 19, 2023 00:51
manolama pushed a commit to manolama/atlas that referenced this pull request May 22, 2024
When mapping to time series data points, we need to know
the timestamp for an event. For events like spans that
have a start and end, the end time is used. This is similar
behvavior to a timer which would get updated at the end when
the latency is known.
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.

None yet

1 participant