![]() ![]() I do want to expose metrics via HTTPS, but it shouldn’t be my add-on’s job to do that. I’m running my Home Assistant instance in my homelab and it’s not exposed to the internet, so I’m comfortable disabling protection mode internally.Īs far as SSL, I’m going back and forth on that. I tried to enable it, but wasn’t getting all the metrics I needed. This is why protection mode needs to be disabled. Node exporter requires host-level access (since it’s running in a container) so that it can read CPU, memory, disk, etc… of the host. Please inspect the code of this add-on before you run Thanks, always open to feedback and help! As such, I have requested all possible permissions. The add-on needs to access to host-level metrics (CPU, memory, disk, etc…).Why does this add-on require so many permissions?.Yes, but that add-on is for Prometheus server, not the node exporter.Isn’t there already an Prometheus add-on?.Yes, but the official integration only exposes entity-related metrics, not host-related metrics.Doesn’t Home Assistant already have Prometheus integration?. ![]() The “Open Web UI” button doesn’t work when Home Assistant is behind a reverse proxy.The following Prometheus query should return data: node_uname_info To verify the metrics are available, visit in your browser, or use curl curl -X GET ConfigurationĪdd the following to the /etc/prometheus/prometheus.yml config file on your Prometheus server: scrape_configs:.Check the logs of the add-on to see if everything went well.Disable “Protection mode” in the add-on panel.Search for the “Prometheus Node Exporter” add-on in the Supervisor add-on store and install it.The Prometheus Node Exporter for hardware and OS metrics exposed by *NIX kernels. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |