masterwishx
Member
I'm using Unraid server, but don't have experience with MQTT, so for MQTT export receive, I will need install mosquito (MQTT data broker) docker on server side, for receive all data?
Prometheus Adapter for HWiNFO (+ Grafana Dashboard)
- Thread starter Kallex
- Start date
I'm using Unraid server, but don't have experience with MQTT, so for MQTT export receive, I will need install mosquito (MQTT data broker) docker on server side, for receive all data?
Has anyone been able to add their Corsair AIO to Promdater? I tried the catch all
but I am not getting any more information such as my AIO. After I added the line I restarted the promdater service and when that didn't work I rebooted.
My Prometheusmapping.yaml is default except I added that catch all to a line directly above the AggregateValues.
Did I miss something?
YAML:
- '(?<MetricName>.*)'but I am not getting any more information such as my AIO. After I added the line I restarted the promdater service and when that didn't work I rebooted.
My Prometheusmapping.yaml is default except I added that catch all to a line directly above the AggregateValues.
Did I miss something?
I'm not sure what Unraid runs, but for PromDapter + HWiNFO setup you will need something that runs HWiNFO - that is Windows platform - to begin with. The MQTT in this context is just a protocol-format to output the HWiNFO data into processable format, like Prometheus is as well.
So can you explain a bit more of your systems and goals. Are you looking to monitor Unraid or use it as part of runner to monitor something else?
Corsair iCue software and HWiNFO have issues together;
HWiNFO Issue with iCue
Hello, I've been using my commander pro for 3 years now and have also been using HWiNFO for longer. Within the last few months (I think back in May or June) I haven't been able to edit my cooling info in iCue. I've figured out it is an issue with iCue when HWiNFO is open but it didn't used to be...
www.hwinfo.com
My own solution for monitoring Corsair product (PSU in my case) was not to use iCue for monitoring it at all. For AIO where you might need more controlling it might not be feasible case.
Do the sensors/readings appear OK in HWiNFO window? If they do, then it's just about configuring PromDapter properly.
Do you get any metrics out, just the Corsair AIO ones are missing?
The Prometheusmapping.yaml is confusing in the setup, because it installs "original default" under C:\Program Files - but that's not the one to edit. The proper one to edit is the one:
C:\ProgramData\PromDapter\Prometheusmapping.yaml
Can you double check that you edited the right one?
masterwishx
Member
Sorry, I not explained well I meaned I run HWiNFO with PromDapter in Windows and run Prometheus + Grafana dockers on Unraid Server.
Using HWiNFO Home Cluster.json as Dashboard.
I was thinking I need MQTT docker for receive data but I think for this I can use MQTT builded in grafana, instead Prometheus for data server in Grafana.
Do you want to make work both Prometheus or MQTT in PromDapter?
masterwishx
Member
Or maybe we still need Mosquito for receive MQTT data in grafana?
Thank you for your detailed reply, sorry for being an idiot I did the one in program files.Corsair iCue software and HWiNFO have issues together;
HWiNFO Issue with iCue
Hello, I've been using my commander pro for 3 years now and have also been using HWiNFO for longer. Within the last few months (I think back in May or June) I haven't been able to edit my cooling info in iCue. I've figured out it is an issue with iCue when HWiNFO is open but it didn't used to be...
My own solution for monitoring Corsair product (PSU in my case) was not to use iCue for monitoring it at all. For AIO where you might need more controlling it might not be feasible case.
Do the sensors/readings appear OK in HWiNFO window? If they do, then it's just about configuring PromDapter properly.
Do you get any metrics out, just the Corsair AIO ones are missing?
The Prometheusmapping.yaml is confusing in the setup, because it installs "original default" under C:\Program Files - but that's not the one to edit. The proper one to edit is the one:
C:\ProgramData\PromDapter\Prometheusmapping.yaml
Can you double check that you edited the right one?
The information is showing up in HWInfo just fine, I just made the change in the correct YAML file and it solved my issue.
Michael_Afton
New Member
How to open this osd
sailing_nut
Member
This is not an OSD. It is a Prometheus adapter to generate a data feed. The best way to visualize the feed is to install Grafana, configure this as a data source, then design your dashboard with whatever you want to display. Oh, and I forgot to mention that you will also need to fiddle with the YAML file to extract all of the info you want to display from HWiNFO.
Hi all 
First off, thanks for the tool hwinfo, the prometheus adapter and the powershell script nice work!
I used gwilders PS script and encountered an error when multiple parts from same type are used.
In my example I use 4 Aquacomputer Pumps, but in the variable $psdata they all have the same source. So I wrote a little hack in PS for this:
Would be nice if the prometheus adapter can extract the different parts!
Keep up the good work <3
Kind regards, Clero
First off, thanks for the tool hwinfo, the prometheus adapter and the powershell script
nice work!I used gwilders PS script and encountered an error when multiple parts from same type are used.
In my example I use 4 Aquacomputer Pumps, but in the variable $psdata they all have the same source. So I wrote a little hack in PS for this:
Bash:
$psdata | Group-Object -Property Source,Name,Category | ?{$_.Count -gt 1} | %{
$i=1
$_.Group | %{
$_.Source = $_.Source + " # $i"
$i++
}
}Would be nice if the prometheus adapter can extract the different parts
!Keep up the good work <3
Kind regards, Clero
Can you elaborate a bit. If recall right, gwildor's great script makes the MQTT pushing from PromDapter outputted data. So are you using MQTT as a target? And then in the process do you have multiple sources outputting same stuff.
Is the multiple sensors having same name also problem with the PromDapters initial Prometheus output that you get from http://localhost:10445/metrics?
I'm trying to understand if there are two problems I could fix. The MQTT pusher is on my too-delayed TODO list (which I could use other testers when I eventually get it done) and that multiple sensor thing I would like to address also. Just want to understand if it's in the PS script or in PromDapter output.
Is the multiple sensors having same name also problem with the PromDapters initial Prometheus output that you get from http://localhost:10445/metrics?
I'm trying to understand if there are two problems I could fix. The MQTT pusher is on my too-delayed TODO list (which I could use other testers when I eventually get it done) and that multiple sensor thing I would like to address also. Just want to understand if it's in the PS script or in PromDapter output.
Hi Kallex
I use just the powershell script as posted above without MQTT.
How can I adjust the Prometheusmapping.yaml to get these values so I can verify your question?
I use just the powershell script as posted above without MQTT.
I dont know, didnt get the results with the url. Here is the output from the ps script:
Code:
Source : GPU [#0]: NVIDIA GeForce RTX 3060 Laptop:
Name : GPU Core (NVVDD) Output Power
Value : 0.35865625
Unit : W
Category : SENSOR_TYPE_POWER
Source : GPU [#0]: NVIDIA GeForce RTX 3060 Laptop:
Name : GPU Core (NVVDD) Output Power
Value : 0.851
Unit : W
Category : SENSOR_TYPE_POWERHow can I adjust the Prometheusmapping.yaml to get these values so I can verify your question
?How can I adjust the Prometheusmapping.yaml to get these values so I can verify your question
You can try to add catch all phrase in the last entry, but before aggregate values:
YAML:
- '(?<MetricName>.*)'That should provide you all of your sensors.
It does that without trying to categorize any sensor names etc, so remember to remove it after the testing as it possibly messes up with your properly defined namings.
Ok, I can confirm its also with the url.
*edit
this is also with the 4 Aquacomputer pumps
# HELP hwi_gpu_core_nvvdd_output_power_w GPU Core (NVVDD) Output Power W - GPU [#0]: NVIDIA GeForce RTX 3060 Laptop:
hwi_gpu_core_nvvdd_output_power_w{unit="W",sensor_type="SENSOR_TYPE_POWER",sensor="GPU Core (NVVDD) Output Power",source="GPU [#0]: NVIDIA GeForce RTX 3060 Laptop: ",host="NB-G14-CLERO"} 0
hwi_gpu_core_nvvdd_output_power_w{unit="W",sensor_type="SENSOR_TYPE_POWER",sensor="GPU Core (NVVDD) Output Power",source="GPU [#0]: NVIDIA GeForce RTX 3060 Laptop: ",host="NB-G14-CLERO"} 0.299625
hwi_gpu_core_nvvdd_output_power_w{unit="W",sensor_type="SENSOR_TYPE_POWER",sensor="GPU Core (NVVDD) Output Power",source="GPU [#0]: NVIDIA GeForce RTX 3060 Laptop: ",host="NB-G14-CLERO"} 0
hwi_gpu_core_nvvdd_output_power_w{unit="W",sensor_type="SENSOR_TYPE_POWER",sensor="GPU Core (NVVDD) Output Power",source="GPU [#0]: NVIDIA GeForce RTX 3060 Laptop: ",host="NB-G14-CLERO"} 0.299625
*edit
this is also with the 4 Aquacomputer pumps
So if I understand it right, this GPU example has two sensors having equal name but are in fact different ones?
That's logically quite a tricky one, as if PromDapter's API sees them alike, there is no guarantee they'll be in the same order on every call. So automatically indexing them 1, 2, 3... or alike might or might not work.
EDIT: The HWINFO API might return them consistently in the same order, but PromDapter's processing isn't focusing to guarantee it remain that. There is for example parallel processing happening when sensor counts go above certain limits, and that will change the output order by itself.
That's logically quite a tricky one, as if PromDapter's API sees them alike, there is no guarantee they'll be in the same order on every call. So automatically indexing them 1, 2, 3... or alike might or might not work.
EDIT: The HWINFO API might return them consistently in the same order, but PromDapter's processing isn't focusing to guarantee it remain that. There is for example parallel processing happening when sensor counts go above certain limits, and that will change the output order by itself.
Hi Kallex,
I am currently trying to query the new PresentMon values. However, for some reason it does not want to work?
I would assume that the following line should work. I have renamed the framerate values.
# PresentMon
- '(?<Entity>PresentMon) (?<MetricName>Framerate_Presented|Framerate_Displayed|Frame Time|GPU Busy)
Do you have any idea what could be the cause?
Edit: Have solved it myself.
I am currently trying to query the new PresentMon values. However, for some reason it does not want to work?
I would assume that the following line should work. I have renamed the framerate values.
# PresentMon
- '(?<Entity>PresentMon) (?<MetricName>Framerate_Presented|Framerate_Displayed|Frame Time|GPU Busy)
Do you have any idea what could be the cause?
Edit: Have solved it myself.
Last edited:
