Inspired by a related thread about vendor lock in.
Ask HN: What's your open source stack?
1–10 of 16 posts
Re: Ask HN: What's your open source stack?
#2This is still the goto OSS stack, and I wouldn’t really recommend looking into smaller projects (usually backed by a single vendor) that are claiming better performance/lower resource usage for the same capabilities, because that always comes with a cost.
Re: Ask HN: What's your open source stack?
#3Re: Ask HN: What's your open source stack?
#4Re: Ask HN: What's your open source stack?
#5Re: Ask HN: What's your open source stack?
#6logrotate, systemd, `journalctl -u server-name | grep whatever`
Re: Ask HN: What's your open source stack?
#7Metrics: Prometheus, Grafana and prometheus-client (Python library for Prometheus expoters).
Re: Ask HN: What's your open source stack?
#8Re: Ask HN: What's your open source stack?
#9They do integrate with Grafana much like Prometheus but we are not happy with Grafana[0] and recommendations for something low-maintenance we can drop in to the above stack instead would be awesome.
[0]: Why? Managing dashboards/plugins in an airgapped IaC setting is like pulling teeth at every other turn. Then at one point supposedly we had the container version pinned (by tag not sha, lesson learned) but yet at some point an image update from Docker Hub broke most of our dashboard/data-source links so now those dashboards are broken and I'd rather try something new before I recommit to Grafana.