feat: spike console logs #17589
Closed
feat: spike console logs #17589
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
tomasfarias
force-pushed
the
feat/batch-exports-logs
branch
from
a9af4f3 to
1d683c4
Compare
tomasfarias
force-pushed
the
feat/batch-exports-logs
branch
from
1d683c4 to
1001043
Compare
|
closed in favour of #17739 |
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.
** This is absolutely not for merging but shows it would work... **
Asking the question could we ingest and use console logs using the proposed log entries table
Answering that question with hell yes
We're already looping over the console logs during ingestion so can gather them as log entries and produce them at the same time