Menu

Post image 1
Post image 2
Post image 3
1 / 3
0

Whistleblower for Database: Set up an internal informant who exposes performance

DEV Community·MongoDB Guests·26 days ago
#LaIJnDtK
Reading 0:00
15s threshold

This tutorial was written by Darshan Jayarama . As DBAs, waking up at 2 AM because production is down or slow is a nightmare, and none of us like it. However, we all know that it is not instant karma; it is like a pressure cooker where the database has reached its breaking point. Database whistleblowers constantly give signals that we ignore before it explodes into a Production Issue . Whistleblower 1: Performance Informant High CPU utilization? CPU utilization is not just an alert, it is a future prediction with regard to the database. When you get constant High CPU utilization alerts, think of it as a Whistleblower reviewing the database logs, metrics, and processes that are consuming CPU. If possible, shift those processes to a different server and let your Database breathe without pressure. Ignoring high CPU utilization can lead to high latency. Query <5 seconds? A query that was blazing fast is now causing a slow query alert since the last data load.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More