New Telemetry features – metric descriptions and alert incidents

If you are running MongoDB in production, you should have a robust uptime and historical monitoring solution for every database deployment. Uptime monitoring ensures that your application runs smoothly by tracking database stability and alerts you to take action if necessary. Historical monitoring helps you analyze and compare database and operating system metrics over time so that you can make informed decisions when tuning and scaling your database.

Telemetry, our real-time and historical monitoring tool, provides a customizable dashboard and alerting system that allows you to track key MongoDB metrics, analyze specific points in time, and configure custom alert thresholds. We've now made Telemetry even easier to work with by adding metric descriptions for each graph along with a list of alert incidents.

Metric descriptions in UI

Telemetry CPU graph

You may have noticed the new "?" icon located on every Telemetry chart. If you click on the icon, you can view the descriptions for each metric. For example, the CPU metric descriptions are the following:

Telemetry metrics help text

We hope these descriptions help you better understand each metric and serve as a quick reference when you are reading the charts or configuring alerts.

Telemetry alert incidents

Telemetry also allows you to create custom alerts. For example, you may want to configure an alert whenever the CPU User metric exceeds 75%. You can visit our Telemetry documentation for more information on how to configure Telemetry alerts and set up different notification channels.

If you have multiple alerts configured and your database is under duress, it is likely that there are multiple alerts are triggered at once. To help you keep track of alert incidents we have now added a new tab in Telemetry called "Alert Incidents". You can toggle between "open" and "closed" status, where "open" events are active issues and the "closed" events are past events.

Questions or feedback?

For questions about Telemetry metrics or feedback on what you would like to see in Telemetry, please contact MongoLab support. We look forward to hearing from you!

Leave a Reply