-
Notifications
You must be signed in to change notification settings - Fork 71
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
Expose parca-agent logs as a slot in the snap #3017
Comments
We're pretty clueless honestly about the snap. @jnsgruk has been maintaining it, so whatever you think we should add we're very happy with! |
Happy to contribute, but the issue is I think that parca agent doesn't offer to redirect its logs from the standard streams to a file or sth and that is something we'd probably need. |
It seems quite widespread to only log to stdout/stderr, is there no way for snaps to accommodate that? |
I think we could solve it with a wrapper in the snap if needed. |
You might also be able to use something like this: https://pkg.go.dev/k8s.io/component-base/logs/kube-log-runner#section-readme (Which I've used previously in a ROCK) |
I propose that
parca-agent
snap should expose its logs using a content interface slot. This would allow other snaps to connect to thelogs
slot to access log files directly.However, if I'm not mistaken,
parca-agent
doesn't redirect its std logs to a file.The text was updated successfully, but these errors were encountered: