fix: Make it clear that we publicly just support timestamp
as the log timestamp
#19484
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.
Give us some context
When looking into a support ticket, I noticed that the Logs API docs were confusing about which fields we'd use as a timestamp. This PR attempts to clarify that.
Note that
log_timestamp
is only used in built-in parsing rules, and we intentionally don't use that attribute as the log time, maybe because originally we weren't confident that the parsing rules could parse timestamps correctly?