@Maximiliano, I think having only the host ip as resource_id would causing some problems, think of the following scenario:
for the same metric hardware.network.outgoing.bytes from the same machine 192.168.90.11, first gnocchi gets the measure for eth3 of the value 1000, later gnocchi gets another measure for br-tun of the value 2000. These are two different measures for different network interface on the same machine 192.168.90.11. If we have 192.168.90.11 as the resource_id for both of them, then we can't differentiate them.
@Alejandro, thanks for the info. Will look into that
@Maximiliano, I think having only the host ip as resource_id would causing some problems, think of the following scenario:
for the same metric hardware. network. outgoing. bytes from the same machine 192.168.90.11, first gnocchi gets the measure for eth3 of the value 1000, later gnocchi gets another measure for br-tun of the value 2000. These are two different measures for different network interface on the same machine 192.168.90.11. If we have 192.168.90.11 as the resource_id for both of them, then we can't differentiate them.
@Alejandro, thanks for the info. Will look into that