| 2014-11-20 15:35:16 |
gordon chung |
description |
this is to discuss the value of certain 'meters'.
when having a quick look at measurements page we can see a bunch 'Existence of xyz' meters which don't actually measure anything.
for example:
instance
instance:<type>
network
subnet
port
router
ip.floating
image
volume
snapshot
<all keystone meters>
<all heat meters>
<all sahara meters>
switch
switch.port
network.services.lb.pool
network.services.lb.vip
network.services.member
network.services.health_monitor
<all VPNaaS meters>
<all FWaaS meters>
... probably a few others
tbh, i don't think these are meters and they only exists because the concept of events wasn't fully fleshed out. now that we support events in all backends, i think we should remove these 'meters' and make them events.
in most cases, this can be easily achieved as they are derived from real event notifications and we just need to add them to event definition file.... in some cases, they are polled so we need a way to translate them into events. |
this is to discuss the value of certain 'meters'.
when having a quick look at measurements page we can see a bunch 'Existence of xyz' meters which don't actually measure anything.
for example:
instance
instance:<type>
network
subnet
port
router
ip.floating
image
volume
snapshot
<all keystone meters>
<all heat meters>
<all sahara meters>
switch
switch.port
network.services.lb.pool
network.services.lb.vip
network.services.member
network.services.health_monitor
<all VPNaaS meters>
<all FWaaS meters>
... probably a few others
tbh, i don't think these are meters and they only exists because the concept of events wasn't fully fleshed out. now that we support events in all backends, i think we should remove these 'meters' and make them events as they aren't measuring anything. also, it's confusing users as Horizon for quite some time thought that the meter volume actually represented something useful.
in most cases, this can be easily achieved as they are derived from real event notifications and we just need to add them to event definition file.... in some cases, they are polled so we need a way to translate them into events. |
|
