3 ms·
This looks really good! Might give this a spin next week, currently using NR, but it’s slow, expensive and the in-cluster collection services are frustratingly
by FridgeSeal 4y ago
This looks really good!
Might give this a spin next week, currently using NR, but it’s slow, expensive and the in-cluster collection services are frustratingly fragile.
- pranay01 4y agothanks, if you have any questions while setting things up, feel free to drop by on our slack community - https://signoz.io/slack https://signoz.io/slack Also, can you explain a bit more on in-cluster collection services are frustratingly fragile do you mean the agent they use for sending application metrics from clusters breaks down?
- FridgeSeal 4y ago> do you mean the agent they use for sending application metrics from clusters breaks down? Yeah basically, a number of the kubernetes deployments are configured with too-low memory and resource limits, so they're constantly crashing (and triggering all sorts of alerting false-positives). The limits are semi-hardcoded, so we can't override them, and at the moment, the effort required to fix the deeply-interlinked helm chart they provide isn't worth it. The NRI-Bundle helm chart also installs a lot into your cluster - it brings its own NATS instance, there's multiple daemon sets, etc. I'd likely get quite a lot of spare compute back by swapping to something lighter.