Home > Servers > Systems Management > White Papers > Server Configuration Profiles: Reference Guide > Custom Metric Report Definitions
Starting with the iDRAC9 4.40.00.00 release, SCP includes the ability to configure Telemetry’s custom Metric Report Definitions using the Include Custom Telemetry flag in SCP Export. This option is available with all interfaces. Here is a racadm example:
racadm get ‐t xml ‐f export.xml ‐u user ‐p password ‐l //ip/share/ ‐‐includeCustomTelemetry
or
racadm get ‐t json ‐f export.json ‐u user ‐p password ‐l //ip/share/ ‐‐includeCustomTelemetry
Note: The Include Custom Telemetry option can be combined with any other optional parameters.
This flag adds an XML or JSON element to the template that is outside of the legacy schema. As a result, the schema has been updated in iDRAC9 4.40.00.00 to accommodate this feature. Templates generated with this optional flag are not backwards compatible with older versions of iDRAC.
The custom Metric Report Definitions are at the end of the template under the CustomComponents element in XML templates:
<SystemConfiguration>
<Component FQDD="iDRAC.Embedded.1">
<Attribute Name="Telemetry.1#EnableTelemetry">Enabled</Attribute>
</Component>
<CustomComponents>
<CustomMetricReportDefinitions>
…
</CustomMetricReportDefinitions>
</CustomComponents>
</SystemConfiguration>
Likewise, the CustomComponents block is near the end of a JSON template.
],
"CustomComponents": { "CustomMetricReportDefinitions": [
{
"@odata.type": "#MetricReportDefinition.v1_3_0.MetricReportDefinition",
To import Telemetry custom Metric Report Definitions, the Datacenter license must be installed on the iDRAC and the Telemetry feature must be enabled. The Telemetry feature can be enabled and configured, and custom Metric Report Definitions can be applied in a single SCP Import operation.