Remotely-controlled collector

[paweljw]

It's noisy, so here's the pertinent changes:

• images contain almost nothing besides an empty initial supervisord.conf and (for collector) the bootstrap script
• bootstrap.sh runs once, and if successful - updater takes over
• even vector healthcheck is remote
• host path /var/lib/better-stack is mounted between the containers
• directly controlling supervisord in the beyla container via a socket (exposed in volume)
• direct supervisor run replaced with scripts that can install the initial supervisord.conf if needed

[curusarn]

Thanks @paweljw!

💄: Could you nest the files for Dockerfile under e.g. collector/ directory for consistency with beyla/ and Dockerfile.beyla? Currently, there seems to be a lot of subtle differences in paths between the two images.

[curusarn]

Any changes needed to Kubernetes configs? E.g. https://github.com/BetterStackHQ/collector-helm-chart/blob/main/templates/daemonset.yaml#L146

[curusarn]

Left a comment, looks good 👍

[curusarn]

I would prefer to nest the socket under /var/lib/better-stack

[paweljw]

@curusarn

Could you nest the files for Dockerfile under e.g. collector/ directory

Yes, good shout! I will probably even move the Dockerfiles into their respective spots.

Any changes needed to Kubernetes configs?

Yes, coming tomorrow once I'm happy there aren't too many corner cases in the simple case of compose!

Are we intentionally loosing all tests?

Yes, from this repository, I will be reintroducing them in Telemetry soonish 🙏

I would prefer to nest the socket under /var/lib/better-stack

Reasonable! I'll make the adjustment.