Users Guide

Table Of Contents
Following table describes the metric reports that can be generated using telemetry:
Type Metric Group Inventory Sensor Statistics Configuration Metrics
I/O Devices NICs No Yes Yes No No
FC HBAs No Yes Yes No No
Server Devices CPUs No Yes No No Yes
Memory No Yes No No Yes
Fans No Yes No No No
PSUs No No No No Yes
Sensors No Yes No No No
Environmental Thermal No Yes No No Yes
Power No No Yes No Yes
Performance No No Yes No No
Accelerators GPUs No No Yes No Yes
To know about the field descriptions of Telemetry section, see iDRAC Online Help.
NOTE:
StorageDiskSMARTDATA is only supported on SSD drives with SAS/SATA bus protocol and behind the BOSS controller.
StorageSensor data is reported only for the drives in Ready / Online / Non-RAID mode and not behind the BOSS
controller.
NVMeSMARTData is only supported for SSD (PCIeSSD / NVMe Express) drives with PCIe bus protocol (not behind
SWRAID).
GPGPUStatistics data is only available in specific GPGPU models that support ECC memory capability.
PSUMetrics is not available on modular platforms.
Fan Power and PCIe Power Metrics may be displayed as 0 for some platforms.
CUPS report has been renamed to SystemUsage in 4.40.00.00 release and it's supported on both INTEL and AMD
platforms.
Telemetry Workflow:
1. Install Datacenter license, if not installed already.
2. Configure global Telemetry settings including Enabling the telemetry and Rsyslog server network address and port using
RACADM, Redfish, SCP, or iDRAC GUI.
3. Configure the following Telemetry report streaming parameters on the required device report or log using either RACADM or
Redfish interface:
EnableTelemetry
ReportInterval
ReportTriggers
NOTE: Enable iDRAC Alerts and Redfish events for the specific hardware for which you need telemetry reports.
4. Redfish client makes subscription request to the Redfish EventService on iDRAC.
5. iDRAC generates and pushes the metric report or log/event data to the subscribed client when the predefined trigger
conditions are met.
Feature Constraints:
1. For security reasons, iDRAC supports only HTTPS-based communication to the client.
2. For stability reasons, iDRAC supports up to eight subscriptions.
3. Deletion of subscriptions is supported through Redfish interface only, even for the manual deletion by the Admin.
Behavior of Telemetry feature:
iDRAC generates and pushes (HTTP POST) the Metric Report or log/event data to all the subscribed clients to the
destination specified in the subscription when the predefined trigger conditions are met. The clients receive new data only
upon successful subscription creation.
The metric data includes the timestamp in ISO format, UTC time (ends in 'Z'), at the time of data collection from source.
224
Inventario, supervisión y configuración de dispositivos de red