kolla-ansible should configure event expiration in panko by default
Bug #1843113 reported by
Xing Zhang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
In Progress
|
Wishlist
|
Chason Chan | ||
Bug Description
similar to https:/
The openstack telemetry documentations suggests setting a time-to-live on collected events to avoid unbounded growth of the database, but a default kolla-ansible install does not, at this time, have any time-to-live configured.
We should:
(a) configure event_time_to_live to something other than -1 by default.
(b) allow a deployer to configure event_time_to_live via parameters
(c) configure a periodic panko-expirer cron job (should frequency of this job be configurable separately from the TTL?)
| Changed in kolla-ansible: | |
| status: | New → Triaged |
| assignee: | nobody → Chason Chan (chen-xing) |
| Changed in kolla-ansible: | |
| importance: | Undecided → Wishlist |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to kolla-ansible (master) | #1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/