Querying events by "generated" fails due to lookup in traits
Bug #1514349 reported by
Christian Brinker
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Panko |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
When trying to query something like /v2/events?
Revision history for this message
| gordon chung (chungg) wrote | #1 |
| Changed in ceilometer: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Changed in ceilometer: | |
| assignee: | nobody → heha (zhanghanqun) |
Revision history for this message
| heha (zhanghanqun) wrote | #2 |
| Changed in ceilometer: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on ceilometer (master) | #3 |
| Changed in ceilometer: | |
| assignee: | heha (zhanghanqun) → Zi Lian Ji (jizilian) |
| affects: | ceilometer → panko |
| Changed in panko: | |
| assignee: | Zi Lian Ji (jizilian) → nobody |
| Changed in panko: | |
| status: | In Progress → Triaged |
To post a comment you must log in.
the current use case is to query against start_timestamp or end_timestamp. i'm ok with adding support for using generated keyword. that said, this might be a gap in documentation as well.
https:/