[release/8.0] Flow dashboard logs through the app host's logger #3598
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.
Backport of #3523 to release/8.0
/cc @davidfowl
Customer Impact
If the dashboard fails to launch, there's no way to get the logs other than digging deeply into DCP guts to find logs for it. This is because we don't show the dashboard logs in the dashboard (amongst other things). This change allows users to turn on dashboard logging levels via configuration so we can get better diagnostics when failures occur in the wild.
Testing
Unit tests, manual tests, updated one sample to turn on the logging.
Risk
Low, the code is resilient to failures and will noop if dcp is unhealthy and we're unable to get the logs.
Regression?
No