docs: add logging section for control/data planes & DNS #2198
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
dascole
requested review from
johncowen and
lobkovilya
and removed request for
a team
✅ Deploy Preview for kuma ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
bartsmykla
requested changes
Mar 7, 2025
dascole
force-pushed
the
feat/add-troubleshooting-guide
branch
from
f620d8a to
883d9cf
Compare
* feat(tf): render tf tab Signed-off-by: slonka <[email protected]> * feat(tf): arrays sort of work Signed-off-by: slonka <[email protected]> * feat(tf): commas in arrays work Signed-off-by: slonka <[email protected]> * feat(tf): seems to render quite correctly now Signed-off-by: slonka <[email protected]> * feat(tf): top part looks good Signed-off-by: slonka <[email protected]> * feat(tf): render from uni style Signed-off-by: slonka <[email protected]> * feat(tf): render only when not kuma Signed-off-by: slonka <[email protected]> * feat(tf): update golden files Signed-off-by: slonka <[email protected]> * feat(tf): make all keys snake_case Signed-off-by: slonka <[email protected]> * feat(tf): use snake_case fn everywhere Signed-off-by: slonka <[email protected]> * feat(tf): no need to if else on tf tab Signed-off-by: slonka <[email protected]> * feat(tf): add a guard for 2.10.x onwards Signed-off-by: slonka <[email protected]> --------- Signed-off-by: slonka <[email protected]> Signed-off-by: dascole <[email protected]>
This commit adds a new section to the troubleshooting guide for logging. It includes information on how to enable debug logging for the control and data planes, as well as how to enable debug logging for DNS. This partially addresses issue kumahq#1302 by providing initial documentation for logging. Further work is needed to complete the full scope of the issue. Signed-off-by: dascole <[email protected]>
Resolve lint errors in troubleshooting.md Signed-off-by: dascole <[email protected]>
Address the linting issue from 'Adjusting Logging Levels for Kuma-DP' Signed-off-by: dascole <[email protected]>
Address 'Adjusting Logging Levels for Kuma-DP' Signed-off-by: dascole <[email protected]>
Signed-off-by: dascole <[email protected]>
dascole
force-pushed
the
feat/add-troubleshooting-guide
branch
from
76c24ec to
4b1d4cc
Compare
Signed-off-by: dascole <[email protected]>
|
Tabs have been adjusted to align with #2216 |
Signed-off-by: Lukasz Dziedziak <[email protected]>
Signed-off-by: dascole <[email protected]>
Signed-off-by: dascole <[email protected]>
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 commit adds a new section to the troubleshooting guide for logging. It includes information on how to enable debug logging for the control and data planes, as well as how to enable debug logging for DNS.
This partially addresses issue #1302 by providing initial documentation for logging. Further work is needed to complete the full scope of the issue.
Did you sign your commit? Instructions
Have you read Contributing guidelines?