Per invocation log docs #60
Merged
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.
TL;DR
Adds documentation for the new per-invocation logging feature, which allows users to view logs for a specific run of their application.
Why we made these changes
Currently, users can only view global application logs, which makes it difficult to debug issues tied to a single invocation. This change introduces documentation for a feature that provides isolated log streams for each invocation, simplifying the debugging process.
What changed?
apps/logs.mdxto document retrieving logs for a specific run using the-ior--invocationflag.Validation
Description generated by Mesa. Update settings