Administrator Guide

Receiving telemetry reports
Document 418
• FanSensor report gets generated only for Monolithic servers. For modular servers, the report is empty
(with "[e-mail]": 0).
When a report is enabled but the device hardware is not present, no report is generated. For instance, if a
GPU card is not present in the system and the GPUMetrics report is pulled, the result would be an empty
report with "[e-mail]": 0.
For all metric reports, the users can set a ReportInterval of 0 apart from the defined boundary values. When
the ReportInterval is set to 0, the report can only be pulled and it cannot be streamed.
Troubleshooting and Tips
Problem
Possible Solutions
1. Cannot configure telemetry.
1. Check license. Need “Datacenter” license for most
reports.
2. “OpenManage Enterprise” license for basic
reports.
2. Redfish client cannot stream or pull
telemetry reports.
1. Check license.
2. Check if global Telemetry enabled.
3. Check per report Telemetry enabled.
4. Check User Guide for unsupported ports for
Subscription destination.
5. Check if host is powered off.
3. No reports are seen Rsyslog server.
1. Check if Rsyslog target set to true on the report
settings.
2. Check if Rsyslog connection is good.
3. Check if host is powered off.
4. No reports are streamed on Trigger.
1. Check Redfish eventing setting in IDRAC GUI.
2. Check LC log for the EEMI ID that belongs to
trigger.
3. Check User Guide for triggers to EEMI ID
mapping.
4. Check if host is powered off.
Best practices
1. A Server Configuration Profile (SCP) would be a better option to configure all the metric reports, setting
ReportInterval and enabling RSyslogTarget. Once an SCP file is created, the same file can be applied to multiple
servers that support Telemetry feature and Datacenter license.
2. Configure the “report interval” based on the system configuration and number of configured telemetry reports. On
a max config system, a high report interval can in-turn result in large telemetry reports since it includes every
relevant device metric. Also, a minimum report interval like 5 s can in-turn contribute to processing overheads
based on the number active configured reports.
a. For servers with max configurations (large number of hard drives and or memory cards) it is advisable to
NOT set the ReportInterval to maximum value.