This section describes the various components of the Databases dashboard. To learn how to customize the display of this dashboard and focus on a specific instance, refer to Selecting an Instance to Monitor.
The Instance home page is displayed by accessing the Databases dashboard.
The Databases dashboard includes the following sections:
Database cartridge type tiles - each tile represents a database type (SQL Server, SQL Server BI, Oracle, Sybase, DB2, MongoDB, Cassandra, or All Instances). Tiles display the number of instances for each database type, along with a breakdown according to the instance health (Normal, Warning, Critical, Fatal, or Unknown).
Status section - includes the following components:
The Status Indicators section can be used for filtering the Databases Group table to display only instances that meet a criterion set in this section. For more information, refer to Filtering the Display by Severity.
The Monitor button - Use this button to add instances to monitor. For more information, refer to Monitoring Data Replication.
The Configure Alarms button - Navigates you directly to the Administration > Alarms page. On the Alarms page you can view the alarms as well as configure the Alarm Template and alarm notification settings.
The Settings button - Use this button to do one of the following:
Currently selected database group table - a list of all monitored databases within the database group that is selected in the Databases section. For more information, refert to Currently Selected Database Group.
The Select dashboards () button - provides direct link to several drilldowns and panels, by that means saving the need to navigate to these locations through the Overview drilldown.
This section covers the following key areas:
The User Level Access screen allows you to assign specific instances to users or groups. When users view their Databases dashboard, they only see the instances assigned to them.
The Status Indicators section filters the Databases Group table to display only instances that meet a criterion set in this section. For more information, refer to Filtering the Display by Severity.
To assign instances to a specific user or group:
A Reset button is available in the Users table toolbar. This button allows you to reset user level access to the default behavior. All users will be assigned to view all instances.
Because the Databases dashboard displays by default all the currently monitored databases, customize the dashboard view to display only the relevant instances, and then preview such instances to decide which to monitor.
To select an instance to monitor:
Launching a full-screen view of the requested database by clicking the Home Page link can only be performed for instances monitored in Foglight for SQL Server mode.
The Databases table displays the group selected from the available database groups under the Databases section of the navigation pane. The Databases table contains the following columns:
As the currently selected group can contain instances of various types of databases monitored by Foglight, the table describes instances in general.
Name | Description |
---|---|
Database | |
Sev | The highest severity alarm of an instance, which determines its health state. |
Name | The name of the instance. |
Version | The version number of the instance. |
Up Since | The date and time when the instance was last restarted. |
Workload | Displays the workload chart for the instance. |
DB Alarms | The number of warnings, critical, and fatal alarms for the instance. Shows the most recent alarms invoked for the specific instance displayed in the row. The alarms are displayed by their severity levels, with the aggregated number for each severity. Click the severity icon of an alarm to display the Alarm pop-up, which provides in-depth information about the alarm, including its causes and implications |
System Utilization | |
Host | The name of the computer that hosts the instance. |
CPU Load (%) | The overall operating system CPU usage (including CPU usage by the database). |
Memory (%) | The percentage of memory consumed by all operating system processes (including the database) within the total memory. This value includes both RAM resident memory and swapped memory. |
Disk (% Busy) | The percentage of time the busiest device spent serving system-wide input and output requests. This metric serves as a measure for the system I/O load. |
Monitoring Status | |
Agent | The operational status of the monitoring agent. When the agent instance is running, hovering over the Stat icon displays the status message “Collecting Data”. When the agent instance is running but not collecting data, hovering over the State icon displays one of the following status messages: Starting Stopped Stopping Unknown |
OS | The state of OS-related data retrieval by the database cartridge, the Infrastructure cartridge, or both. |
The Status Indicators section can be used for filtering the Databases Group table to display only instances that meet a criterion set in this section.
To filter the display by severity:
While all existing and newly discovered instances are added to the “All” list, the Databases area of the navigation pane allows the creation, editing, and removal of sub-groups of database instances. By doing so, it serves as a filter that enables the display of only a specific, user-defined group of instances.
The Databases area includes the following components, which can be selected from a drop-down list:
All the Foglight for SQL Server sub-groups, which were created using the Database Groups section, are also displayed under Services. In addition, Services displays groupings of monitored resources that were created using the Service Builder dashboard, and contain Foglight for SQL Server database topology.
The Services section also contains the column SLC (Service Level Compliance), which indicates the current availability of the selected service over a given period.
To create a database group:
After adding one or more user-defined sub-groups, it is possible to add sub-groups to these sub-groups.
To remove a database sub-group:
To edit a database sub-group: