{"id":20110799,"url":"https://github.com/dell/idrac-telemetry-reference-tools","last_synced_at":"2025-08-21T23:32:24.436Z","repository":{"id":37072461,"uuid":"332058090","full_name":"dell/iDRAC-Telemetry-Reference-Tools","owner":"dell","description":"Reference toolset for PowerEdge telemetry metric collection and integration with analytics and visualization solutions.","archived":false,"fork":false,"pushed_at":"2024-10-01T17:31:54.000Z","size":7934,"stargazers_count":30,"open_issues_count":9,"forks_count":20,"subscribers_count":8,"default_branch":"main","last_synced_at":"2024-12-07T03:41:26.601Z","etag":null,"topics":["analytics","idrac9","poweredge","telemetry","visualization"],"latest_commit_sha":null,"homepage":"https://github.com/dell/iDRAC-Telemetry-Reference-Tools","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/dell.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"docs/CONTRIBUTING.md","funding":null,"license":"LICENSE.md","code_of_conduct":"docs/CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2021-01-22T20:42:40.000Z","updated_at":"2024-11-07T18:26:01.000Z","dependencies_parsed_at":"2023-02-15T02:31:11.806Z","dependency_job_id":"f021f4cb-cc7e-4d9d-bddc-b7a99c3cb30a","html_url":"https://github.com/dell/iDRAC-Telemetry-Reference-Tools","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dell%2FiDRAC-Telemetry-Reference-Tools","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dell%2FiDRAC-Telemetry-Reference-Tools/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dell%2FiDRAC-Telemetry-Reference-Tools/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dell%2FiDRAC-Telemetry-Reference-Tools/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/dell","download_url":"https://codeload.github.com/dell/iDRAC-Telemetry-Reference-Tools/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":230542287,"owners_count":18242332,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["analytics","idrac9","poweredge","telemetry","visualization"],"created_at":"2024-11-13T18:13:42.331Z","updated_at":"2025-08-21T23:32:24.424Z","avatar_url":"https://github.com/dell.png","language":"Go","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Telemetry Reference Tools\n\n- [Telemetry Reference Tools](#telemetry-reference-tools)\n  - [Navigation](#navigation)\n  - [So, what is the point of this repo?](#so-what-is-the-point-of-this-repo)\n  - [What is Telemetry?](#what-is-telemetry)\n  - [What do I do with telemetry data?](#what-do-i-do-with-telemetry-data)\n  - [What is in this data pipeline?](#what-is-in-this-data-pipeline)\n  - [Architecture Details](#architecture-details)\n  - [Getting Started](#getting-started)\n    - [Make Sure iDRAC is up-to-date](#make-sure-idrac-is-up-to-date)\n    - [Licensing](#licensing)\n    - [Enabling Telemetry](#enabling-telemetry)\n    - [Hardware and System Requirements](#hardware-and-system-requirements)\n  - [What to do next?/Installation](#what-to-do-nextinstallation)\n  - [Post Installation](#post-installation)\n  - [Debugging](#debugging)\n  - [Default Ports Used by the Framework](#default-ports-used-by-the-framework)\n  - [FAQ](#faq)\n    - [What is the advantage of using HTTP SSE over other approaches?](#what-is-the-advantage-of-using-http-sse-over-other-approaches)\n      - [Why not syslog?](#why-not-syslog)\n    - [How much horsepower do I need to collect telemetry?](#how-much-horsepower-do-i-need-to-collect-telemetry)\n    - [What is the output format from telemetry?](#what-is-the-output-format-from-telemetry)\n    - [Do I need to worry about telemetry overwhelming the iDRAC link?](#do-i-need-to-worry-about-telemetry-overwhelming-the-idrac-link)\n    - [What does a telemetry report look like?](#what-does-a-telemetry-report-look-like)\n    - [Is telemetry vendor neutral?](#is-telemetry-vendor-neutral)\n    - [Are there demo licenses for iDRAC Datacenter](#are-there-demo-licenses-for-idrac-datacenter)\n    - [What license is required for telemetry?](#what-license-is-required-for-telemetry)\n  - [LICENSE](#license)\n  - [Contributing](#contributing)\n  - [Disclaimer](#disclaimer)\n  - [Support](#support)\n\n## Navigation\n\n- [Main README](README.md)\n- [Architecture](docs/ARCHITECTURE.md)\n- [Debugging](docs/DEBUGGING.md)\n- [Install](docs/INSTALL.md)\n\n## So, what is the point of this repo?\n\nWhile it's easy to collect telemetry metrics it is not easy to build a well-structured, best-practice following, \npipeline. We will not profess to be perfect and the totality of this code base is maintained by Dell employees in \ntheir spare time, but this repo is here to give people a head start in building that pipeline with a near one button\ndeploy mechanism to create a telemetry collection pipeline.\n\nWe tried hard to write these instructions such that things would be easy to follow. If you have feedback, especially \nif something was confusing, feel free to open an [issue](https://github.com/dell/iDRAC-Telemetry-Reference-Tools/issues)\n\n## What is Telemetry?\n\nTelemetry is a vendor-neutral part of the Redfish standard for providing telemetry data from a device. For more on the\nRedfish standard see DMTF's [white paper](https://www.dmtf.org/sites/default/files/standards/documents/DSP2051_1.0.0.pdf). \nYou can also see their [developer resources](https://redfish.dmtf.org/redfish/mockups/v1/1155). Many people first\nask, \"What is in telemetry?\"\n\nTelemetry is presented by what are called reports. There are currently 24 report types available with their Metrics. You can obtain a \nlist by browsing to your iDRAC at `https://\u003ciDRAC\u003e/redfish/v1/TelemetryService/MetricReports`.\n\nFollowing are the currently available metrics (MetricIDs) and the associated pre-canned reports. \nDetail of each metric (MetricDefinition), like description, type, units, and sensing interval etc., can be obtained using\nthe following command:\n\ncurl -s -k -u : -X GET https://redfish/v1/TelemetryService/MetricDefinitions/SystemMaxPowerConsumption\n\nOutput:\n\n{\n\n\"@odata.type\": \"#MetricDefinitio.v1_1_1.MetricDefinition\",\n\n\"@odata.context\": \"/redfish/v1/$metadata#MetricDefinition.MetricDefinition\",\n\n\"@odata.id\": \"/redfish/v1/TelemetryService/MetricDefinitions/SystemMaxPowerConsumption\",\n\n\"Id\": \"SystemMaxPowerConsumption\",\n\n\"Name\": \"System Max Power Consumption Metric Definition\",\n\n\"Description\": \"Peak system power consumption\",\n\n\"MetricType\": \"Numeric\",\n\n\"MetricDataType\": \"Decimal\",\n\n\"Units\": \"W\",\n\n\"Accuracy\": 1,\n\n\"SensingInterval\": \"PT60S\",\n\n}\n\nList of Metric Reports with Metrics:\n- StorageDiskSMARTData\n  \n      • CommandTimeout\n      • CRCErrorCount\n      • CurrentPendingSectorCount\n      • DriveTemperature\n      • ECCERate\n      • EraseFailCount\n      • ExceptionModeStatus\n      • MediaWriteCount\n      • PercentDriveLifeRemaining\n      • PowerCycleCount\n      • PowerOnHours\n      • ProgramFailCount\n      • ReadErrorRate\n      • ReallocatedBlockCount\n      • UncorrectableErrorCount\n      • UncorrectableLBACount\n      • UnusedReservedBlockCount\n      • UsedReservedBlockCount\n      • VolatileMemoryBackupSourceFailures \n- SerialLog\n- ThermalMetrics\n\n      • ComputePower\n      • ITUE\n      • PowerToCoolRatio\n      • PSUEfficiency\n      • SysAirFlowEfficiency\n      • SysAirflowPerFanPower\n      • SysAirflowPerSysInputPower\n      • SysAirflowUtilization\n      • SysNetAirflow\n      • SysRackTempDelta\n      • TotalPSUHeatDissipation\n- MemorySensor\n\n      • TemperatureReading\n- GPUMetrics\n\n      • BoardPowerSupplyStatus\n      • BoardTemperature\n      • GPUHealth\n      • GPUMemoryUsage\n      • GPUUsage\n      • GPUMemoryClockFrequency\n      • GPUClockFrequency\n      • GPUStatus\n      • MemoryTemperature\n      • PowerBrakeState\n      • PowerConsumption\n      • PowerSupplyStatus\n      • PrimaryTemperature\n      • SecondaryTemperature\n      • ThermalAlertState\n      • GPUArbitratedPowerLimit\n      • GPUEnforcedPowerLimit\n      • GPUPCIeLinkSpeed\n      • GPUPCIeLinkSpeedMax\n      • GPUPCIeRxThroughput\n      • GPUPCIeTxThroughput\n      • GPUPCIeCorrectableErrorCount\n      • GPUMemBandwidthUsage\n      • GPUClockEventReason\n      • GPUTotalSMUsageTime\n      • GPUSMActivity\n      • GPUSMOccupancy\n      • GPUTensorCoreUsage\n      • GPUHmmaUsage\n\n- MemoryMetrics\n  \n      • AddressParityError\n      • UncorrectableECCError\n      • CorrectableECCError\n      • DataLossDetected\n      • MemorySpareBlock\n      • PredictedMediaLifeLeftPercent\n      • TemperatureThresholdAlarm\n- ThermalSensor\n  \n      • TemperatureReading\n- CPURegisters\n- AggregationMetrics\n  \n      • SystemAvgInletTempHour\n      • SystemMaxInletTempHour\n      • SystemMaxPowerConsumption\n- GPUStatistics\n\n      • CumulativeDBECounterFB\n      • CumulativeDBECounterGR\n      • CumulativeSBECounterFB\n      • CumulativeSBECounterGR\n      • DBECounterFB\n      • DBECounterFBL2Cache\n      • DBECounterGRL1Cache\n      • DBECounterGRRF\n      • DBECounterGRTex\n      • DBERetiredPages\n      • SBECounterFB\n      • SBECounterFBL2Cache\n      • SBECounterGRL1Cache\n      • SBECounterGRRF\n      • SBECounterGRTex\n      • SBERetiredPages    \n- Sensor\n  \n      • AmpsReading\n      • CPUUsagePctReading\n      • IOUsagePctReading\n      • MemoryUsagePctReading\n      • RPMReading\n      • SystemUsagePctReading\n      • TemperatureReading\n      • VoltageReading\n      • WattsReading\n\n- NICSensor\n\n      • TemperatureReading\n- FanSensor\n\n      • RPMReading\n- PowerMetrics\n  \n      • SystemHeadRoomInstantaneous\n      • SystemInputPower\n      • SystemOutputPower\n      • SystemPowerConsumption\n      • TotalCPUPower\n      • CPUPower\n      • TotalFanPower\n      • TotalMemoryPower\n      • TotalPciePower\n      • TotalStoragePower\n      • TotalFPGAPower\n      • FPGAPower\n- NICStatistics\n\n      • DiscardedPkts\n      • FCCRCErrorCount\n      • FCOELinkFailures\n      • FCOEPktRxCount\n      • FCOEPktTxCount\n      • FCOERxPktDroppedCount\n      • LanFCSRxErrors\n      • LanUnicastPktRxCount\n      • LanUnicastPktTxCount\n      • LinkStatus\n      • OSDriverState\n      • PartitionLinkStatus\n      • PartitionOSDriverState\n      • RDMARxTotalBytes\n      • RDMARxTotalPackets\n      • RDMATotalProtectionErrors\n      • RDMATotalProtocolErrors\n      • RDMATxTotalBytes\n      • RDMATxTotalPackets\n      • RDMATxTotalReadReqPkts\n      • RDMATxTotalSendPkts\n      • RDMATxTotalWritePkts\n      • RxBroadcast\n      • RxBytes\n      • RxErrorPktAlignmentErrors\n      • RxErrorPktFCSErrors\n      • RxFalseCarrierDetection\n      • RxJabberPkt\n      • RxMutlicast\n      • RxPauseXOFFFrames\n      • RxPauseXONFrames\n      • RxRuntPkt\n      • RxUnicast\n      • TxBroadcast\n      • TxBytes\n      • TxErrorPktExcessiveCollision\n      • TxErrorPktLateCollision\n      • TxErrorPktMultipleCollision\n      • TxErrorPktSingleCollision\n      • TxMutlicast\n      • TxPauseXOFFFrames\n      • TxPauseXONFrames\n      • TxUnicast\n- StorageSensor\n\n      • TemperatureReading\n- CPUMemMetrics\n\n      • CPUC0ResidencyHigh\n      • CPUC0ResidencyLow\n      • CUPSIIOBandwidthDMI\n      • CUPSIIOBandwidthPort0\n      • CUPSIIOBandwidthPort1\n      • CUPSIIOBandwidthPort2\n      • CUPSIIOBandwidthPort3\n      • NonC0ResidencyHigh\n      • NonC0ResidencyLow\n      • AvgFrequencyAcrossCores\n      • CPUPkgEnergy\n      • DRAMPkgEnergy\n      • LimitingEvents\n      • EnergyTimestamp\n      • PkgPwr\n      • DRAMPwr\n      • PkgThermalStatus\n      • ThermalCrtlCircuitActivation\n      • DRAMThrottling\n      • TJMax\n      • CPUEpi\n      • CPUViolationCounter\n      • CPULimitingCounter\n      • DDRLimitingCounter\n      • TCtrl\n      • CPUAvgPbmRatioCounterLow\n      • AccCoreCyclesLow\n      • AccCoreCyclesHigh\n      • UncoreClocksLow\n      • UncoreClocksHigh\n- PowerStatistics\n\n      • LastDayAvgPower\n      • LastDayMaxPower\n      • LastDayMaxPowerTime\n      • LastDayMinPower\n      • LastDayMinPowerTime\n      • LastHourAvgPower\n      • LastHourMaxPower\n      • LastHourMaxPowerTime\n      • LastHourMinPower\n      • LastHourMinPowerTime\n      • LastMinuteAvgPower\n      • LastMinuteMaxPower\n      • LastMinuteMaxPowerTime\n      • LastMinuteMinPower\n      • LastMinuteMinPowerTime\n      • LastWeekAvgPower\n      • LastWeekMaxPower\n      • LastWeekMaxPowerTime\n      • LastWeekMinPower\n      • LastWeekMinPowerTime\n- FPGASensor\n\n      • TemperatureReading\n- CPUSensor\n\n      • TemperatureReading\n- PSUMetrics\n  \n      • PSURPMReading\n      • PSUTemperatureReading\n- FCPortStatistics\n  \n      • FCInvalidCRCs\n      • FCLinkFailures\n      • FCLossOfSignals\n      • FCRxKBCount\n      • FCRxSequences\n      • FCRxTotalFrames\n      • FCTxKBCount\n      • FCTxSequences\n      • FCTxTotalFrames\n      • FCStatOSDriverState\n      • PortSpeed\n      • PortStatus\n- NVMeSMARTData\n\n      • AvailableSpare\n      • AvailableSpareThreshold\n      • CompositeTemparature\n      • ControllerBusyTimeLower\n      • ControllerBusyTimeUpper\n      • CriticalWarning\n      • DataUnitsReadLower\n      • DataUnitsReadUpper\n      • DataUnitsWrittenLower\n      • DataUnitsWrittenUpper\n      • HostReadCommandsLower\n      • HostReadCommandsUpper\n      • HostWriteCommandsLower\n      • HostWriteCommandsUpper\n      • MediaDataIntegrityErrorsLower\n      • MediaDataIntegrityErrorsUpper\n      • NumOfErrorInfoLogEntriesLower\n      • NumOfErrorInfoLogEntriesUpper\n      • PercentageUsed\n      • PowerCyclesLower\n      • PowerCyclesUpper\n      • PowerOnHoursLower\n      • PowerOnHoursUpper\n      • UnsafeShutdownsLower\n      • UnsafeShutdownsUpper\n- FCSensor\n\n      • TemperatureReading\n- SFPTransceiver\n  \n      • SFPTemperature\n      • TemperatureStatus\n      • SFPVoltage\n      • VoltageStatus\n      • TxBiasCurrent\n      • TxBiasCurrentStatus\n      • TxOutputPower\n      • TxOutputPowerStatus\n      • RxInputPower\n      • RxInputPowerStatus\n- SystemUsage\n\n      • CPUUsage\n      • IOUsage\n      • MemoryUsage\n      • AggregateUsage\n- DPU Metrics (No pre-canned report for these metrics. Custom Metric Report should be created to get reports of these DPU metrics)\n  \n      • DPUTemperature\n      • DPUPowerConsumption\n\nIf you want to see what a report looks like check out this [sample report](scripts/GetSensorThresholds/reports.json) \nof the StorageDiskSMARTData report.\n\n## What do I do with telemetry data?\n\nThe question most people then have is, \"Well, what do I do with it?\" Generally, what most people want to do is grab \nthese JSON reports and push them into a time series database. This way they can monitor their systems over time for \nthings like tracking load, failure prediction, anomaly detection etc. For example, maybe you want to know what times \nof day your network is most active, telemetry can tell you that. Maybe you have a group of systems failing with a \nhigher frequency and you want to know why. Telemetry could tell you that everything is overheating because no one \ntold you the datacenter in question was 92 degrees. Not that we have seen anyone do that *cough*.\n\nHere is what the data might look like for you. This is what an R840 looked like during startup in Splunk analytics.\n\n![](images/2022-03-01-12-57-32.png)\n\n## What is in this data pipeline?\n\nCurrently, we support the following time series databases for the pipeline:\n\n- Elasticsearch\n- InfluxDB\n- Prometheus\n- Timescale\n- Splunk (you must bring your own Splunk instance)\n\nWith the exception of Splunk, the databases for the pipeline are self deploying. With Splunk you will have to deploy \nyour own instance of Splunk, but we detail how to do this in the instructions.\n\nAt its highest level the pipeline looks like this:\n\niDRAC telemetry -\u003e ActiveMQ -\u003e Time series database\n\n![Overview](images/overview.png)\n\nThere are several GoLang programs in between that provide the glue which connect all of these data pipelines. See \nthe [architecture](docs/ARCHITECTURE.md) for more details.\n\n## Architecture Details\n\nSee [ARCHITECTURE.md](docs/ARCHITECTURE.md)\n\n## Getting Started\n\n### Make Sure iDRAC is up-to-date\n\nYou must be running iDRAC 4.0 or higher for telemetry support.\n\n### Licensing\n\nThe first thing you will need is the \n[Datacenter License](https://www.dell.com/support/kbdoc/en-us/000176472/idrac-cmc-openmanage-enterprise-openmanage-integration-with-microsoft-windows-admin-center-openmanage-integration-with-servicenow-and-dpat-trial-licenses) \nfor iDRAC. If you do not know what license your iDRAC currently has you can check it by logging into the iDRAC and \nlooking here:\n\n![](images/2022-03-01-13-12-03.png)\n\nIf you just want to try things out you can get a trial license for your iDRACs \n[here](https://www.dell.com/support/kbdoc/en-us/000176472/idrac-cmc-openmanage-enterprise-openmanage-integration-with-microsoft-windows-admin-center-openmanage-integration-with-servicenow-and-dpat-trial-licenses). If you would like to deploy licenses to \nmany servers programmatically there is an example script of how to do that in \n[Python](https://github.com/dell/iDRAC-Redfish-Scripting/blob/master/Redfish%20Python/IdracLicenseManagementREDFISH.py) and\n [Powershell](https://github.com/dell/iDRAC-Redfish-Scripting/tree/master/Redfish%20PowerShell/Invoke-IdracLicenseManagementREDFISH). \n\n### Enabling Telemetry\n\nThe next thing you will need to do is enable telemetry on your servers. You can either do this through the GUI or \nthere is a [script available](https://github.com/dell/iDRAC-Telemetry-Scripting/blob/master/ConfigurationScripts/EnableOrDisableAllTelemetryReports.py)\nthat will do it programmatically. The syntax is \n`python3 ./ConfigurationScripts/EnableOrDisableAllTelemetryReports.py -ip YOUR_IDRAC_IP -u IDRAC_ADMIN -p IDRAC_PASSWORD -s Enabled` \nTo do it through the GUI log into the iDRAC and go to Configuration-\u003eSystem Settings-\u003eTelemetry Streaming and set \nTelemetry Data Stream enabled.\n\n![](images/2022-03-01-13-32-33.png)\n\n### Hardware and System Requirements\n\nWhatever server on which you decide to run telemetry reference tools will have to run the following applications:\n\n- A few lightweight GoLang programs\n- Docker\n- Apache ActiveMQ\n- Your time series database\n\nThe amount of resources you will need strongly depends on the number of servers from which you will create data. We \nare still in the initial phases of testing but here are some stats from a 5-minute capture of a live R840:\n\n| Total Packets               | 2933              |\n|-----------------------------|-------------------|\n| Average PPS                 | 9.8               |\n| Average Packet Size (Bytes) | 720               |\n| Total Bytes sent/recv       | 2112629 (~2.06MB) |\n| Average bytes/s             | 7056              |\n\nAs you can see from the above, the data load is very light. You could easily pull data from hundreds of servers with \none receiver depending on its resources. As we perform more load testing we will push results here.\n\nIf you would like to perform some simple testing on your own you can pull all reports via \n[HTTP SSE](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events) with the \ncommand:\n\n```bash\ncurl -kX GET -u root:PASSWORD \"https://YOUR_IDRAC_IP/redfish/v1/SSE?$filter=EventFormatType%20eq%20MetricReport\"\n```\n\n## What to do next?/Installation\n\nAfter you have gone through getting started. You can head over to our [installation instructions](docs/INSTALL.md).\n\n**NOTE:** You will need access to the internet for the initial build of the pipeline but can move it offline after \nit is built.\n\n## Post Installation\n\nAfter you have your setup running you will likely want to start customizing it to your liking. This is meant to be a \nreference architecture but it is unlikely it will do exactly what you want. You will likely want to develop your own \ndashboards, analytics setups, or tune parts of the pipeline.\n\n## Debugging\n\nIf you need to debug things, we have included a few tips and tricks we learned along the way in \n[DEBUGGING.md](docs/DEBUGGING.md).\n\n## Default Ports Used by the Framework\n\n- 3000 - Grafana\n- 8080 - configgui port (external). Internally it uses 8082\n- 8088 - Splunk HTTP Event Listener (if using Splunk)\n- 8000 - Splunk Management UI (if using Splunk)\n- 8161 - ActiveMQ Administrative Interface (default credentials are admin/admin)\n- 61613 - ActiveMQ messaging port. Redfish read will send to this port\n\n## FAQ\n\n### What is the advantage of using HTTP SSE over other approaches?\n\n[HTTP SSE](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events) consumes \nfar less bandwidth than the alternate methods of obtaining telemetry data. Long pulling/Hanging GET requires a GET to \n\"hang\" on all iDRACs, using POST subscriptions runs the risk of no one being available to listen to the events and \nconsumes more bandwidth, and syslog has a number of protocol-specific problems detailed below. \n\n#### Why not syslog?\n\nThe issue with the syslog protocol is that the protocol does not specify a max message size. This means that each \nsyslog server implementation chooses a max message size. Furthermore, the behavior when a message exceeds the \nmaximum message size is not defined. Many syslog servers simply truncate the message which is obviously not a \ndesirable behavior. If you decide you really want to try to use syslog (we don't recommend this approach) a member \nof our team has written \n[a script](https://github.com/dell/iDRAC-Telemetry-Scripting/blob/master/TelemetryReportProcessingScripts/TelemetryRsysLogProcessor.py)\nfor reassembling the messages.\n\n### How much horsepower do I need to collect telemetry?\nSee [Hardware and System Requirements](#hardware-and-system-requirements)\n\n### What is the output format from telemetry?\nJSON\n\n### Do I need to worry about telemetry overwhelming the iDRAC link?\nThere is no risk that even with all reports turned on telemetry can overwhelm iDRAC's 1Gb/s link. Each report takes \nonly KB/s. Even if you tune the reports to send very frequently you will not overwhelm the 1Gb/s link.\n\n### What does a telemetry report look like?\nSee [this example](scripts/GetSensorThresholds/reports.json) of what a telemetry report looks like.\n\n### Is telemetry vendor neutral?\nYes. Telemetry is part of DMTFs Redfish specification. While there are parts of the Redfish standard which are \nleft to vendor implementation Dell's telemetry implementation is compliant with the specification.\n\n### Are there demo licenses for iDRAC Datacenter\nYes. See [this website](https://www.dell.com/support/kbdoc/en-us/000176472/idrac-cmc-openmanage-enterprise-openmanage-integration-with-microsoft-windows-admin-center-openmanage-integration-with-servicenow-and-dpat-trial-licenses)\n\n### What license is required for telemetry?\niDRAC Datacenter\n\n## LICENSE\nThis project is licensed under Apache 2.0 License. See the [LICENSE](LICENSE.md) for more information.\n\n## Contributing\nWe welcome your contributions to this reference toolset. See [Contributing Guidelines](docs/CONTRIBUTING.md) for \nmore details. Please reference our [Code of Conduct](docs/CODE_OF_CONDUCT.md).\n\n## Disclaimer\nThe software applications included in this package are  considered \"BETA\". They are intended for testing use in \nnon-production  environments only. \n\nNo support is implied or offered. Dell Corporation assumes no  responsibility for results or performance of \"BETA\" \nfiles.  Dell does NOT warrant that the Software will meet your requirements, or that operation of the Software will \nbe uninterrupted or error free. The Software is provided to you \"AS IS\" without warranty of any kind. DELL DISCLAIMS \nALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS \nFOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. The entire risk as to the results and performance of the Software\nis assumed by you. No technical support provided with this Software. \n\nIN NO EVENT SHALL DELL OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT OR INDIRECT DAMAGES WHATSOEVER (INCLUDING, WITHOUT \nLIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER \nPECUNIARY LOSS) ARISING OUT OF USE OR INABILITY TO USE THE SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH \nDAMAGES. Some jurisdictions do not allow an exclusion or limitation of liability for consequential or incidental \ndamages, so the above limitation may not apply to you.\n\n\n## Support\n- To report an issue open one [here](https://github.com/dell/iDRAC-Telemetry-Reference-Tools/issues).\n- If any requirements have not been addressed, then create an issue [here](https://github.com/dell/iDRAC-Telemetry-Reference-Tools/issues).\n- To provide feedback to the development team, email **idractelemetryteam@dell.com**.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdell%2Fidrac-telemetry-reference-tools","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdell%2Fidrac-telemetry-reference-tools","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdell%2Fidrac-telemetry-reference-tools/lists"}