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.
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
feat(ourlogs): Allow log ingestion behind a flag #4448
base: master
Are you sure you want to change the base?
feat(ourlogs): Allow log ingestion behind a flag #4448
Changes from 4 commits
5fb547f
97b7590
6dc83ef
3f6f6f9
817a9fd
87f4882
20e75e4
177d523
7cbe5c9
413338c
99b1d60
f92a726
568bde8
077d50e
240b92b
153c0bc
12127e1
7c2bd4d
bbe569d
1ab81d3
06b30de
5c01989
0748d2c
188f0ed
535022c
57f578f
484e540
b2c1613
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other data types accept both unix timestamps and formatted date strings, although they do not have nanosecond precision:
relay/relay-event-schema/src/protocol/span.rs
Lines 16 to 18 in 4622914
Are nanos required for logs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OTel defines them as nanos, the consumers will consume nanos, and they are stored as nanos, we may need breadcrumbs to switch from floats to nanos but otherwise I think we are leaning towards keeping it the same format throughout instead of having slightly different intermediate formats.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this actually the protocol we want (i.e. explicit types in the JSON key)? Wouldn't this be nicer?
Or is it vital to distinguish between integers and floating points?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm of the opinion we want to keep this as close to OTel compatible as possible so we don't have any subtle impedance mismatch bugs, unless there is a strong reason otherwise (I haven't considered this deeply though so I can be convinced otherwise).
For reference these follow AnyValue