-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Netdata identifiers are not properly handled #14897
Comments
home-assistant/home-assistant.io#5528 contains details to get valid names for the elements to monitor. |
Is multiply element(s) supported?
|
|
No support for multiple elements at the moment. A PR would be welcome. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 |
Was change with #16656. |
Home Assistant release with the issue:
0.71
Operating environment (Hass.io/Docker/Windows/etc.):
all
Component/platform:
https://www.home-assistant.io/components/sensor.netdata/
Description of problem:
Multiple entries for the same resource will not work as they don't pass configuration validation.
There are some deviation in the naming of values in the frontend and the RESTful API. In the documentation is stated that the frontend should be used to determine the name of the
data_group
. E.g., forhddtemp
is the frontend usinghddtemp_local.disks_temp
and the APIhddtemp_local.temperatures
.This seems also be the case for network metrics.
InOctets
instead ofreceived
.It may happen at other places as well.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Additional information:
Initial report: https://community.home-assistant.io/t/netdata-configuration/55712
The text was updated successfully, but these errors were encountered: