A lot of unneeded events/signals send when using autoscaling group
Bug #1445361 reported by
Marcin Zbik
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Angus Salkeld | ||
Kilo |
Fix Released
|
Medium
|
Angus Salkeld |
Bug Description
When using autoscaling group with alarms which have short check time, for example: check CPU usage every one minute Heat (Ceilometer?) generates huge amount of events (in horizon) like:
"alarm state changed from alarm to alarm (Remaining as alarm due to 1 samples outside threshold, most recent: 0.294406779661)"
What is more heat sends (AMQP) notification "Orchestration Event: Autoscaling end" every minute, like that information above.
All of this generates a lot of redundant, and really unnecessary data.
Changed in heat: | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
Changed in heat: | |
assignee: | nobody → Angus Salkeld (asalkeld) |
milestone: | none → liberty-1 |
tags: | added: kilo-backport-potential |
Changed in heat: | |
status: | Fix Committed → Fix Released |
tags: | removed: kilo-backport-potential |
Changed in heat: | |
milestone: | liberty-1 → 5.0.0 |
To post a comment you must log in.
Maybe you need to increase your cooldown? docs.openstack. org/developer/ heat/template_ guide/openstack .html#OS: :Heat:: ScalingPolicy
http://