Search results

  1. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    I understand what you mean. Lifetime is kind of artificial "promise" - rather than solid guarantee that can be dependent on. I on the other hand dislike it, because there is no guarantee for it. There is much less motivation to support lifetime upgraders, when thinking of the future, than...
  2. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    I can understand what you possibly mean, but I want to clarify certain aspect. O365 is a subscription, you cannot use it without having active subscription. HWiNFO "subscription" is actual active upgrade-maintenance plan. It's common on all kinds of "updating required software", many use 40-50%...
  3. K

    IMPORTANT CHANGES TO HWiNFO64 COMING SOON

    Maintenance cost is if you want upgrades. Pretty standard procedure; the terms you use 1 year license and ransomware would indicate that the software would be "turned off" if you didn't renew the license. Either there's a misunderstanding somewhere or we have different opinions of standard...
  4. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    The latest version has host-attribute within that can possibly be used to this. I haven't done it myself (yet), but there should be way to filter based on it. If that seems to work, I could add manual fixed categories, that you could configure on each machine, so that your server(s) and...
  5. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    I registered my v7.0 Pro - can confirm it works without any changes with the setting enabled.
  6. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    Did you also enable the Shared Memory from the options? As its currently disabled by default, it could explain the error for "not finding memory mapped file".
  7. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    I am not aware if there are any changes in the actual memory layout. I haven't personally upgraded to 7.0 yet - figuring out the proper licensing model first as I'm getting it for Corporate use myself. Fast/easy way to test is to see, if the 7.0 is functional as-is when the Shared Memory is...
  8. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    Just for the quick heads up. As of the changes with HWiNFO's licensing model, PromDapter will require the Pro version to stay functional. I personally support the change. PromDapter will remain free add-on, and we also get the benefit of being able to open the whole source stack now, thanks for...
  9. K

    IMPORTANT CHANGES TO HWiNFO64 COMING SOON

    As the author of PromDapter I'd like to drop my line about this change. I support the stance taken here - as a whole, including the pricing. I don't have strong opinion on pricing, its not my business - but the magnitude seems to be on level field for alike tools. I understand (and can hereby...
  10. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    I added now the "host" attribute in the latest release. If you could check it out and report back if it's working, I'd appreciate :-). https://github.com/kallex/PromDapter/releases/tag/v0.9.18-beta
  11. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    I wish I had my newest one, but I need to recreate it. I'm running Grafana on Kubernetes and... my Prometheus has its persistent volume set, but I learned the hard way that my Grafana didn't. I'll post it back one I manage to recreate it; it's based on the example though, but with some...
  12. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    I agree that the hostname is kind of mandatory to be honest. I try to activate on PromDapter in coming week and see if I can get those few quite small but big improvements done :-).
  13. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    There is "instance" attribute by default Prometheus that is IP address and port or computer name; depending how you have your Prometheus scrapers configured. I should add the attribute "host" in the list, so that could be used. You can check out how "instance" serves you; the notation is...
  14. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    Oh I am over halfway of adding WMI data to PromDapter too, just got occupied elsewhere a bit - so its been "delayed" for now. I wanted it myself for monitoring process specific stuff (what's hogging RAM etc). What are you looking to get from WMI specifically?
  15. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    Yes that seems correct; did you add that one yourself? I didn't see it in mine, but my CPU has the sensor bit different named. So it should already appear in exporter; that is in the list: http://localhost:10445/metrics So it's working as you wanted now, hopefully..? :)
  16. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    It should be just a matter of proper regexp pattern on C:\ProgramData\PromDapter\Prometheusmapping.yaml If you post the exact name of the sensor in HWiNFO, I can help you modify the regexp pattern to match it.
  17. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    You also need to install Prometheus; that's the missing piece in your puzzle. PromDapter is servicing data to Prometheus scrapers; so that the data gets stored in Prometheus database. Then Grafana connects the Prometheus normally and can use the data. PromDapter is short for "Prometheus...
  18. K

    REALLY LOW GPU VRM VOTLAGE IN (VIN/+12V)

    How old is that Power Supply? And is there instability, or sensor value based concern? EDIT: Also how about other V12 rail voltages, not only on GPU?
  19. K

    RX570 HIGH AMPERES

    I just woke up from naps, but I don't spot the "extremely high amperate" and "really low GPU VRM Voltage VIN +12V". EDIT: Ok I read your other post and realized the voltage is addressed there. If you mean GPU Core Voltage, that is supposed to be at that ~1.1v-1.2v ballpark. Which means that...
  20. K

    Prometheus Adapter for HWiNFO (+ Grafana Dashboard)

    No I didn't take you wrong, no worries. The regexs are pain in the ass also. I think you can go by "best of the both worlds"; I think they default regexps provided should already give you all the CPU parts OK. You can try to keep the "catch-all" as last line (before aggregated values)... or...
Back
Top