-
Notifications
You must be signed in to change notification settings - Fork 6
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
Allow for millisecond in Datadog logs timestamp #152
Comments
Chatted offline, as of now Datadog backend doesn’t support nanosecond, but we can look into setting millisecond precision in logs. |
songy23
changed the title
Allow for nanoseconds in Datadog timestamp
Allow for millisecond in Datadog logs timestamp
Aug 10, 2023
ladenedge
added a commit
to ladenedge/opentelemetry-mapping-go
that referenced
this issue
Nov 20, 2023
ladenedge
added a commit
to ladenedge/opentelemetry-mapping-go
that referenced
this issue
Nov 23, 2023
ladenedge
added a commit
to ladenedge/opentelemetry-mapping-go
that referenced
this issue
Nov 28, 2023
ladenedge
added a commit
to ladenedge/opentelemetry-mapping-go
that referenced
this issue
Dec 5, 2023
liustanley
pushed a commit
that referenced
this issue
Dec 5, 2023
Fixed in #202. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the @timestamp additional property is set and sent to Datadog milli and nanoseconds are suppressed. Would it be possible to change the formatting of the field to:
lr.Timestamp().AsTime().Format(time.RFC3339Nano)
Instead of:
lr.Timestamp().AsTime().Format(time.RFC3339)
opentelemetry-mapping-go/pkg/otlp/logs/logs_translator.go
Line 159 in 1c4a596
The text was updated successfully, but these errors were encountered: