-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add extraArgs to debug dumps; use them to specify number of lines from Loki and which profiles to grab. #9888
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! My only comment is around making separate, typed args in the API
…ki; allow specifying which profiles to grab
95135e3
to
e0fb76c
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #9888 +/- ##
==========================================
- Coverage 58.07% 58.07% -0.01%
==========================================
Files 606 606
Lines 73534 73572 +38
==========================================
+ Hits 42708 42730 +22
- Misses 30264 30280 +16
Partials 562 562 ☔ View full report in Codecov by Sentry. |
…m Loki and which profiles to grab. (#9888) A template now looks like this: ```yaml $ pachctl debug template defaults: clusterDefaults: true inputRepos: true starlarkScripts: - builtin: starlark/basic.star timeout: 60s - builtin: starlark/list_rcs.star timeout: 60s system: database: true describes: - name: console - name: etcd - name: pachd - name: pachyderm-kube-event-tail - name: pachyderm-proxy - name: pg-bouncer helm: true logs: - name: console - name: etcd - name: pachd - name: pachyderm-kube-event-tail - name: pachyderm-proxy - name: pg-bouncer lokiLogs: - lokiArgs: maxLogs: "30000" name: console - lokiArgs: maxLogs: "30000" name: etcd - lokiArgs: maxLogs: "30000" name: pachd - lokiArgs: maxLogs: "30000" name: pachyderm-kube-event-tail - lokiArgs: maxLogs: "30000" name: pachyderm-proxy - lokiArgs: maxLogs: "30000" name: pg-bouncer profiles: - name: pachd profileArgs: profiles: - name: heap - name: goroutine version: true ``` This means you can now specify how many lines Loki should get you, and which profiles to run. You can do a CPU profile like: ```yaml system: profiles: - name: pachd profileArgs: profiles: - name: cpu duration: 30s ``` The `n` in `name` is low in alphabetical order so the generated template doesn't sort for optimal readability. This is unavoidable ;)
Use them to specify number of lines from Loki and which profiles to grab. (#9888) A template now looks like this: ```yaml $ pachctl debug template defaults: clusterDefaults: true inputRepos: true starlarkScripts: - builtin: starlark/basic.star timeout: 60s - builtin: starlark/list_rcs.star timeout: 60s system: database: true describes: - name: console - name: etcd - name: pachd - name: pachyderm-kube-event-tail - name: pachyderm-proxy - name: pg-bouncer helm: true logs: - name: console - name: etcd - name: pachd - name: pachyderm-kube-event-tail - name: pachyderm-proxy - name: pg-bouncer lokiLogs: - lokiArgs: maxLogs: "30000" name: console - lokiArgs: maxLogs: "30000" name: etcd - lokiArgs: maxLogs: "30000" name: pachd - lokiArgs: maxLogs: "30000" name: pachyderm-kube-event-tail - lokiArgs: maxLogs: "30000" name: pachyderm-proxy - lokiArgs: maxLogs: "30000" name: pg-bouncer profiles: - name: pachd profileArgs: profiles: - name: heap - name: goroutine version: true ``` This means you can now specify how many lines Loki should get you, and which profiles to run. You can do a CPU profile like: ```yaml system: profiles: - name: pachd profileArgs: profiles: - name: cpu duration: 30s ``` The `n` in `name` is low in alphabetical order so the generated template doesn't sort for optimal readability. This is unavoidable ;)
…m Loki and which profiles to grab. (#9888) A template now looks like this: ```yaml $ pachctl debug template defaults: clusterDefaults: true inputRepos: true starlarkScripts: - builtin: starlark/basic.star timeout: 60s - builtin: starlark/list_rcs.star timeout: 60s system: database: true describes: - name: console - name: etcd - name: pachd - name: pachyderm-kube-event-tail - name: pachyderm-proxy - name: pg-bouncer helm: true logs: - name: console - name: etcd - name: pachd - name: pachyderm-kube-event-tail - name: pachyderm-proxy - name: pg-bouncer lokiLogs: - lokiArgs: maxLogs: "30000" name: console - lokiArgs: maxLogs: "30000" name: etcd - lokiArgs: maxLogs: "30000" name: pachd - lokiArgs: maxLogs: "30000" name: pachyderm-kube-event-tail - lokiArgs: maxLogs: "30000" name: pachyderm-proxy - lokiArgs: maxLogs: "30000" name: pg-bouncer profiles: - name: pachd profileArgs: profiles: - name: heap - name: goroutine version: true ``` This means you can now specify how many lines Loki should get you, and which profiles to run. You can do a CPU profile like: ```yaml system: profiles: - name: pachd profileArgs: profiles: - name: cpu duration: 30s ``` The `n` in `name` is low in alphabetical order so the generated template doesn't sort for optimal readability. This is unavoidable ;)
A template now looks like this:
This means you can now specify how many lines Loki should get you, and which profiles to run. You can do a CPU profile like:
The
n
inname
is low in alphabetical order so the generated template doesn't sort for optimal readability. This is unavoidable ;)