| Summary: | export instance events - running events each minute obscure rest of events | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Dave Johnson <dajohnso> | ||||||
| Component: | aeolus-conductor | Assignee: | Angus Thomas <athomas> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | wes hayutin <whayutin> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.0.0 | CC: | akarol, clalance, dajohnso, deltacloud-maint, dgao, jprovazn, slinaber, ssachdev, whayutin | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-05-15 22:12:55 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 526497 [details]
instance details page screenshot
check out the scroll bar, pretty sure those are all running events
Yeah, you are right. This is because that every time dbomatic wakes up (every 60 seconds), it updates all instances. However, even if it doesn't have a "change", it still generates an event. Ian, can you take a look at this? Basically we need to check if the state and IP addresses are the same as they were last time, and if they are, don't generate an event. That should cut down the number of events generated dramatically. I think Matt fixed this in commit 030107026645c5f5209f5f53a5728006ff5d0e32 030107026645c5f5209f5f53a5728006ff5d0e32 is in aeolus-conductor-0.8.0-2.el6.src.rpm good 2 go with aeolus-conductor-0.8.0-20.el6.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0583.html |
Created attachment 526495 [details] csv file Description of problem: ================================== Saw this 'export events' button on the instances table and took a peek at the csv it produced. Immediately noticed that there was a ton of running events, one every 61 seconds which seems excessive. If you have multiple running instances, this csv grows very quickly. Just thinking that this would be more useful just tracking transition changes like when a instance changes from 'pending to running' or 'running to stopped'. Version-Release number of selected component (if applicable): ==================================================================== aeolus-all-0.4.0-0.20111003184622git65a7d19.fc15.noarch aeolus-conductor-0.4.0-0.20111003184622git65a7d19.fc15.noarch aeolus-conductor-daemons-0.4.0-0.20111003184622git65a7d19.fc15.noarch aeolus-conductor-doc-0.4.0-0.20111003184622git65a7d19.fc15.noarch aeolus-configure-2.0.2-4.20110930103205gitaf78594.fc15.noarch rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch Steps to Reproduce: ================================== 1. login 2. on the monitor tab, click the details view 3. start some instances 4. let them run for a short while 5. click on instances link 6. click on export events button