deprecate meters that are really events
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceilometer |
Fix Released
|
Wishlist
|
gordon chung | ||
Bug 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.
network.
network.
network.
<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.
| Liusheng (liusheng) wrote | #1 |
| Liusheng (liusheng) wrote | #2 |
| gordon chung (chungg) wrote | #3 |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to ceilometer (master) | #4 |
| Changed in ceilometer: | |
| assignee: | nobody → gordon chung (chungg) |
| status: | New → In Progress |
| OpenStack Infra (hudson-openstack) wrote | #5 |
| summary: |
- drop meters that are really events + deprecate meters that are really events |
| description: | updated |
| OpenStack Infra (hudson-openstack) wrote Fix merged to ceilometer (master) | #6 |
| OpenStack Infra (hudson-openstack) wrote | #7 |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to ceilometer (master) | #8 |
| OpenStack Infra (hudson-openstack) wrote | #9 |
| Lianhao Lu (lianhao-lu) wrote | #10 |
| OpenStack Infra (hudson-openstack) wrote Fix merged to ceilometer (master) | #11 |
| OpenStack Infra (hudson-openstack) wrote | #12 |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to ceilometer (master) | #13 |
| Changed in ceilometer: | |
| importance: | Medium → Wishlist |
| OpenStack Infra (hudson-openstack) wrote Fix merged to ceilometer (master) | #14 |
| gordon chung (chungg) wrote | #15 |
| Changed in ceilometer: | |
| status: | In Progress → Fix Committed |
| Changed in ceilometer: | |
| milestone: | none → liberty-rc1 |
| Changed in ceilometer: | |
| status: | Fix Committed → Fix Released |
| Changed in ceilometer: | |
| milestone: | liberty-rc1 → 5.0.0 |
Hi gordon chung, thanks for this report, is there any discussion about this issue? or do you have any plan to drom this meters (maybe need a blueprint )? if this is approved, what the scope of meter should be droped? (most meters from notification-agent are really events). I agree with you, actually there is a known bug that the *instance* meter from notification you mentioned above will affect the *instance* samples from polling agent, that may will affect alarm (created by users) base on the number of instance. maybe the bug 1383751 and bug 1386178 will should be marked "invalid" :)