Nagios vs. Prometheus vs. StatsD

Each piece of our infrastructure is monitored using Nagios, alerting us immediately if anything goes wrong (hopefully before anyone else notices), and with a level of granularity that really helps in resolving things quickly when things are on fire.

We use Nagios to monitor customer instances of Bridge and proactively alert us about issues like queue sizes, downed services, errors in logs, etc.

Internal IT monitoring.

System, apps, monitoring.

Monitor web servers, databases, utility servers

We use nagios based OpsView to monitor our server farm and keep everything running smoothly.

For the monitoring full stack of the platform.

For system up times

Monitors everything!

We use Nagios to monitor our stack and alert us when problems arise. Nagios allows us to monitor every aspect of each of our servers such as running processes, CPU usage, disk usage, and more. This means that as soon as problems arise, we can detect them and call out an engineer to resolve the issues as soon as possible.

Gather metrics from systems and applications. Evaluate alerting rules. Alerts are pushed to OpsGenie and Slack.

We primarily use Prometheus to gather metrics and statistics to display them in Grafana. Aside from that we poll Prometheus for our orchestration-solution "JCOverseer" to determine, which host is least occupied at the moment.

We primarily use Prometheus to gather metrics and statistics to display them in Grafana.

Business and system counters go through StatsD and are pushed to InfluxDB

Arm yourself with sensor all over your application

StatsD is used to track the number of messages we're publishing and the type of realtime subscribers. So it shows the number of longpoll connections, the number of websocket connections etc. It also tracks how Redis is performing.