Types of dashboard visualizations
This table shows the visualizations that you can add to your dashboards. For each visualization, the table shows:
- The series that the visualization contains.
- Which of the source's signals gives the information displayed by the visualization.
- Which premade dashboards contain the visualization.
- What filtering options are available for the visualization.
- Some visualizations can be filtered to show information for a single node a time. Try adding multiple copies of these aggregations to your dashboards, filtering each one to show information about a different HCP node. For example, this dashboard includes multiple HTTP Connections visualizations, one for each node in an 8-node HCP system:
- Some pie chart visualizations, such as Objects By Tenant, show data for the most-recent point in time. Others, such as Operations Breakdown, show cumulative data.
- The filtering options for some visualizations are determined by the data that HCM has collected. For example, if no DELETE requests have occurred on your HCP system, you cannot filter the Operations Breakdown visualization to show information about such requests.
- For visualizations with median series, the median values presented are approximations that are calculated using the t-Digest algorithm each time the visualization is loaded. As a result, median values might differ slightly each time you view a visualization.
| Visualization | Description | Series | Source | Premade dashboards |
| Back-end Network I/O | Shows data transfer rate over the HCP system's back-end network in bytes per second and the back-end limit. If you know the maximum bandwidth for the HCP system's back-end network, you can use this visualization to see if the HCP back-end traffic is approaching that limit. |
| HCP Node Status API | Resources |
| CPU I/O Wait | Shows the percentage of CPU capacity spent waiting to access logical volumes being used by other processes. A high CPU I/O wait percentage might indicate that disk I/O is a bottleneck on the system. | I/O Wait : Percentage of CPU capacity waiting to access in-use logical volumes. | HCP Node Status API | Resources |
|
CPU Utilization For HCP systems | Shows the percentage of total CPU capacity being used across all CPUs in all HCP nodes for which the visualization shows information. The CPU limit is also shown. Because this visualization shows sums of percentages, values displayed can exceed 100%. |
| HCP Node Status API | Resources |
|
CPU Utilization For HCP S systems | Shows the percentage of total CPU capacity being used across all CPUs in all HCP S nodes for which the visualization shows information. The CPU limit is also shown. Because this visualization shows sums of percentages, values displayed can exceed 100%. |
| MAPI | Resources |
| Disk I/O | Shows the number of blocks per second read and written across all logical volumes in all HCP nodes for which the visualization shows information. |
| HCP Node Status API | Resources |
| Disk Utilization | Shows the percentage of I/O capacity used by the logical volumes on all HCP nodes for which the visualization shows information. Because this visualization shows sums of percentages, values displayed can exceed 100%. |
| HCP Node Status API | Resources |
| Economy Storage | Shows storage usage for all HCP S Series nodes. |
| SNMP | Storage and Objects |
| Event Severity | Shows the number of events of different severity levels over time. | Includes a series for each event severity level, for example INFO or WARNING. | Syslog | None |
| Event Severity Breakdown | Shows the breakdown of event severities as a pie chart. This visualization shows the total numbers of each event severity type for the entire time period that the dashboard displays. | Includes a series for each event severity level, for example INFO or WARNING. | Syslog | None |
|
Front-end Network I/O For HCP systems |
Shows data transfer rate over the HCP system's front-end network in bytes per second and the front-end limit. If you know the maximum bandwidth for the HCP system's front-end network, you can use this visualization to see if the HCP front-end traffic is approaching that limit. |
| HCP Node Status API | Resources |
|
Front-end Network I/O For HCP S systems |
Shows data transfer rate over the HCP S system's front-end network in bytes per second and the front-end limit. If you know the maximum bandwidth for the HCP S system's front-end network, you can use this visualization to see if the HCP S front-end traffic is approaching that limit. |
| MAPI | Resources |
| HCP for Cloud Scale | Provides monitoring details of the performance, health, and storage metrics of an HCP for Cloud Scale system. |
| Prometheus API | None |
| HTTP Connections | Shows the number of HTTP connections, HTTPS connections, and HTTP+HTTPS connections for an HCP system or node. The limits for all three are also displayed. HCP allows a maximum of 255 active HTTP connections per node. Note: The HTTP(S) metric represents HTTP+HTTPS connections. | Connections: Shows the number of connections over time. | Node Status API | Resources, Application Load |
| Latency | Shows operation latency time, in seconds. Significant spikes or steady increases in latency might indicate a performance issue that needs to be investigated. |
| Syslog | Application Load |
| Memory Swap | Shows swap space usage rate, in pages per second. If your HCP system uses a large amount of swap memory, the system might be undersized. | Swap: The swap rate, in pages per second. | Node Status API | None |
| Objects | Shows the number of objects stored for an HCP system or systems. | Objects: Number of objects. | SNMP | Storage and Objects |
| Objects By Tenant | Shows the number of objects stored in each tenant, in a pie chart. | Includes a series for each tenant. | MAPI | Storage and Objects |
| Objects Processed (by Service) | Shows the number of objects that have been examined and processed by an HCP system. |
| MAPI Note: To view Objects Processed or Obects Processed Per Second, Gather HCP MAPI Metrics must be enabled on the signal source in the Monitor App. | Services |
| Objects Processed Per Second (by Service) | Shows the number of objects per second that are being examined and processed by an HCP system. |
| ||
| Operation Size | Shows the median, average, and total sizes for operations, in bytes. This visualization can be filtered to show information about all operations or only specific types of operations. |
| Syslog | Storage and Objects |
| Operations/Second | Shows the number of operations per second. This visualization can be filtered to show information about all operations or only specific types of operations. Note: When no operations or events have occurred over the displayed time period, No Data Available will appear for this visualization. This is not an error." | Operations/second: Number of operations per second for the current filter. | Syslog | Application Load |
| Operations Breakdown | Shows the number of occurrences of a specified operation property during the filtered time period. For example, you can configure this visualization to show the number of operations performed for each namespace, or the number of operations performed by each user. Note: When no operations or events have occurred over the displayed time period, No Data Available will appear for this visualization. This is not an error." | Includes a series for each distinct value configured for the Breakdown Element option. For example, if the visualization is configured to show a breakdown of response codes, the visualization includes a series for each unique response code. | Syslog | Application Breakdown |
| Operations/Second Breakdown Timeline | Shows the changes in number of occurrences of a specified operation property across operations over time. For example, you can configure this visualization to show the number of operations performed for each namespace, or the number of operations performed by each user. | Includes a series for each distinct value configured for the Breakdown Element option. For example, if the visualization is configured to show a breakdown of response codes, the visualization includes a series for each unique response code in the data. | Syslog | Application Breakdown |
|
Primary Storage For HCP systems | Shows storage usage for all nodes. |
| SNMP | Storage and Objects |
|
Primary Storage For HCP S systems | Shows storage usage for all nodes. |
| MAPI | Storage and Objects |
| Replication Bytes | Shows pending and replicated bytes for the HCP replication service. |
| MAPI | Replication |
| Replication Bytes Rate | Shows pending and replicated bytes per second for the HCP replication service. | Bytes Replicated: Displays the total number of bytes replicated. | ||
| Replication Objects | Shows pending/replicated objects and errors for the HCP replication service. |
| ||
| Replication Objects Rate | Shows operations and errors per second for the HCP replication service. |
| ||
| Replication Verification | Shows objects verified and replicated for the HCP replication verification service. |
| ||
| Storage By Node | Shows a breakdown of the number of bytes stored on each HCP node. When you filter a dashboard to show data for a historical period of time, this visualization shows information from the last data point in that time period. | SNMP | Storage and Objects | |
| Storage By Tenant | Shows a breakdown of the number of bytes stored on each HCP tenant. When you filter a dashboardto show data for a historical period of time, this visualization shows information from the last data point in that time period. | SNMP | Storage and Objects | |
| Text | Shows any text you specify. Use this to display comments or notes on your dashboard. | N/A | You specify the text to be displayed. | N/A |
| Throughput | Shows the data transmission rate in bytes per second for the type of network traffic that the visualization is currently showing. For example, you can filter this visualization to show throughput information for all GET requests to a specific HCP tenant on a specific node. |
| Syslog | Application Load |
HCP services
HCP services are responsible for optimizing the use of system resources and maintaining the integrity and availability of the stored data. Each of the services performs a specific function that contributes to the overall health and viability of the system.
The following HCP services are available for selection when utilizing the Objects Processed and Objects Processed Per Second visualizations for a dashboard in the Monitor App:
Capacity Balancing
The Capacity Balancing service ensures that the percent of HCP storage space used on the storage nodes in the system remains roughly equivalent across the nodes when new nodes are added.
Compression
The Compression service compresses object data so as to make more efficient use of HCP storage space. The space reclaimed by compression can be used to store additional objects.
Content Verification:
The Content Verification service ensures the integrity of each object by:
- Verifying that the object data, system metadata, and custom metadata still match the stored cryptographic hash values.
- Ensuring that certain secondary metadata other than the hash value matches the primary metadata for the object.
Disposition
The Disposition service automatically deletes expired objects. An object is expired if either of these is true:
- The object has a retention setting that’s a specific date and time, and that date and time is in the past.
- The object has a retention setting that’s a retention class, and the date and time calculated from the duration specified by the retention class is in the past. In this case, the Disposition service deletes the object only if the retention class has disposition enabled.
Duplicate Elimination
Duplicate elimination is the process of merging the data associated with two or more identical objects. For objects to be identical, their data content must match exactly. By eliminating duplicates, HCP increases the amount of space available for storing additional objects.
Erasure Coding
The Erasure Coding service is responsible for ensuring that objects that are or have ever been subject to erasure coding are in the correct state at any given time.
Fast Object Recovery
The Fast Object Recovery service verifies unavailable objects and, if it finds that an object is available, changes the object status from unavailable to available.
Garbage Collection
The Garbage Collection service ensures that HCP storage doesn’t fill up with data that’s no longer needed.
Geo-distributed Erasure Coding
The Geo-distributed Erasure Coding service is responsible for ensuring that objects that are or have ever been subject to erasure coding are in the correct state at any given time.
Migration
The Migration service migrates data off selected storage nodes in either an HCP RAIN or SAIN system or off selected storage arrays in an HCP SAIN system in preparation for retiring those devices. During a data migration, the service copies objects and, if applicable, the metadata query engine index from the selected devices to free storage on the remaining devices. Before you start a data migration, you need to ensure that those devices have enough unused capacity to hold the data to be migrated.
After copying an object, the service deletes it from the source device.
Migration Verification
The Migration Verification service is responsible for verifying whether the Migration service encountered any errors with objects that should have been replicated. If the Migration Verification service encounters such an object, the service tries to migrate the object.
Protection
The Protection service ensures the stability of the repository by maintaining a specified level of data redundancy, called the data protection level (DPL), for each object in the repository throughout the entire object lifecycle. The DPL for an object is the number of copies of the object data that HCP must maintain.
Replication
The Replication service starts sending information on a link the first time you add HCP tenants and default-namespace directories to that link, as long as the link schedule has the service running at that time. If the service is not scheduled to run at that time, the service starts sending information as soon as the next scheduled run period starts.
Replication Verification
The Replication Verification service is responsible for verifying whether the Replication service missed replicating or cannot replicate any objects that should have been replicated. If the Replication Verification service encounters such an object, the service tries to replicate the object.
Retirement
The Retirement service restores the chunk for the object to a full copy of the object data on HCP systems where the object is not supposed to be metadata-only. It also deletes the chunk for the object on HCP systems where the object should be metadata-only. The service does not delete the chunk for an object until a full copy of the object data exists either on at least two systems in the topology or on one system if the object should have data on only one system.
Scavenging
The Scavenging service ensures that objects in the repository have valid metadata. When the service runs, it verifies that both the primary metadata for each object and the secondary metadata is complete, valid, and in sync with each other.
Shredding
The Shredding service shreds deleted objects that are marked for shredding. If the object is a multipart object, the Shredding service shreds each part of the object. The Shredding service also shreds unused parts of multipart uploads that began in namespaces where the default shred setting is
True.Storage Tiering
The Storage Tiering service performs these functions according to rules specified in service plans:
- Moving copies of the objects in a given namespace among all of the storage tiers that are defined for that namespace by its service plan.
- Creating and deleting copies of objects in a given namespace on each storage tier that’s defined for that namespace to ensure that each tier always contains the correct number of copies of each object.
- Changing objects stored on primary running storage to be metadata-only or restoring data to metadata-only objects.
S Series Compression/Encryption Validation
The S Series Compression/Encryption service compresses object data so as to make more efficient use of HCP storage space. The space reclaimed by compression can be used to store additional objects.