--- title: "Read the monitoring dashboard" description: "Read the Event Monitoring dashboard's open problems by severity and period, filter them, open a resource's graphs, and go from a problem to its fix." content_type: "how-to" product: "monitoring" platform: "MyAccount" url: "/myaccount/monitoring/how-to/read-the-monitoring-dashboard/" topic: ["problems"] --- # Read the monitoring dashboard The **Monitoring Dashboard** shows what needs attention on your resources. Each row is a problem: one alert's condition, or one of E2E's built-in checks, holding true on one resource. That resource can be a node, load balancer, DBaaS instance, or Kubernetes node. Two alerts that are both true on the same resource make two rows. From a problem you can open the resource's graphs, and then fix the cause or change the alert. In the side menu, click **Event Monitoring** to open the dashboard. On your MyAccount dashboard, **View Monitoring Dashboard** in the **Node monitored** card's menu opens it too. The dashboard shows the problems of the project and region selected in MyAccount, Delhi or Chennai. ## Count the problems by severity **Problems by severity** at the top shows six counts: **Disaster**, **High**, **Average**, **Warning**, **Information**, and **Not classified**. To list only one severity, select its count. Each problem carries the severity of the alert that raised it. For what each level means, see [Alerts and problems](/myaccount/monitoring/concepts/alerts-and-problems/#severity). ## Choose the period The list shows the open problems that began within the period you pick, newest first. Choose **5 Minutes**, **15 Minutes**, **30 Minutes**, **1 Hour**, **6 Hours**, **12 Hours**, **1 Day**, **15 Days**, or **30 Days**. The dashboard opens on **30 Minutes**, so a problem that began earlier than that and is still open appears once you pick a longer period. To pick exact dates and times, choose **Custom**. A range picker opens, on a 24-hour clock, for any range within the last 30 days. Once you apply a range, the list shows the problems in it, and **Custom** stays selected with the range shown until you pick another period. To go back to **30 Minutes**, select the x beside the range. The dashboard loads when you open it or pick a period, and stays as it is after that. To see the latest problems, pick the period again. ## Read the problem list Each problem shows its **Time**, in India Standard Time, and the **Resource** it is on. **Problem - Severity Level** says what is wrong and how severe it is, and **Duration** says how long it has been open. With nothing open in the period, the list reads **No problems found.** Some problems come from E2E's own checks, which run on every running resource. They report that the resource is unreachable, that it has been restarted, or that its monitoring agent is not available. A paused alert's problem still appears here while its condition is true, since pausing stops only the alert's notifications. ## Filter the list 1. To narrow the list, open **Filters**. 2. Under **Severity**, choose the levels you want. 3. Under **Nodes** or **DBaaS**, choose the resources you want. Each section lists your running resources of that kind, with a search, and appears only when you have one. 4. Click **Apply**. To close the panel without filtering, click **Cancel**. The filters you applied show above the list. Remove one to widen the list again, or click **Clear all** to remove them all. ## Open a resource's graphs To open a resource's own page, select its name under **Resource**. The page is titled **Viewing Data of** followed by the name. The name opens the page when MyAccount can match the problem to one of your resources. The **Problems** tab lists that resource's problems, for the same periods as the dashboard. The **Metrics Data** tab shows graphs of **CPU Load**, **CPU Utilization**, **Disk Utilization**, **Disk Read Operations**, **Disk Write Operations**, **Memory Utilization**, and **Network Traffic**. Each network interface gets its own **Network Traffic** graph. Pick a period to choose the time the graphs cover. When the machine's monitoring agent is not reporting, **Metrics Data** shows a message in place of the graphs. To fix it on a node, see [Troubleshooting node monitoring and encryption](/myaccount/node/troubleshooting/monitoring-and-encryption/). To return to the problem list, click **Back to Dashboard**. ## Go from a problem to its fix The graphs show whether a problem is a short spike or a steady climb. Then: - If a disk is filling up or memory is running short, fix it on the machine itself: free some space, or give it more. On a node, [Upgrade a node's plan](/myaccount/node/how-to/upgrade-node-plan/) can give it more memory and a bigger disk. An E1 node keeps its disk size on a new plan; to grow it, see [Increase a node's root storage](/myaccount/node/how-to/increase-root-storage/). To store new data on a separate disk, see [Attach a volume to a node](/myaccount/volumes/how-to/attach-a-volume/). - If the machine's monitoring agent is unreachable, or the graphs stay blank, work through [Troubleshooting node monitoring and encryption](/myaccount/node/troubleshooting/monitoring-and-encryption/). - If the alert fires too readily, change its threshold, or pause it for planned work; see [Edit, pause, or delete an alert](/myaccount/monitoring/how-to/edit-pause-or-delete-an-alert/). To change who it notifies, change who is in its groups; see [Manage alert groups](/myaccount/monitoring/how-to/manage-alert-groups/). The problem leaves the list once its condition clears. For help with anything else on the dashboard, see [Troubleshooting Event Monitoring](/myaccount/monitoring/troubleshooting/monitoring/).