Search results

Oh yeah you can rename the sensor name in hwinfo, I don't remember if you can rename the source too. But renaming either should be enough.

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...

You can try to add catch all phrase in the last entry, but before aggregate values: - '(?<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...

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...

Sorry for not being active here. I'll try to get back to finishing the MQTT provider implementation soon.

Corsair iCue software and HWiNFO have issues together; https://www.hwinfo.com/forum/threads/hwinfo-issue-with-icue.7627/ 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...

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...

Just for some status report of not releasing anything. I've been busy elsewhere, but I'm still on the MQTT implementation. It requires bit of refactoring of the existing codebase, so it wasn't as trivial to add as I initially thought. I hope to finish it soon-ish.

I'm still on this. I have had busy autumn, so just didn't manage to focus the tiny bit for this yet.

It takes one to know one.

Thanks, I guess I'm running out of excuses here :) . I'll implement those parts into the adapter directly, with some configurable repeatable push for MQTT endpoint. I try to do it in near future/this week (weekend included).

Hey, what a cool suggestion! I checked the MQTT specs and available .NET libraries and I think it is small effort to add support for MQTT. I can try to add it in the near-ish future, but of course if someone wants to submit a pull request for that, it's also OK :-).

There you go, should be fixed now: https://github.com/kallex/PromDapter/releases/tag/v2022.0830.30-beta

Oh sorry about that. I'll fix it asap.

I released quick attempt for the fix. Can you test the newest release and report back, if the error is still there. https://github.com/kallex/PromDapter/releases/tag/v2022.0828.29-beta

I can help you :) . It seems there's a bug in the calculation of parallelism. I get to check this after the weekend, sorry that you have to wait. It seems your installation and setup is all good, the degree of parallelism is based on the cores and/or total amount of metrics and there apparently...

I don't have experience of that kind of aggregating yet, but I think I'm looking to get something similar with WMI cpu and memory loads. I'll report back if I get experienced enough to have some/any idea about such calculations.

Added WMI support for the newest beta. NOTE! JSON support is broken in this version, so if you're relying on it and want to use WMI, please let me know and I hurry up the fix for this version. Otherwise just stick with the earlier release for now. Example configuration added to the bottom of...

The Entity_CPU ones are the ones, where there is no CPU in the metricname to recognize/grab the value from. The Entity - tag is when there is CPU in the text to recognize. So in your case it would be Entity_CPU, as/if you want to categorize them "under" CPU when there is no CPU in the...

There's the "catch all" phrase described, that I don't recall now off my head. You can use that to get the raw version of ALL the metrics and then refine the Entity etc categorizing off that. I'll get to this asap again, sorry for late reply.