2 publicaciones etiquetados con "pmm"

Setting up database monitoring from scratch is one of those tasks that feels like it should take an afternoon but ends up consuming a week.

You need Prometheus. Then an exporter for your specific database. Then Grafana (or another dashboard). Then Alertmanager. Then you need to write the alert rules, configure notification channels, test that the alerts actually fire, and figure out why they fire at 3am for things that aren't real emergencies.

And this is before you've handled certificate rotation for the exporter, dealt with the Prometheus scrape interval tuning, or figured out why your dashboard queries are returning No data.

With Filess Dedicated databases, all of this ships by default. Here's what you get and how it's built.

Your database is running. But is it really running well?

You check your application logs. Everything seems fine. Your users aren't complaining. But deep down, you know you're flying blind. You have no idea if:

• Your queries are getting slower over time
• Your connection pool is about to hit the limit
• Your disk I/O is becoming a bottleneck
• Your replication lag is growing

In the old days, you'd cobble together a monitoring solution: install Prometheus, configure Grafana, write custom exporters, set up alerting rules. Weeks of work, and you'd still miss critical metrics.

Filess.io solves this by providing Percona Monitoring and Management (PMM) out of the box on all Dedicated Runtime databases.