Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Integrated Dell Remote Access Controller 9 User's Guide

PDF

Telemetry Streaming

Telemetry enables users to collect and stream real-time device metrics, events, and data logs from a PowerEdge server to a subscribed external client or server application. Using Telemetry, you can set the type and frequency of reports that needs to be generated.

NOTE:The feature is supported on all the platforms and it requires iDRAC Datacenter license.

Telemetry is one-to-many solution for collecting and streaming the live system data from one or more PowerEdge servers (iDRAC) to a centralized 'Remote Server Monitoring, Analysis, and Alerting service'. The feature also supports on-demand data collection of the data.

The telemetry data includes metrics/inventory and logs/events. The data can be streamed (pushed out) or collected (pulled) from iDRAC to or by remote consumers like Redfish client and Remote Syslog Server. The telemetry data is also provided to the iDRAC SupportAssist data collector on demand. The data collection and report is based on predefined Redfish telemetry metrics, trigger, and report definitions. The telemetry streaming settings can be configured using iDRAC web interface, RACADM, Redfish, and Server Configuration Profile (SCP).

To configure Telemetry, enable or select the required device reports or logs that define the behavior and frequency of data streaming. Go to Configuration > System Settings page to configure Telemetry. Data streaming is automatic until the Telemetry is disabled.

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:
  • When SAS/SATA Back Plane is connected to on-board SATA controller then it is expected that Back Plane may not show as Enclosure in system and may not be shown in hardware inventory as well.
  • 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.
  • Clients can terminate a subscription by sending an HTTP DELETE message to the URI of the subscription resource through the Redfish interface.
  • If the subscription is deleted either by iDRAC or the client, then iDRAC does not send (HTTP POST) reports. If the number of delivery errors exceeds predefined thresholds, then iDRAC may delete a subscription.
  • If a user has Admin privilege, they can delete the subscriptions but only through Redfish interface.
  • Client is notified about the termination of a subscription by iDRAC by sending 'Subscription terminated' event as the last message.
  • Subscriptions are persistent and can remain even after iDRAC restarts. But, they can be deleted either by performing racresetcfg or LCwipe operations.
  • User interfaces like RACADM, Redfish, SCP, and iDRAC display the current status of the client subscriptions.
  • TelemetryService readiness can be checked using a new attribute TelemetryServiceStatus added under GetRemoteServiceAPIStatus API call. This attribute is added to the existing list of LTStatus, RTStatus, ServerStatus and Status.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\