We can let ironic out of this. I need to monitor a physical server ( hypervisor ) and when ceilometer agents push the metrics
to gnocchi, it is done without an unique resource_id, and this is because it is not using an IP/hostname as a resource_id.
For example , lets take this two metrics examples:
POST /v1/resource/generic/192.168.90.11.br-tun/metric/hardware.network.outgoing.bytes/measures
POST /v1/resource/generic/192.168.90.11.eth3/metric/hardware.network.outgoing.errors/measures
Here the resource ID is :
192.168.90.11.br-tun
192.168.90.11.eth3
But br-tun and eth3 are two network devices from the same resource ( hypervisor ), so the resource should be just 192.168.90.11
Lianhao,
We can let ironic out of this. I need to monitor a physical server ( hypervisor ) and when ceilometer agents push the metrics
to gnocchi, it is done without an unique resource_id, and this is because it is not using an IP/hostname as a resource_id.
For example , lets take this two metrics examples:
POST /v1/resource/ generic/ 192.168. 90.11.br- tun/metric/ hardware. network. outgoing. bytes/measures generic/ 192.168. 90.11.eth3/ metric/ hardware. network. outgoing. errors/ measures
POST /v1/resource/
Here the resource ID is :
192.168. 90.11.br- tun
192.168.90.11.eth3
But br-tun and eth3 are two network devices from the same resource ( hypervisor ), so the resource should be just 192.168.90.11
this make any sense to you ?