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.

Sign up for GitHub

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

Jump to bottom

[BUG] Azure.Monitor.OpenTelemetry.Exporter - TelemetryItem.Time format does not include milliseconds #20475

Closed
mangeg opened this issue Apr 16, 2021 · 1 comment · Fixed by #20476
Closed

[BUG] Azure.Monitor.OpenTelemetry.Exporter - TelemetryItem.Time format does not include milliseconds #20475

mangeg opened this issue Apr 16, 2021 · 1 comment · Fixed by #20476
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Exporter Monitor OpenTelemetry Exporter needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@mangeg
Copy link
Contributor

mangeg commented Apr 16, 2021

Describe the bug
TelemetryItem.Time is set in a format that does not keep the milliseconds. This results in events in ApplicationInsights appear to have happened simultaneously when they happen within the same second.

Expected behavior
The format should be including milliseconds and follow the https://en.wikipedia.org/wiki/ISO_8601#UTC format according the ApplicationInsights API description, ex. 2021-04-16 23:22:25.0660Z.

https://raw.githubusercontent.com/Azure/azure-rest-api-specs/0ae35fd0c27e0f06004d820e75a13c615b9c2e96/specification/applicationinsights/data-plane/Monitor.Exporters/preview/2020-09-15_Preview/swagger.json
This field must be formatted in UTC ISO 8601 format, with a trailing 'Z'

Actual behavior (include Exception or Stack Trace)
Time is set without milliseconds in a format not according to the API description, ex. 04/16/2021 23:22:25

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

  1. View TelemetryItem.Time property after it has been created by TelemetryPartA.GetTelemetryItem(Activity activity, Resource resource, string instrumentationKey)

Environment:

  • Name and version of the Library package used: Azure.Monitor.OpenTelemetry.Exporter-1.0.0-beta.2
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 16, 2021
@mangeg mangeg mentioned this issue Apr 16, 2021
Merged
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. Monitor - Exporter Monitor OpenTelemetry Exporter needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team. labels Apr 17, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 17, 2021
@jsquire
Copy link
Member

jsquire commented Apr 17, 2021

Thank you for your feedback. Tagging and routing to the team best able to assist.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Exporter Monitor OpenTelemetry Exporter needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

TelemetryItem.Time format to keep time precision
3 participants
@mangeg @jsquire and others