Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

helm, doc: Added debug Helm flag for the agent #2622

Merged
merged 1 commit into from
Jul 9, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/content/en/docs/reference/helm-chart.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

9 changes: 9 additions & 0 deletions docs/content/en/docs/troubleshooting/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,15 @@ level is controlled by the log-level option at startup:
* Enable debug level with `--log-level=debug`
* Enable trace level with `--log-level=trace`

### Change log level on Kubernetes

{{< warning >}}
The Tetragon DaemonSet will be restarted automatically after changing the debug Helm value!
Copy link
Member

Choose a reason for hiding this comment

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

This is a pedantic nit, I don't mind not changing this, just a suggestion:

Suggested change
The Tetragon DaemonSet will be restarted automatically after changing the debug Helm value!
The Pods of the Tetragon DaemonSet will be restarted automatically after changing the debug Helm value.

{{< /warning >}}

It is possible to change the log level of the Tetragon (DaemonSet) instances by
setting `tetragon.debug` to `true`.
Comment on lines +100 to +101
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
It is possible to change the log level of the Tetragon (DaemonSet) instances by
setting `tetragon.debug` to `true`.
It is possible to change the log level of Tetragon's DaemonSet Pods by
setting `tetragon.debug` to `true`.


### Change log level dynamically

It is possible to change the log level dynamically by sending the corresponding
Expand Down
1 change: 1 addition & 0 deletions install/kubernetes/tetragon/README.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ data:
btf: {{ .Values.tetragon.btf }}
{{- end }}
procfs: /procRoot
debug: {{ .Values.tetragon.debug | quote }}
enable-process-cred: {{ .Values.tetragon.enableProcessCred | quote }}
enable-process-ns: {{ .Values.tetragon.enableProcessNs | quote }}
process-cache-size: {{ .Values.tetragon.processCacheSize | quote }}
Expand Down
2 changes: 2 additions & 0 deletions install/kubernetes/tetragon/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,8 @@ tetragon:
# Tetragon puts processes in an LRU cache. The cache is used to find ancestors
# for subsequently exec'ed processes.
processCacheSize: 65536
# -- If you want to run Tetragon in debug mode change this value to true
debug: false
# JSON export filename. Set it to an empty string to disable JSON export altogether.
exportFilename: tetragon.log
# JSON export file permissions as a string. Set it to "600" to restrict access to owner.
Expand Down
Loading