split observability stack into two modes #2047
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.
Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes introduce enhancements and new features to the observability stack command options in a CLI tool, improving flexibility and coverage of observability tools for local development environments. Specifically, it adds a "full" mode to include additional services for more comprehensive monitoring and introduces a new dummy dashboard file for local testing.
What
book/src/framework/observability/observability_stack.md
framework/cmd/main.go
observabilitycommand to include flags for a "full" stack option, allowing users to choose between a standard and a more comprehensive set of observability tools.framework/observability.go
ObservabilityUpandObservabilityUpFullto handle the setup of the default and full observability stacks, respectively.framework/observability/compose/docker-compose.yaml
framework/observability/dashboards/dummy.json