Azure AI inference events timestamp in AzMon workaround #38955
Conversation
This file contains 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
github-actions
bot
added
the
AI Model Inference
|
API change check API changes are not detected in this pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
GenAI messages content logs, when exported to Azure Monitor, end up there with the same timestamp (open-telemetry/semantic-conventions#1621 (comment)).
It happens for two reasons:
time.time_ns()precision on windows is low - ~1ms on my machine - this is fixable in OTel - Implement higher precision clock than time_ns open-telemetry/opentelemetry-python#4367This PR adds a workaround by using distinct timestamps for events. It's temporary - we'll find a way to fix it in open-telemetry/semantic-conventions#1701