Expose parca-agent logs as a slot in the snap

[michaeldmitry]

I propose that parca-agent snap should expose its logs using a content interface slot. This would allow other snaps to connect to the logs slot to access log files directly.

However, if I'm not mistaken, parca-agent doesn't redirect its std logs to a file.

[brancz]

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!

[michaeldmitry]

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.

[brancz]

It seems quite widespread to only log to stdout/stderr, is there no way for snaps to accommodate that?

[jnsgruk]

I think we could solve it with a wrapper in the snap if needed.

[jnsgruk]

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)

[PietroPasotti]

@jnsgruk for my own understanding, why can't we simply use tee in the rock's command definition to redirect to a logfile?

[jnsgruk]

You definitely can do that - I think I used kube-log-runner in an image where tee wasn't available (it was a bare base), and rather than pull in all of coreutils I just built that small go thingy

[PietroPasotti]

aha right, we have to check what the base is in our snap and determine what to pull in as dependency