# Dashboard

## Chapter 5:Using the Dashboard

Your central hub for at-a-glance monitoring and a launchpad for investigating issues.

> ℹ️ **Dashboard Access**
>
> * **Available to**: All user roles (Organization Admin, POD Admin, POD Viewer)
> * **Scope:** Organization, Hierarchy View, POD levels
> * **Permissions:** Monitor-only for all roles

***

## Overview: Your Daily Operations Cockpit

The **Dashboard** is your primary starting point for daily operations. Think of it as the main cockpit of your infrastructure, providing a high-level, real-time overview of your environment's health. Its purpose is to help you answer one question very quickly: "**Is everything okay**, **or does something need my immediate attention?**"

It's designed to be an interactive **launchpad**. The widgets not only show you information but also act as direct shortcuts, allowing you to jump from a high-level alert straight to the detailed page needed to investigate it.

{% hint style="warning" %}
**Critical Note: The Dashboard is a Snapshot**

The data on the Dashboard is a snapshot from when the page was loaded. It **does not auto-refresh**. To get the most up-to-the-minute status from the node BMCs, you must **perform a manual browser refresh (F5)**.
{% endhint %}

***

## Understanding Scope Impact on Dashboard

What You See Depends on Your Selected Scope:

* **Organization Level:** Displays aggregated data from all PODs you have access to
* **Hierarchy View Level**: Shows data only from PODs within that HV that you can access
* **POD Level:** Displays data specifically from the selected POD

{% hint style="warning" %}
**Permission Filtering**: The dashboard automatically filters content based on your role and authorized PODs. For example, if you have access to POD1 and POD3 but not POD2, selecting "Organization" will show combined data from POD1+3 only.
{% endhint %}

***

## Your 60-Second Daily Health Check

Workflow: Incorporate this simple routine into your daily operations for efficient infrastructure management.

```
1. Select Scope → 2. Check Health → 3. Investigate Issues → 4. Navigate to Details
```

### Step-by-Step Process:

1. **Select Your Scope:** Use the hamburger menu to choose the Organization, HV, or specific POD you want to check from the Management Tree.
2. **Check POD Health First:** The POD Health widget is your most critical indicator. Its color, status, and node count tell you if immediate action is required.
3. **Investigate Alerts:** If the status shows node counts with CRITICAL or WARNING, click the widget. This is your shortcut to jump directly to the Services page to see which specific nodes need attention.
4. **Review Resource Trends:** Quickly scan the resource distribution and historical trends for any anomalies.

{% hint style="info" %}
**Remember to Refresh:** Hit **F5** to ensure you're seeing the latest BMC data
{% endhint %}

***

## Understanding Rack Management

The Rack count in your Dashboard requires manual setup:

1. **Initial State**: New PODs show "0" racks even if physical racks exist in your data center
2. **Creating Logical Racks**: Navigate to **`MANAGE → POD`** View to create and define racks
3. **Assigning Nodes:** Drag nodes into rack positions in POD View
4. **Dashboard Update**: Once nodes are placed in racks, the Dashboard will reflect your logical rack count

{% hint style="warning" %}
**Remember:** Rack management in EDCC is a planning and documentation tool. It doesn't automatically detect physical rack arrangements.
{% endhint %}

***

## Interpreting the Dashboard Widgets

Overview: Each widget on the Dashboard provides a specific piece of information and often serves as a direct link to a more detailed page.

<figure><img src="https://content.gitbook.com/content/iGPGTG6LFrVfBRB76ZPF/blobs/WgFIDFrfplTZimdk8Jkl/image.png" alt=""><figcaption></figcaption></figure>

### Primary Monitoring Widgets

<table><thead><tr><th width="151.84765625">Widget</th><th width="246.85546875">What It Tells Me</th><th width="218.32421875">Interactive Action</th><th>Priority</th></tr></thead><tbody><tr><td>POD Health</td><td>An immediate, color-coded health summary showing the number of nodes with unresolved Critical or Warning events from their BMC SELs.</td><td>Clicking the status takes you directly to the Services page, pre-filtered to show the specific nodes reporting issues.</td><td>🔴 HIGHEST</td></tr><tr><td>Racks &#x26; Nodes</td><td><p>A quick inventory count showing:</p><p>• <strong>Nodes:</strong> Total nodes in this POD with Online vs. Offline breakdown</p><p>• <strong>Racks:</strong> Number of logical racks created in POD View (only counted when nodes are assigned to racks)</p></td><td>Clicking the Nodes count navigates directly to the Node List for detailed view.</td><td>🟡 HIGH</td></tr></tbody></table>

{% hint style="success" %}
**Note on Rack Count**: The Rack number only appears after you've organized nodes into racks using `MANAGE → POD View`. This is a logical organization feature, not automatic physical detection.
{% endhint %}

### Capacity Planning Widgets

<table><thead><tr><th width="118.49609375">Widget</th><th width="312.03515625">What It Tells Me</th><th width="176.61328125">Interactive Action</th><th>Purpose</th></tr></thead><tbody><tr><td>Resource Distribution</td><td>A visual breakdown of the total installed capacity of Memory and Storage across your nodes. This is for capacity planning, not real-time usage.</td><td>(No link) Read-only informational chart.</td><td>Planning Tool</td></tr></tbody></table>

### Historical & Audit Widgets

<table><thead><tr><th width="141.29296875">Widget</th><th width="284.4453125">What It Tells Me</th><th width="187.38671875">Interactive Action</th><th>Purpose</th></tr></thead><tbody><tr><td>Recent Activity Timeline</td><td>A log of the most recent administrative actions performed in EDCC, such as configuration changes or firmware updates.</td><td>(No link) Read-only audit log.</td><td>Audit Trail</td></tr><tr><td>Nodes Status History</td><td>A historical line graph tracking the number of online and offline nodes over time. Useful for identifying trends or pinpointing outage timing.</td><td>(No link) Read-only historical chart.</td><td>Trend Analysis</td></tr></tbody></table>

<figure><img src="https://content.gitbook.com/content/iGPGTG6LFrVfBRB76ZPF/blobs/QdPVeDzmQjLkyY63z54c/image.png" alt=""><figcaption><p>The lower section of the dashboard, focusing on the Recent Activity Timeline and the Nodes Status history graph</p></figcaption></figure>

***

## Dashboard Status Indicators

### POD Health Status Meanings

<table><thead><tr><th width="117.6640625">Status</th><th width="106.37109375">Color</th><th width="199.46484375">Meaning</th><th>What the Number Shows</th></tr></thead><tbody><tr><td>GOOD</td><td>🟢 Green</td><td>No nodes have critical or warning events</td><td>No number displayed</td></tr><tr><td>WARNING</td><td>🟡 Yellow</td><td>One or more nodes have warning-level events</td><td>Number of nodes with warnings (e.g., "2 WARNING" = 2 nodes have warnings)</td></tr><tr><td>CRITICAL</td><td>🔴 Red</td><td>One or more nodes have critical events</td><td>Number of nodes with critical issues (e.g., "3 CRITICAL" = 3 nodes need attention)</td></tr></tbody></table>

{% hint style="warning" %}
**Important:** The number shown represents affected nodes, not event count. For example, "3 CRITICAL" means 3 servers have critical issues, regardless of how many events each server has. Click the widget to see which specific nodes need attention.
{% endhint %}

### Understanding Node Counts vs. Event Counts

#### **What you'll see:**

* **Dashboard POD Health:** Shows node count (e.g., "3 CRITICAL")
* **Services Page:** Shows the actual nodes that are in critical state
* **BMC SEL:** Shows the detailed events causing the critical status

#### **Example Scenario:**

* Dashboard shows: "2 CRITICAL"
* This means: 2 nodes in your POD have critical issues
* Services page will show: Those 2 specific nodes with their issues
* Each node might have multiple critical events in its BMC SEL

***

## Troubleshooting Dashboard Issues

### Common Dashboard Problems

:interrobang: **Problem:** "I don't see any rack count"

* **Cause:** Nodes haven't been organized into racks in POD View
* **Solution:** Navigate to MANAGE → POD View and organize your nodes into logical racks

:interrobang: **Problem:** "I don't see all my servers"

* **Cause:** Scope filtering or permission limitations
* **Solution:** Check your selected scope in the header and verify your POD access permissions

:interrobang: **Problem:** "Dashboard shows outdated information"

* **Cause:** Dashboard doesn't auto-refresh
* **Solution:** Press F5 to manually refresh and get latest BMC data

:interrobang: **Problem:** "Resource numbers seem wrong"

* **Cause:** Resource charts show installed capacity, not current usage
* **Solution:** This is expected behavior - these are planning tools, not utilization monitors

:interrobang: **Problem:** "POD Health shows a number but I'm not sure what it means"

* **Cause:** Misunderstanding of node count vs. event count
* **Solution:** The number represents how many nodes have issues, not how many issues exist. Click through to Services page for details

***

## Dashboard Quick Reference

### Widget Priority Guide

1. **First Check:** POD Health (any critical/warning node counts?)
2. **Second Check:** Nodes status (any offline nodes?)
3. **Third Check:** Recent Activity (any recent changes that might affect operations?)
4. **Fourth Check:** Historical trends (any patterns emerging?)

### Navigation Shortcuts from Dashboard

<table><thead><tr><th width="214.77734375">From Dashboard Widget</th><th width="229.8671875">From Dashboard Widget</th><th>Takes You To</th></tr></thead><tbody><tr><td>POD Health with issues</td><td>Click the status</td><td>Services page (filtered to problem nodes)</td></tr><tr><td>Nodes count</td><td>Click the number</td><td>Node List (all nodes in POD)</td></tr><tr><td>Offline node indicator</td><td>Click through to Node List</td><td>Node List (can filter by status)</td></tr></tbody></table>

***

## Chapter Summary & Key Takeaways

Essential Dashboard Concepts:

* **It's a Launchpad:** Use widgets as shortcuts to jump directly to problem areas
* **Node Counts, Not Events:** POD Health shows how many nodes have issues, not how many issues exist
* **Rack Organization is Manual:** Rack counts require organizing nodes in POD View first
* **Health is Driven by SEL:** The POD Health status is determined by unresolved events in the BMC SEL. To clear a critical alert, you must resolve the corresponding hardware events
* **Refresh is Required:** The data is a snapshot. Always manually refresh (F5) your browser to get the latest status
* **Capacity, Not Usage:** The resource charts show total installed hardware capacity, not real-time utilization
* **Scope Matters:** What you see depends on your selected management scope and permissions

**What's Next:** Chapter 6 will dive deeper into the Node List, where you'll learn to manage individual servers and perform bulk operations across your infrastructure.

> 💡 **Pro Tip:** Bookmark the Dashboard as your EDCC starting point and develop a habit of checking POD Health first thing each morning. Remember that the numbers show affected nodes - if you see "3 CRITICAL", you know exactly 3 servers need your attention!

<br>