Skip to content

docs: add logging section for control/data planes & DNS#2198

Open
dascole wants to merge 21 commits into
kumahq:masterfrom
dascole:feat/add-troubleshooting-guide
Open

docs: add logging section for control/data planes & DNS#2198
dascole wants to merge 21 commits into
kumahq:masterfrom
dascole:feat/add-troubleshooting-guide

Conversation

@dascole

@dascole dascole commented Feb 25, 2025

Copy link
Copy Markdown
Contributor

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.

@dascole
dascole requested a review from a team as a code owner February 25, 2025 15:59
@dascole
dascole requested review from johncowen and lobkovilya and removed request for a team February 25, 2025 15:59
@netlify

netlify Bot commented Feb 25, 2025

Copy link
Copy Markdown

Deploy Preview for kuma ready!

Name Link
🔨 Latest commit 0cf0701
🔍 Latest deploy log https://app.netlify.com/sites/kuma/deploys/6806fe66de937600088ddac4
😎 Deploy Preview https://deploy-preview-2198--kuma.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 87 (🔴 down 10 from production)
Accessibility: 90 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

@bartsmykla bartsmykla left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tabs needs to be adjusted here after: #2216

@dascole
dascole force-pushed the feat/add-troubleshooting-guide branch from f620d8a to 883d9cf Compare March 12, 2025 16:05
slonka and others added 6 commits March 12, 2025 12:06
* feat(tf): render tf tab

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): arrays sort of work

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): commas in arrays work

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): seems to render quite correctly now

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): top part looks good

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): render from uni style

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): render only when not kuma

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): update golden files

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): make all keys snake_case

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): use snake_case fn everywhere

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): no need to if else on tf tab

Signed-off-by: slonka <slonka@users.noreply.github.com>

* feat(tf): add a guard for 2.10.x onwards

Signed-off-by: slonka <slonka@users.noreply.github.com>

---------

Signed-off-by: slonka <slonka@users.noreply.github.com>
Signed-off-by: dascole <joe.dascole@konghq.com>
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 <joe.dascole@konghq.com>
Resolve lint errors in troubleshooting.md

Signed-off-by: dascole <joe.dascole@konghq.com>
Address the linting issue from 'Adjusting Logging Levels for Kuma-DP'
Signed-off-by: dascole <joe.dascole@konghq.com>
Address 'Adjusting Logging Levels for Kuma-DP'

Signed-off-by: dascole <joe.dascole@konghq.com>
Signed-off-by: dascole <joe.dascole@konghq.com>
@dascole
dascole force-pushed the feat/add-troubleshooting-guide branch from 76c24ec to 4b1d4cc Compare March 12, 2025 16:06
Signed-off-by: dascole <72866937+dascole@users.noreply.github.com>
@dascole

dascole commented Mar 12, 2025

Copy link
Copy Markdown
Contributor Author

Tabs have been adjusted to align with #2216

@dascole
dascole requested a review from bartsmykla March 25, 2025 16:08
metadata:
annotations:
kuma.io/envoy-log-level: debug
kuma.io/envoy-component-log-level: dns:debug

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this line is not for "all components"

Suggested change
kuma.io/envoy-component-log-level: dns:debug

Comment thread app/_src/guides/logging.md Outdated
Co-authored-by: Jay Jijie Chen <1180092+jijiechen@users.noreply.github.com>
Signed-off-by: dascole <72866937+dascole@users.noreply.github.com>
{% endtab %}
{% tab Universal %}

In Universal mode, logging can be enabled by setting the environment variable `KUMA_RUNTIME_KUBERNETES_INJECTOR_BUILTIN_DNS_LOGGING`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Universal DPs use KUMA_DNS_ENABLE_LOGGING, insead of KUMA_RUNTIME_KUBERNETES_INJECTOR_BUILTIN_DNS_LOGGING

@jijiechen jijiechen left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution and I think we do need docs helping people diagnostic the mesh.


use_meshservice = @params["use_meshservice"] == "true" && Gem::Version.new(release.value.dup.sub "x", "0") >= TARGET_VERSION

show_tf = Gem::Version.new(release.value.dup.sub "x", "0") >= TARGET_VERSION

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change is not needed, right?

```yaml
containers:
- name: control-plane
image: "docker.io/kong/kuma-cp:2.9.3"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the image field is not correct for kuma. We may just remove it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same suggestion applys to other code snippets underneath.

group: true
items:
- text: Logging
url: /guides/logging

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's better to put it under "Using Kuma". WDYT @bartsmykla ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants