Prometheus

4.6/5

“Flexible and future-proof but requires DevOps commitment”

For our fast-growing architecture (microservices, Kubernetes, cloud + on-prem mix), Prometheus felt like a future-proof choice. It gives flexibility and visibility. But I know it needs regular upkeep by our DevOps team, it’s not a “set and forget” solution.

Pros : Prometheus remains one of the most flexible monitoring systems good for containers, microservices, hybrid cloud, on-prem + cloud and adapts to evolving needs.

Cons : Because of its flexibility and self-hosting, it needs dedicated DevOps effort, configuration, maintenance, scaling and upgrades are not trivial.

Switched from : Splunk APM

Reason to switch : : I switched because managed services were expensive and sometimes limited; Prometheus gave more control and matched our DevOps culture, even though it needs more hands-on care.

4.5/5

“Custom alerting rules + integrations help with dev-ops automation”

I configured alerts for high error rates, CPU usage, database latency and hooked them into Slack. Now I get notified automatically instead of manually checking dashboards. It makes keeping up with system health much easier.

Pros : Prometheus alerts integrate with tools (PagerDuty, Slack, email, webhook) many users say this helps automate incident response and on-call workflows.

Cons : Alert fatigue is a risk if rules/thresholds are not well tuned, many false positives can annoy teams.

Switched from : Scout Monitoring

Reason to switch : I switched because manual checks were inconsistent; Prometheus’ alerting helped automate monitoring and reduced missed issues.

4.3/5

“Lightweight and reliable, good for startups too”

: For our small startup, Prometheus was an easy deploy just a container, configure exporters and we had monitoring without heavy overhead. For new teams or small projects, that was ideal.

Pros : Prometheus is relatively lightweight, doesn’t require heavy infrastructure (for small-to-medium scale), and can run even on modest servers or containers.

Cons : As data volume grows (long metric retention, many services), you may need remote-storage or sharding, adding complexity.

Switched from : Veeam One

Reason to switch : I switched because enterprise stacks felt overkill for our size; Prometheus matched our scale and budget better.