Search results

Thank you for your kind words :-) (and thanks for Martin to making the HWiNFO in the first place, I had to do PromDapter because the alternatives providing Prometheus-output were insufficient metric/sensorwise). I have some roadmap to improve PromDapter, but it has worked bit too well (not much...

That's odd... this line should catch them: - '(?<Entity>Core) (?<CoreNo>\d+)' They should be visible in http://localhost:10445/metrics view something as following (the ... means there is other stuff, but coreno and unit should be like that among other things)...

It's most likely the HWiNFO Sensors window; it needs to be opened - either manually clicking it or at startup, even as minimized, but still opened :).

Hi, Ensure you have HWiNFO open and with sensors window also opened. It can be minimized later on, but the sensors window has to be opened once for the technical data interface to work properly. So just check that you can see the sensor data in HWiNFO and then try to see if...

Hi, so we got all the others to work except for the temperatures by cores? Can you again share the exact sensor names, lets see if we can solve it out.

Ok, let me get on with some control questions, if I understood this right. So we're looking for these missing 6 values: Power sensors : "IA Cores Power", "GT Cores Power" and "Total DRAM Power" Temperature sensors : "CPU IA Cores", "CPU GT Cores (Graphics)" and "VR VCC Temperature (SVID)" Now...

Ok got it extracted, thanks. I'll go through it, but busy elsewhere today, but I try to get back to you by tomorrow.

Can you zip the current .yaml file and the output of http://localhost:10445/metrics/help ... and if you can also the debug-version output with that catch-all in the first line? I try to figure out what's the issue with the missing ones.

Of those, I think the order might be relevant too, as the "CPU IA Cores" and "CPU GT Cores (Graphics)" should be already catched by this: - '(?<Entity>CPU) (?<MetricName>Package|IA Cores|GT Cores \(Graphics\))' They're just prefixed as hwi_cpu (the entity part in that groups them within...

Okies I have a hypothesis about "CPU (Weight)" - issue that we can lay on order of regexp (and thus blame the regex ;-) ). If there is regexp separately with just plain "CPU" in it and the CPU Weight is after that, it gets caught by alone "CPU" before. So in your custom lines, try rather...

Regex is awful technology, but its unfortunately one of the best ones to use in this case :-( - don't blame yourself for difficulties of getting regexps right! Test your regexp with exact sensor name: http://regexstorm.net/tester Paste the regex between '' as-is there and then copy-paste the...

I was going to modify the last additions, but got curious because that CPU (PECI) should have worked. We could try first with the following simplified (and also, double check you copied to "C:\ProgramData" - and not on "C:\Program Files"), but at least some of these should become visible...

You can use that as an example, it isn't totally fragile, but if you can spot the minor differences in your edits vs these. Of course might be that the editor you're using is causing the problem, standard Notepad should work. But let me know if you need more assistance, I'm happy to hear it...

The file is very sensitive about the indenting depth and it might be (based on what I see above), there might be spaces getting added by the forum as well. I added those to the default file and attached here, if you can try this one it should work better.

I know its unnecessary confusing (sorry for that), I will rename the reference one to different on next publish to reduce the confusion.

Can you list full path of Prometheusmapping.yaml? As its in two places where one is "for reference" and one is the real use. The real one to edit is "C:\ProgramData\..." - NOT "C:\Program Files\...".

Ok to be safe make a copy of your current C:\ProgramData\PromDapter\Prometheusmapping.yaml Try adding following lines as last in the "IndividualValues" section BEFORE/ABOVE the -name: AggregateValues They can be above and not last of that section, but they will be wider scope regexps, so be...

This is good list, I'll compare to mine and see how to generalize the yaml regex-definitions. No need to do that (well right now it would be one option); but for better flexibility I had planned to provide name-mapping in the PromDapter to solve exactly this. Regular expressions in yaml can...

Sure; can you list the exact names of those sensors? You can get the exact names In HWiNFO sensor screen if you hit F2 (or right mouse-click and Rename) when a sensor-row is selected and copy-paste it from there. The generic idea is to edit the "C:\ProgramData\PromDapter\Prometheusmapping.yaml"...

Yeah for RPM that works, so there is no issue in your case now :-). But for relative percentage 0-100% it sometimes becomes ambiguous between different same-named sensors. The sensors are strongly typed, so in HWiNFO there is no confusion, but for now the PromDapter doesn't take the sensor type...