galexrt / dellhw_exporter Goto Github PK

View Code? Open in Web Editor NEW

111.0 12.0 40.0 8.67 MB

Prometheus exporter for Dell Hardware components using Dell OMSA.

Home Page: https://dellhw-exporter.galexrt.moe

License: Apache License 2.0

Makefile 4.26% Go 92.48% Dockerfile 1.32% Shell 0.44% Smarty 1.49%

dell omsa dell-omsa hacktoberfest prometheus metrics monitoring exporter

dellhw_exporter's Introduction

dellhw_exporter

Prometheus exporter for Dell Hardware components using OMSA.

The exporter was originally made by PrFalken. Due to some issues in the code, I rewrote the whole exporter using the "node_exporter" pattern and therefore moved it from being a fork out, to a standalone repository.

Omreport parsing functions were borrowed from the Bosun project, thank you very much for that, they are the most tedious part of the job.

This exporter wraps the "omreport" command from Dell OMSA. If you can't run omreport on your system, the exporter won't export any metrics.

Compatibility

Tested Dell OMSA Compatibility

The dellhw_exporter has been tested with the following OMSA versions:

7.4
8.4
9.1

Kernel Compatibility

Please note that only kernel versions that are supported by DELL DSU / OMSA tools are working!

State 07.06.2019: Dell OMSA DSU_19.05.00 is not compatible with 5.x kernel it seems (e.g., Fedora uses that kernel).

Should you run into issues when using the Container image, please follow the Troubleshooting - No metrics being exported.

Collectors

For a list of the available collectors, see Collectors doc page.

Configuration

For flags and environment variables, see Configuration doc page.

Caching

Optional caching can be enabled to prevent performance issues caused by this exporter, see Caching doc page.

Running in Container

Container Image available from:

(Docker Hub is not receiving new images begining from release v1.10.0)

Pull the Container Image

Each Git tag is built and published as a release and container image.

Quay.io

docker pull quay.io/galexrt/dellhw_exporter

GHCR.IO

docker pull ghcr.io/galexrt/dellhw_exporter

Run the Container Image

NOTE The --privileged flag is required as the OMSA needs to access the host's devices and other components.

docker run -d --name dellhw_exporter --privileged -p 9137:9137 quay.io/galexrt/dellhw_exporter

Running without Docker / Podman

To run without Docker / Podman either download a release binary or build it (using make build command):

./dellhw_exporter
./dellhw_exporter --help
./dellhw_exporter YOUR_FLAGS

The DELL OMSA services must already be running for the exporter to be able to collect metrics!

E.g., run /opt/dell/srvadmin/sbin/srvadmin-services.sh start and / or systemctl start SERVICE_NAME (to enable autostart use systemctl enable SERVICE_NAME; where SERVICE_NAME are the DELL OMSA service(s) you installed).

Prometheus

The exporter runs on port 9137 TCP.

Example static Prometheus Job config:

[...]
  - job_name: 'dellhw_exporter'
    # Override the global default and scrape targets from this job every 60 seconds.
    scrape_interval: 60s
    static_configs:
      - targets:
        - 'YOUR_SERVER_HERE:9137'
[...]

Monitoring

Checkout the files in the contrib/monitoring/ directory.

Installation

See Installation doc page.

Troubleshooting

See Troubleshooting doc page.

Development

Golang version 1.21 is used for testing and building the dellhw_exporter.

go mod is used for "vendoring" of the dependencies.

Creating a new Release

Update the version.
1. VERSION file
2. Helm chart: charts/dellhw_exporter/Chart.yaml appVersion: line and bump the Helm chart version: by a patch release version.
  1. Make sure to run make helm-docs in the root of the repo to update the helm chart docs.

Create an entry in the CHANGELOG.md file. Example of a changelog entry:

## 1.12.0 / 2022-02-02

* [ENHANCEMENT] Added Pdisk Remaining Rated Write Endurance Metric by @adityaborgaonkar
* [BUGFIX] ci: fix build routine issues

The following "kinds" of entries can be added:

CHANGE
FEATURE
ENHANCEMENT
BUGFIX

Commit the version increase with a commit messages in format: version: bump to v1.12.0
Create the git tag using git tag v1.12.0
Now push the changes and commit using git push && git push --tags
In a few minutes the new release should be available for "approval" under the releases section. Edit and save the release on GitHub and the release is complete.

dellhw_exporter's People

Contributors

Stargazers

Watchers

dellhw_exporter's Issues

docker container not starting up: exit status 252

I'm trying to run the docker image using the command: "docker run -d --name dellhw_exporter --privileged -p 9137:9137 galexrt/dellhw_exporter"

Unfortunately the container failes to start up. The log says:

time="2019-02-11T00:33:15Z" level=info msg="Starting srcds_exporter (version=1.3.2, branch=HEAD, revision=28563bef56c1c9ed7b2ac6ed4352706e5ca8e596)"
time="2019-02-11T00:33:15Z" level=info msg="Build context (go=go1.10.3, user=root@60ae3f9111bb, date=20180911-07:53:51)"
time="2019-02-11T00:33:15Z" level=info msg="Starting srvadmin-services ..."
time="2019-02-11T00:33:17Z" level=fatal msg="exit status 252"

H750 RAID cannot obtain storage disk information, can upgrade to OMSA 10.2.0.0 to fix it.

dell model：PowerEdge R740
raid model：H750
link: https://dl.dell.com/FOLDER07619118M/1/OM-SrvAdmin-Dell-Web-LX-10.2.0.0-4631_A00.tar.gz

Alerts / Graphs

Hi,

Thanks for this, looks very good! btw, do you have any alerts defined or graphana dashboards?

Cheers

no components found

Hello @galexrt
I installed the v1.13.8 versions in some servers, and I just found out that the pdsik error is still there in one of them, except this time when running the omreport command, it shows no fans, ps, or pdisk components

DEBUG mode
ERRO[0024] ps collector failed after 0.089713s: failed to execute command. exit status 255 ERRO[0024] fans collector failed after 0.093299s: failed to execute command. exit status 255 ERRO[0024] storage_pdisk collector failed after 0.470633s: failed to execute command. exit status 255

the omreport shows that there is no disk, although it has two, which I can confirm through iDRAC UI

`List of Physical Disks on Controller PCIe SSD Subsystem (Not Available)

Controller PCIe SSD Subsystem (Not Available)
No Physical Disks found`

Fans and PS collectors
For this one, It occurs in only very few servers, but I can open another discussion for it
the omreport command says also that there is no fans or Powersupply
Error! No fan probes found on this system.
Error! No instrumented power supplies found on this system.

manual setup

So i'm trying to set this up manually but I don't see what port it runs on or what I need to put in my prometheus configuration so ti scrapes it. Can you help with this and can you update the README.md to provide this in the future?

Fix Release Upload issues

Currently getting the errors below when the build pipeline is trying to upload the artifcats:

promu release .tarballs
error: can't create upload request to https://uploads.github.com/repos/galexrt/dellhw_exporter/releases/9065925/assets?name=dellhw_exporter-1.3.0.linux-386.tar.gz, Post https://uploads.github.com/repos/galexrt/dellhw_exporter/releases/9065925/assets?name=dellhw_exporter-1.3.0.linux-386.tar.gz: write tcp 172.17.25.59:43028->192.30.253.96:443: write: broken pipe
error: can't create upload request to https://uploads.github.com/repos/galexrt/dellhw_exporter/releases/9065925/assets?name=dellhw_exporter-1.3.0.linux-386.tar.gz, Post https://uploads.github.com/repos/galexrt/dellhw_exporter/releases/9065925/assets?name=dellhw_exporter-1.3.0.linux-386.tar.gz: write tcp 172.17.25.59:54743->192.30.253.99:443: write: broken pipe
error: could not upload, status code (422 Unprocessable Entity), msg: Validation Failed, errors: [field: name, code: already_exists]
!! Failed to upload all files: failed to upload "dellhw_exporter-1.3.0.linux-386.tar.gz" after 3 attempts: exit status 1

promu release .tarballs returned exit code 1

Action failed: promu release .tarballs

Have a make rpm target?

Hi,

To deploy this package on RH derivates, a "make rpm" target could be useful.
I forked and edited a bit to make a crude (working) stuff, but that should be enhanced.

Is that something that could be useful to others?

Regards,

Yannick

storage_vdisk parsing error

Seeing a vdisk parsing error on a "Critical" disk

Redirecting to /bin/systemctl status dell_hw_exporter.service
● dell_hw_exporter.service - Prometheus exporter for Dell hardware -- Version true
     Loaded: loaded (/etc/systemd/system/dell_hw_exporter.service; enabled; preset: disabled)
     Active: active (running) since Fri 2024-05-17 18:20:58 UTC; 13s ago
   Main PID: 2045713 (dellhw_exporter)
      Tasks: 26 (limit: 100305)
     Memory: 20.0M
        CPU: 5.726s
     CGroup: /system.slice/dell_hw_exporter.service
             └─2045713 /usr/bin/dellhw_exporter

May 17 18:25:41 m0081489.ppops.net dellhw_exporter[2045713]: time="2024-05-17T18:25:41Z" level=error msg="storage_vdisk collector failed after 0.139247s: strconv.ParseFloat: parsing \"\": invalid syntax"
May 17 18:26:07 m0081489.ppops.net dellhw_exporter[2045713]: time="2024-05-17T18:26:07Z" level=error msg="storage_vdisk collector failed after 0.166057s: strconv.ParseFloat: parsing \"\": invalid syntax"
May 17 18:26:11 m0081489.ppops.net dellhw_exporter[2045713]: time="2024-05-17T18:26:11Z" level=error msg="storage_vdisk collector failed after 0.143599s: strconv.ParseFloat: parsing \"\": invalid syntax"
May 17 18:26:37 m0081489.ppops.net dellhw_exporter[2045713]: time="2024-05-17T18:26:37Z" level=error msg="storage_vdisk collector failed after 0.151444s: strconv.ParseFloat: parsing \"\": invalid syntax"
May 17 18:26:41 m0081489.ppops.net dellhw_exporter[2045713]: time="2024-05-17T18:26:41Z" level=error msg="storage_vdisk collector failed after 0.148115s: strconv.ParseFloat: parsing \"\": invalid syntax"

List of Virtual Disks in the System

Controller PERC H710 Mini (Embedded)

ID;Status;Name;State;Hot Spare Policy violated;Virtual Disk Bad Blocks;Encrypted;Layout;Size;T10 Protection Information Status;Associated Fluid Cache State ;Device Name;Bus Protocol;Media;Read Policy;Write Policy;Cache Policy;Strip Element Size;Disk Cache Policy
0;Ok;Virtual Disk 0;Ready;Not Assigned;No;No;RAID-6;93.13 GiB (99999547392 bytes);No;Not Applicable;/dev/sda;SATA;HDD;Adaptive Read Ahead;Write Back;Not Applicable;128 KB;Enabled
1;Critical;Virtual Disk 1;Ready;Not Assigned;Yes;No;RAID-6;22,259.87 GiB (23901351444480 bytes);No;Not Applicable;/dev/sdb;SATA;HDD;Adaptive Read Ahead;Write Back;Not Applicable;128 KB;Enabled

dellhw_exporter, version 1.13.12 (branch: HEAD, revision: b8900ff8addca32021e9bbb97258cebe7b0c230c)
  build user:       root@d49947862d6f
  build date:       20240516-20:45:11
  go version:       go1.22.3
  platform:         linux/amd64
  tags:             netgo static_build

how to install dellhw_exporter

there is no section for how to install the 'dellhw_exporter'

i am a normal user, i dont know how to install 'dellhw_exporter'

please guide me how to install 'dellhw_export' to real server

make: /bin/promu: Command not found

I believe 'promu' is missing from the list of dependencies in the README.md .

$ git clone https://github.com/galexrt/dellhw_exporter.git
$ cd dellhw_exporter
$ make
...
make: /bin/promu: Command not found
make: *** [Makefile:25: build] Error 127

Multiple controllers cause duplicate metrics logs

Been receiving these duplicate error messages:

dellhw_exporter[3781]: time="2020-05-14T12:28:12-04:00" level=info msg="error gathering metrics: collected metric \"dell_hw_storage_battery_status\" { label:<name:\"controller\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values"

dellhw_exporter[96877]: time="2020-05-14T12:43:35-04:00" level=info msg="error gathering metrics: 9 error(s) occurred:\n* collected metric \"dell_hw_storage_battery_status\" { label:<name:\"controller\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_battery_status\" { label:<name:\"controller\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_enclosure_status\" { label:<name:\"enclosure\" value:\"0_1\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_enclosure_status\" { label:<name:\"enclosure\" value:\"0_0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_enclosure_status\" { label:<name:\"enclosure\" value:\"0_1\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_vdisk_status\" { label:<name:\"vdisk\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_vdisk_status\" { label:<name:\"vdisk\" value:\"1\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_vdisk_status\" { label:<name:\"vdisk\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_vdisk_status\" { label:<name:\"vdisk\" value:\"1\" > gauge:<value:0 > } was collected before with the same name and label values"

dellhw_exporter[96877]: time="2020-05-14T12:43:05-04:00" level=info msg="error gathering metrics: 9 error(s) occurred:\n* collected metric \"dell_hw_storage_enclosure_status\" { label:<name:\"enclosure\" value:\"0_1\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_enclosure_status\" { label:<name:\"enclosure\" value:\"0_0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_enclosure_status\" { label:<name:\"enclosure\" value:\"0_1\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_battery_status\" { label:<name:\"controller\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_battery_status\" { label:<name:\"controller\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_vdisk_status\" { label:<name:\"vdisk\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_vdisk_status\" { label:<name:\"vdisk\" value:\"1\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_vdisk_status\" { label:<name:\"vdisk\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_vdisk_status\" { label:<name:\"vdisk\" value:\"1\" > gauge:<value:0 > } was collected before with the same name and label values"

dellhw_exporter[13642]: time="2020-05-14T12:47:02-04:00" level=info msg="error gathering metrics: 2 error(s) occurred:\n* collected metric \"dell_hw_storage_vdisk_status\" { label:<name:\"vdisk\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values\n* collected metric \"dell_hw_storage_battery_status\" { label:<name:\"controller\" value:\"0\" > gauge:<value:0 > } was collected before with the same name and label values"

These are with OMSA 9.1.0 and 9.4.0

Had a look through and it seems to be a how omreport reports the information, for eg:

The name of device is unique however the scraped fields need not always be unique.

omreport storage battery -fmt ssv
List of Batteries in the System

Controller PERC H840 Adapter  (Slot 1)

ID;Status;Name;State;Recharge Count;Max Recharge Count;Learn State;Next Learn Time;Maximum Learn Delay
0;Ok;Battery ;Ready;Not Applicable;Not Applicable;Not Applicable;Not Applicable;Not Applicable

Controller PERC H740P Mini  (Slot Embedded)

ID;Status;Name;State;Recharge Count;Max Recharge Count;Learn State;Next Learn Time;Maximum Learn Delay
0;Ok;Battery ;Ready;Not Applicable;Not Applicable;Not Applicable;Not Applicable;Not Applicable

The metrics are still collected and displayed without crashing the exporter.
However it only displays the metric for the first item.

which packages of OMSA should be use

when i un-tar OM-SrvAdmin-Dell-Web-LX-9.1.0-2757.RHEL7.x86_64_A00.tar.gz, there are a lot of packages.

Which one should be using for dellhw_exporter

Thank you

linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-itunnelprovider-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-rac4-populator-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-isvc-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-realssd-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-idracadm7-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-storage-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-cm-9.1.0-17.12.00.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-isvc-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-argtable2-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-sysfsutils-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-idracadm-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-racadm4-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-deng-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-smcommon-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-idrac-vmcli-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-rac-components-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-deng-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-omaksmig-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-xmlsup-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/libsmbios-2.3.1-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/raidcfg-6.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/syscfg-6.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-tomcat-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-racdrsc-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-idrac7-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-storage-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-omacs-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-storelib-sysfs-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-racadm5-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-racsvc-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-jre-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-idrac-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-hapi-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-storage-cli-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-idrac-ivmcli-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-omcommon-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-omacore-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-smweb-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-oslog-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-nvme-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-storelib-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-marvellib-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/smbios-utils-bin-2.3.1-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-ominst-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/srvadmin/RHEL7/x86_64/srvadmin-omilcore-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/
linux/RPMS/supportRPMS/metaRPMS/RHEL7/
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-storageservices-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-all-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-server-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-webserver-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-idrac-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-base-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-rac5-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-storageservices-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-standardAgent-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-storageservices-cli-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-server-cli-9.1.0-2757.12163.el7.x86_64.rpm
linux/RPMS/supportRPMS/metaRPMS/RHEL7/x86_64/srvadmin-rac4-9.1.0-2757.12163.el7.x86_64.rpm
linux/SRPMS/
linux/SRPMS/license.txt
linux/SRPMS/gpl.txt
linux/supportscripts/
linux/supportscripts/srvadmin-uninstall.sh
linux/supportscripts/prereqcheck/
linux/supportscripts/prereqcheck/license.txt
linux/supportscripts/prereqcheck/smbios-sys-info-lite_i386
linux/supportscripts/prereqcheck/ClientSystemList.txt
linux/supportscripts/prereqcheck/syslist.txt
linux/supportscripts/prereqcheck/smbios-sys-info-lite_x86_64
linux/supportscripts/prereqcheck/8gsyslist.txt
linux/supportscripts/prereqcheck/lockfile
linux/supportscripts/prereqcheck/9gsyslist.txt
linux/supportscripts/prereqcheck/CheckSystemType
linux/supportscripts/prereqcheck/smbios-sys-info-lite
linux/supportscripts/srvadmin-services.sh
linux/supportscripts/srvadmin-install.sh
linux/custom/RHEL7/add-RAC4/x86_64/srvadmin-rac4-populator-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC4/x86_64/srvadmin-racadm4-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC4/x86_64/srvadmin-rac-components-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC4/x86_64/srvadmin-racdrsc-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC4/x86_64/srvadmin-racsvc-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC4/x86_64/srvadmin-idrac-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/
linux/custom/RHEL7/Remote-Enablement/x86_64/
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-itunnelprovider-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-isvc-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-cm-9.1.0-17.12.00.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-isvc-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-deng-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-smcommon-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-deng-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-xmlsup-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/libsmbios-2.3.1-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-omacs-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-hapi-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-omcommon-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-omacore-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/smbios-utils-bin-2.3.1-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-ominst-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Remote-Enablement/x86_64/srvadmin-omilcore-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC5/x86_64/srvadmin-argtable2-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC5/x86_64/srvadmin-racadm4-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC5/x86_64/srvadmin-rac-components-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC5/x86_64/srvadmin-racdrsc-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC5/x86_64/srvadmin-racadm5-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-RAC5/x86_64/srvadmin-idrac-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-isvc-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-cm-9.1.0-17.12.00.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-isvc-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-deng-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-smcommon-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-deng-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-xmlsup-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/libsmbios-2.3.1-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-omacs-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-hapi-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-omcommon-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-omacore-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-oslog-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/smbios-utils-bin-2.3.1-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-ominst-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/Server-Instrumentation/x86_64/srvadmin-omilcore-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-iDRAC/x86_64/srvadmin-idracadm7-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-iDRAC/x86_64/srvadmin-argtable2-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-iDRAC/x86_64/srvadmin-idracadm-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-iDRAC/x86_64/srvadmin-racadm4-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-iDRAC/x86_64/srvadmin-idrac-vmcli-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-iDRAC/x86_64/srvadmin-rac-components-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-iDRAC/x86_64/srvadmin-racdrsc-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-iDRAC/x86_64/srvadmin-idrac7-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-iDRAC/x86_64/srvadmin-idrac-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-StorageManagement/x86_64/srvadmin-realssd-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-StorageManagement/x86_64/srvadmin-storage-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-StorageManagement/x86_64/srvadmin-sysfsutils-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-StorageManagement/x86_64/srvadmin-storage-snmp-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-StorageManagement/x86_64/srvadmin-storelib-sysfs-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-StorageManagement/x86_64/srvadmin-storage-cli-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-StorageManagement/x86_64/srvadmin-nvme-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/add-StorageManagement/x86_64/srvadmin-storelib-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/srvadmin-smcommon-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/srvadmin-omaksmig-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/libsmbios-2.3.1-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/srvadmin-tomcat-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/srvadmin-omacs-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/srvadmin-jre-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/srvadmin-omcommon-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/srvadmin-smweb-9.1.0-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/smbios-utils-bin-2.3.1-2757.12163.el7.x86_64.rpm
linux/custom/RHEL7/SA-WebServer/x86_64/srvadmin-omilcore-9.1.0-2757.12163.el7.x86_64.rpm

storage_pdisk collector failed

Hello

I am getting collectors errors failing, most of time it's fans and storage_pdisk collectors

/var/log/messages:146458:Jan 25 10:25:41 dellhw_exporter[1020987]: time="" level=error msg="storage_pdisk collector failed after 0.388469s: exit status 255"

is there anyone who can help get rid of this messages and solve the issue?
Thanks

Is it working with OMSA 9.1?

tnx

Helm chart for easy Kubernetes deployment

A simple helm chart to deploy a DaemonSet of the dellhw_exporter should be added.

New Release?

Hello,

Can a new release get cut? We'd like to run this as a windows service (#54) and pull the binary from an official release.

Thanks for the project, and thank you in advance!

dell_hw_nic_status metric returning 1 for functional interfaces

Hi @galexrt, thanks for this great contribution to the community. Such an exporter is essential for Dell based on-prem observability!

While analyzing the values returned by the exporter from a couple of different servers, I noticed that some metrics were returning 1s for network interfaces that were known to be functional. After digging into the code, I found that it only marks an interface as functional (0) when the report either returns "Connected" or "Full" in the fifth field. While this covers most scenarios, some edge cases are not covered.

Here is an example of a Team Interface that currently shows 1 in the metric but is functional:

Index             : 1
Interface Name    : br0
Vendor            : Linux
Description       : Network Bridge
Redundancy Status : Not Applicable

I believe this happens because "Not Applicable" is not covered by the exporter logic. It would be a good improvement to also check the field name before matching its value.

I can open a Pull Request including this scenario!

How should run exporter to connect Dell EMC device

I have some devices from EMC (Dell ) now I did follow steps would you please help me :

My Os that want run exporter on that is Redhat 8 :
1- curl -O https://linux.dell.com/repo/hardware/dsu/bootstrap.cgi
2. bash bootstrap.cgi
3. yum install srvadmin-all
I did above steps . What should I do for the next step ?
Where should insert username- password - ip address to connect dell device ?

Use different package for flags

Currently a modified https://github.com/coreos/pkg (https://github.com/galexrt/pkg) is used to allow flags with dots to be from env vars as well.
There are other flag and / or "config" management packages out there which can do both well.

Note to self: Delete https://github.com/galexrt/pkg after replacing the package.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

chore(deps): update dependency go to v1.22.6

Detected dependencies

dockerfile

Dockerfile

docker.io/library/rockylinux 9.3

github-actions

.github/workflows/build_release.yml

actions/checkout v4

actions/setup-go v5

elgohr/Publish-Docker-Github-Action v5

elgohr/Publish-Docker-Github-Action v5

.github/workflows/documentation.yml

actions/checkout v4

azure/setup-helm v4

helm/chart-releaser-action v1.6.0

actions/checkout v4

actions/checkout v4

peaceiris/actions-gh-pages v4

.github/workflows/test.yml

actions/checkout v4

actions/setup-go v5

gomod

go.mod

go 1.22

go 1.22.4

github.com/kardianos/service v1.2.2

github.com/prometheus/client_golang v1.19.1

github.com/prometheus/common v0.55.0

github.com/sirupsen/logrus v1.9.3

github.com/spf13/pflag v1.0.5

github.com/stretchr/testify v1.9.0

helm-values

charts/dellhw_exporter/values.yaml

Check this box to trigger a request for Renovate to run again on this repository

Makefile: build and tarball have wrong directories referenced

I noticed the Makefile has wrong directories referenced for the build and tarball directives.

Minor trouble with updated build routines (promu-related)

Hi Alex,

while trying to use your updated build setup with promu I stumbled over some minor issues which break our builds.

a) promu is referenced as $(PROMU) in the Makefile, which is only set to promu, assuming that it lives in the path. I suggest to use either the location where you put it ($(FIRST_GOPATH)/bin/promu) or set that as variable PROMU

b) Makefile assumes PREFIX being set when calling promu --prefix $(PREFIX), but PREFIX might not be set. I suggest to add --prefix $(PREFIX) only when PREFIX is set.

Cheers,
Stephan

debug mode: flagutil always outputting env vars

Noticed flagutil always outputting the env vars at every call of the dellhw_exporter binary.
Is this by design or a debug feature left behind?

Thanks!!!

Build fails with: case-insensitive import collision: "github.com/sirupsen/logrus"

The following command fails to build:

curl -sSL -o /tmp/dellhw_exporter.tar.gz https://github.com/galexrt/dellhw_exporter/archive/v1.3.5.tar.gz && mkdir /tmp/dellhw_exporter     && tar --strip 1 -xvf /tmp/dellhw_exporter.tar.gz
 -C /tmp/dellhw_exporter && cd /tmp/dellhw_exporter && go get -d ./... && make build

With the error:

package github.com/sirupsen/logrus: case-insensitive import collision: "github.com/sirupsen/logrus" and "github.com/Sirupsen/logrus"

This appears to be due to the author of this lib renaming the account.

If I run the following before go get, I can build without issue:

find . -type f -print0 | xargs -0 sed -i 's/Sirupsen/sirupsen/g'

Should we update the case to reflect the upstream rename?

Thanks for sharing your work.

metrics for the duration of the omreport calls and tunable timeouts

the omreport commands seem to take varying amounts of time, on dell R640 they even sometimes exceed the 10 second timeouts

it might be interesting to have metrics about how long each command takes to better tune the timeouts of the commands.

dellhw-exporter causes a large amount of zombie processes

Hi,

I have observed large number of omreport and omcliproxy processes generated but not exited or terminated.

Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: omreport invoked oom-killer: gfp_mask=0x6000c0(GFP_KERNEL), order=0, oom_score_adj=999
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: CPU: 110 PID: 1319442 Comm: omreport Kdump: loaded Not tainted 4.18.0-372.36.1.el8_6.mr3789_221121_2132.x86_64 #1
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: Tasks state (memory values in pages):
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [ 12750] 0 12750 35965 615 167936 0 -1000 conmon
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [ 12777] 0 12777 179450 4466 196608 0 999 dellhw_exporter
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [ 12844] 0 12844 49366 1786 180224 0 999 dsm_sa_eventmgr
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [ 12845] 0 12845 84507 2358 217088 0 999 dsm_sa_snmpd
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [ 12851] 0 12851 587311 10325 581632 0 999 dsm_sa_datamgrd
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [ 14970] 0 14970 152261 5917 393216 0 999 dsm_sa_datamgrd
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314763] 0 1314763 2926 650 69632 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314764] 0 1314764 2926 637 69632 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314765] 0 1314765 2926 650 69632 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314766] 0 1314766 2926 663 69632 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314767] 0 1314767 2926 638 65536 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314768] 0 1314768 2926 637 61440 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314769] 0 1314769 2926 664 65536 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314771] 0 1314771 2926 644 69632 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314774] 0 1314774 2926 637 69632 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314776] 0 1314776 2926 627 69632 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314778] 0 1314778 2926 653 65536 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314780] 0 1314780 9239 1179 114688 0 999 omcliproxy
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314781] 0 1314781 2926 627 73728 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314783] 0 1314783 2926 650 61440 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314784] 0 1314784 9239 1199 114688 0 999 omcliproxy
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314785] 0 1314785 9239 1190 118784 0 999 omcliproxy
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314787] 0 1314787 2926 663 65536 0 999 omreport
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314788] 0 1314788 9239 1205 122880 0 999 omcliproxy
Sep 26 16:36:59 devenv01-worker003.devenv01.nfvi.localdomain kernel: [1314790] 0 1314790 9239 1145 114688 0 999 omcliproxy

I have posting all the results here as it would be redundant, but output similar to approximately 850 lines was seen following this.
It is likely that these processes were started in the dellhw_exporter Pod. From the name of this Pod,
I speculate that it is an application similar to an agent for monitoring Dell hardware. as Dellhw exporter had a omreport cmd wraper to it to get the data from machine.

Regarding the omreport and omcliproxy, i would like to confirm the following things:

It seems abnormal for over 800 of these processes to be running, is that correct?
Is there any report of the dellhw_exporter Pod being in an abnormal state due to the oom-killer (for example, process proliferation like this time)?
For example, with some monitoring agent applications, there is a scenario where processes proliferate

if they behave such as extracting all files including information about the OS under /proc, leading to a sharp increase in the load on the system.
Are these processes performing any processing that could cause a load on the system when the number of processes increases rapidly?

Add raid layout for vdisk

use case:
Sometimes we don't care about a broken disk because of the a specific RAID setup, it would be nice for us to be able to use the RAID controller metric to alert on.

proposition:
I was thinking something like;

dell_hw_storage_vdisk_raid{vdisk="0"} 10 // RAID 10
dell_hw_storage_vdisk_raid{vdisk="1"} 5 // RAID 5

storage_vdisk parsing error

dellhw_exporter, version 1.13.10 (branch: HEAD, revision: 03ef74fb6af9a63035d5c90e990be845080159b6)
  build user:       root@7c44df39d577
  build date:       20240228-22:12:19
  go version:       go1.21.7
  platform:         linux/amd64
  tags:             netgo static_build

Mar 21 15:53:57 m0394125.ppops.net dellhw_exporter[117188]: time="2024-03-21T15:53:57Z" level=error msg="storage_vdisk collector failed after 0.039089s: strconv.ParseFloat: parsing \"\": invalid syntax"
Mar 21 15:54:08 m0394125.ppops.net dellhw_exporter[117188]: time="2024-03-21T15:54:08Z" level=error msg="storage_vdisk collector failed after 0.035442s: strconv.ParseFloat: parsing \"\": invalid syntax"

Seeing parsing errors for vdisk on 2 of the newest nodes in our infrastructure. Let me know if I can provide any other information that would help.

Predictive failure

Hi All,

how about a metric for predictive failure of the disks?

Cheers

Releases: tarballs

Seems like not all releases don't have tarballs in them.
Do you know if there's a plan to publish tarball releases in github as well.
We use them to deploy them via chef is why.

Additionally I noticed some discrepancies between release versions and actual binary versions. For eg: v1.3.5 and v1.3.2.

Thank you again!

gometalinter issues

Hi @galexrt ,

You could be interested seeing the output of gometalinter, and you could even build a Makefile target running it automatically after fixing or excluding some issues.

See,
$ gometalinter --vendor ./...

My 2 cents.

Running v1.13.12 against iSM

Hey,

Nice little exporter, tried running it against iSM 5.3.0 / iSM OSC 7.3.0 on iDRAC 9 v7.00.00.00, and here are my findings:

immediately got an error when starting:
- /usr/libexec/instsvcdrv-helper: line 519: lsmod: command not found x5
- exporter still starts
dell_hw_chassis_temps all report 0, but dell_hw_chassis_temps_reading have values, unsure what the difference between these two are

All other metrics seems to work fine! 👍

Version Info missing

The version info is empty.

❯ docker run -it --entrypoint /bin/bash  galexrt/dellhw_exporter
[root@03327a5e0100 /]# ls
anaconda-post.log  bin  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
[root@03327a5e0100 /]# dellhw_exporter 
TEST: DELLHW_EXPORTER_COLLECTORS_CMD_TIMEOUT
TEST: DELLHW_EXPORTER_COLLECTORS_ENABLED
TEST: DELLHW_EXPORTER_COLLECTORS_OMR_REPORT
TEST: DELLHW_EXPORTER_COLLECTORS_PRINT
TEST: DELLHW_EXPORTER_CONTAINER
TEST: DELLHW_EXPORTER_DEBUG
TEST: DELLHW_EXPORTER_HELP
TEST: DELLHW_EXPORTER_VERSION
TEST: DELLHW_EXPORTER_WEB_LISTEN_ADDRESS
TEST: DELLHW_EXPORTER_WEB_TELEMETRY_PATH
INFO[0000] Starting dellhw_exporter (version=, branch=, revision=) 
INFO[0000] Build context (go=go1.13.8, user=, date=)    
INFO[0000] Setting command timeout to 15                
INFO[0000] Enabled collectors:                          
INFO[0000]  - chassis_batteries                         
INFO[0000]  - fans                                      
INFO[0000]  - storage_pdisk                             
INFO[0000]  - storage_vdisk                             
INFO[0000]  - nics                                      
INFO[0000]  - ps                                        
INFO[0000]  - ps_amps_sysboard_pwr                      
INFO[0000]  - storage_controller                        
INFO[0000]  - storage_enclosure                         
INFO[0000]  - processors                                
INFO[0000]  - volts                                     
INFO[0000]  - chassis                                   
INFO[0000]  - memory                                    
INFO[0000]  - storage_battery                           
INFO[0000]  - system                                    
INFO[0000]  - temps                                     
C^C
[root@03327a5e0100 /]# ^C
[root@03327a5e0100 /]# ls
anaconda-post.log  bin  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
[root@03327a5e0100 /]# which dellhw_exporter
/usr/bin/dellhw_exporter
[root@03327a5e0100 /]# dellhw_exporter --version
TEST: DELLHW_EXPORTER_COLLECTORS_CMD_TIMEOUT
TEST: DELLHW_EXPORTER_COLLECTORS_ENABLED
TEST: DELLHW_EXPORTER_COLLECTORS_OMR_REPORT
TEST: DELLHW_EXPORTER_COLLECTORS_PRINT
TEST: DELLHW_EXPORTER_CONTAINER
TEST: DELLHW_EXPORTER_DEBUG
TEST: DELLHW_EXPORTER_HELP
TEST: DELLHW_EXPORTER_WEB_LISTEN_ADDRESS
TEST: DELLHW_EXPORTER_WEB_TELEMETRY_PATH
dellhw_exporter, version  (branch: , revision: )
  build user:       
  build date:       
  go version:       go1.13.8
[root@03327a5e0100 /]#

I noticed the same when building it using Makefile

dellhw_exporter sets iDrac Hostname, OS and OS version to those of container

Hi,

We are running dellhw_exporter from the helm chart (v0.2.12) and we see that in the iDrac, the Host Name, Operating System and Operating System Version now reflect on what is running in the pod (dellhw-exporter-xxxxx; Rocky Linux; release 9.4 (Blue Onyx) Kernel 5.15.0-112-generic (x86_64)) instead of what is running on the hardware.

Support for firmware and bios versions (Feature request)

omreport is capable of extracting the version for some firmware and BIOS - it would be really helpful to be able to extract them and expose them as metrics (as a label).
This can help monitoring outdated firmwares or heterogenous cluster states.

I have half a PR in the making for this.

OMSA running in container

Hello, @juliantaylor @galexrt @sfudeus @jddggh @kyle-williams-1

does it support OMSA also running in container ? e.g. https://github.com/ShaneMcC/docker-omsa