Administrator Guide

Technical support and resources
7 Telemetry Streaming with iDRAC9 – Metric Reports Using Rsyslog | Document ID: 362
</SystemConfiguration>
2.1.2 Viewing Rsyslog related configurations
To view and verify that the settings applied using above commands, use RACADM ‘get’ command.
racadm>>get idrac.telemetry
[Key=idrac.Embedded.1#Telemetry.1]
EnableTelemetry=Enabled
RSyslogServer1=10.100.100.11
RSyslogServer1Port=514
RSyslogServer2=100.65.84.123
RSyslogServer2Port=514
2.2 Rsyslog server-side Configurations
Instructions for installation and configuration of Rsyslog server are not in the scope of this document. For
more information, see the documentation for the system operating system
The syslog protocol has a message size limitation for the efficient queuing and delivery of the messages.
Telemetry reports can be larger than 100 K based on the report interval configuration. Hence the
MaxMessageSize at server side must be raised to a value greater than or equal to 32 K.
Here is sample Rsyslog.conf file snippet from ‘Ubuntu-18.04’.
# provides TCP syslog reception
module(load="imtcp")
input(type="imtcp" port="514")
$MaxMessageSize 32k
$template remote-incoming-logs,"/var/log/%HOSTNAME%/%PROGRAMNAME%.log"
2.3 Testing Rsyslog configuration
# racadm –r 192.168.1.2 -u root -p calvin --nocertwarn testrsyslogconnection
TELEMETRY0100: A test message was sent to the configured rsyslog server(s).
To check, perform a manual verification of the message on the required server(s)
On the server, verify that the test message is received, here is a sample message.
number cat 100.65.99.127.log
2019-12-19T13:18:50.058962-06:00 192.168.1.1 idrac-SVCTAG: Testing Rsyslog
Connection...
If there are multiple rsyslog servers that are configured to receive the reports from iDRAC, all the servers are
expected to receive the message.