-
Notifications
You must be signed in to change notification settings - Fork 95
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
Troubleshoot logs collector requires a label value #1518
Comments
We need to verify this, and at the very least improve the docs at https://troubleshoot.sh/docs/collect/logs/#example-collector-definition which aren't clear and consistent for the examples. |
From a Slack conversation with Ryan: in Kubernetes you can query labels with a key=value pair or by the existence of a label (ie: a label with an arbitrary value). I want to be able to select for pods that have a particular label name, with any value.
I'd like to get this use case written into the collector, plus improve the docs. |
Let's also figure out if logs from this collector are available via sbctl, if not then we should raise a bug over at https://github.com/replicatedhq/sbctl/issues |
Hi @bagel-dawg, I can't reproduce the issue. Please refer to this record: https://asciinema.org/a/jR3xbmgGTnbTLpkw2DsXTajnQ troubleshoot/pkg/collect/logs.go Lines 124 to 130 in af4cc8a
|
since we can't reproduce, I'll close this one. |
Bug Description
The following support bundle spec returns no logs for a variety of pods that each have an
app
label with different values.Expected Behavior
The support bundle generated should include any pod that has the label
app
.Steps To Reproduce
Create a support bundle with the above spec and run the following command against a cluster with pods with an
app
label with any value:Additional Context
Additionally,
sbctl
should be able to interact with these logs in the same way that they can with the current implementation. I often use sbctl in CICD as a debugging tool and it can be painful to keep up with multiple services.The text was updated successfully, but these errors were encountered: