Zenoss QA Test Day December 10 UPDATED
8:48:58 AM bbibeault1: Morning everyone.
8:56:15 AM wquesada: Morning
9:01:05 AM cumanzor: Good morning
9:24:26 AM wquesada: Hey ke4qqq ...
9:24:26 AM wquesada: Do you have any experience that would like to share regarding the Event Console ?
9:29:57 AM bbibeault1: All - I am bringing up another installation of 2.5.1 for testing.
9:30:37 AM bbibeault1: message/43102;jsessionid=AD705A62A8AB7E1B8D54C32FD8EC2AFF.node0#43102 (jcurry) message/43102
9:32:48 AM bbibeault1: And for anyone that wants to follow the forum post defining some of the items we will be reviewing - message/43204
9:43:54 AM bbibeault1: Welcome.
9:43:57 AM ckrough: Hello
9:45:46 AM wquesada: hi there ..
9:56:57 AM bbibeault1: Hello Jane.
9:57:44 AM Jane_Curry: Hi there - need to monitor this and standard IRC channel for next hour so please bear with me....
9:59:44 AM bbibeault1: That is fine, I appreciate the participation.
10:01:01 AM bbibeault1: Welcome!
10:01:10 AM rmatte:
10:01:38 AM bbibeault1: Due to some destructive testing I am bringing up a fresh 2.5.1 installation for testing.
10:01:52 AM rmatte: I've already got one running, so I'm good
10:02:51 AM rmatte: now is this purely performance related or can we point out missing features?
10:02:55 AM mrayzenoss: yes
10:03:00 AM mrayzenoss:
10:03:08 AM rmatte: yes to which
10:03:10 AM bbibeault1: Everything around the event console, please.
10:03:11 AM rmatte:
10:03:15 AM cumanzor: I have fresh 2.5.1 ready on a RHEL 5.4 machine
10:03:26 AM rmatte: bbibeault1: right, that's what I meant
10:03:41 AM mrayzenoss: so we're looking for things not covered by current test plans and for issues not covered by tickets yet
10:03:44 AM bbibeault1: Also, I am going to do some freshening and updating of the test cases around the Event Console, if anyone would like to follow along and/or offer feedback.
10:03:49 AM bbibeault1: http://dev.zenoss.com/testlink/index.php
10:03:50 AM mrayzenoss: so let's open new test cases and new tickets
10:03:52 AM rmatte: bbibeault1: first thing, which I've pointed out a few times, when you go to Event History, there is no quick way to specify a range of dates to view history for
10:04:25 AM bbibeault1: 1s
10:04:38 AM rmatte: k
10:04:51 AM mrayzenoss: rmatte: http://dev.zenoss.org/trac/ticket/5659
10:05:21 AM rmatte: mrayzenoss: k, just wanted to make sure it wasn't forgotten
10:05:29 AM rmatte: I forgot about that trac ticket
10:05:51 AM zenethian:
10:06:09 AM rmatte:
10:09:09 AM rmatte: a couple other cosmetic things... when you double click on an event, to the right to the big event severity icon in the top left of the events details window, there is this ">" graphic. It looks pixelated like it was created smaller but stretched to be larger. Aesthetically, it really takes away from the whole new smooth look of the event console.
10:09:44 AM rmatte: In the event details window, when a trap is received, the trap's details, which were previously stored under their own details tab, are now mashed together with all of the other info for the event
10:10:27 AM mrayzenoss: hmmm… my alpha VM game me a server connection error the first time I went to the event console
10:10:33 AM rmatte: It would be nice if there were a second link such as the "Show more details..." link which expands to reveal the details, but only reveals the details for traps
10:10:52 AM bbibeault1: There are some known issues with the alpha, but I wasn't aware of the server connection error.
10:11:13 AM bbibeault1: rmatte, are any of these in Trac already? If not, I'll get entering.
10:11:37 AM rmatte: bbibeault1: I'll have to search around and see, but I doubt it
10:11:46 AM rmatte: bbibeault1: I think they were only mentioned on the forums thus far
10:11:51 AM bbibeault1: I will start searching on those, keep the feedback coming.
10:11:55 AM rmatte: thanks
10:13:16 AM rmatte: oh, another stupid cosmetic issue, but which also takes away from the overall look of the console is the filter list at the top. It doesn't fully expand to the width of the event console, it leaves a fairly large gap at the right-hand edge (This is in Firefox, I haven't checked with IE)
10:13:56 AM rmatte: There also used to be an option to toggle the filters on or off, which appears to have vanished, but I found it was a nice feature
10:15:09 AM mrayzenoss: bbibeault1: here's the gap he mentioned http://imagebin.org/74922
10:15:35 AM bbibeault1: On my machine, that gap is just the width of the scroll bar for the events themselves.
10:15:51 AM mrayzenoss: well I've got no events, so all I have is a gap
10:15:59 AM rmatte: oh, I guess it's because the scrollbar doesn't show up until you have events flooding off the screen
10:16:10 AM bbibeault1: Ahh, but we always leave the space there.
10:16:12 AM rmatte: it should really auto-expand when the scrollbar appears in my opinion
10:16:22 AM rmatte: just looks cleaner
10:16:27 AM mrayzenoss: which log should have the "Server connection error"?
10:16:39 AM rmatte: mrayzenoss: I'd imagine zenhub
10:17:17 AM mrayzenoss: hm… nothing there and nothing in z2.log
10:17:23 AM rmatte: hmmm
10:17:35 AM rmatte: well, Z2 is just web request log as far as I can tell
10:19:31 AM rmatte: oh, check zeo.log
10:19:39 AM mrayzenoss: found this in my event.log http://pastebin.org/63140
10:19:41 AM rmatte: actually, that might just be zope related
10:19:59 AM rmatte: ah, my event.log files are all clean
10:20:28 AM bbibeault1: rmatte: http://dev.zenoss.org/trac/ticket/5917
10:20:46 AM rmatte: thanks
10:23:37 AM bbibeault1: rmatte: For the option on toggling filters on or off, you mean rendering of the filters themselves, or all filtering in ttal?
10:23:40 AM bbibeault1: total?
10:23:51 AM rmatte: it would just make the filter bar dissapear
10:24:01 AM bbibeault1: ok
10:24:06 AM rmatte: there was an option for it in 2.5
10:24:10 AM rmatte: but it dissapeared
10:24:18 AM bbibeault1: In 2.5? It disappeared between 2.5 and 2.5.1?
10:24:21 AM rmatte: or it might have actually been as far back as one of the betas
10:24:32 AM rmatte: I don't recall exactly when it dissapeared
10:25:01 AM cumanzor: to mrayzenoss: about that gap http://imagebin.org/74922, gap width is 19px and it's consistent on all browsers
10:25:21 AM rmatte: yup
10:25:31 AM rmatte: I like the little frowny face
10:25:33 AM rmatte:
10:29:34 AM bbibeault1: rmatte: http://dev.zenoss.org/trac/ticket/5918 (ticket regarding the hiding of the filters)
10:31:34 AM rmatte: cool
10:34:40 AM bbibeault1: rmatte: With viewing the event history by a date range, doesn't setting "First Seen" and "Last Seen" get you the filter you want?
10:35:12 AM rmatte: bbibeault1: no, doing that will only show you events with a start and end date that specifically matches what you set
10:35:23 AM rmatte: bbibeault1: instead of an actual range
10:35:32 AM bbibeault1: o.O
10:35:46 AM bbibeault1: 1m testing on a trunk system...
10:36:19 AM rmatte: I haven't tried in a while, maybe they did change the behaviour of it, I'll check...
10:36:49 AM rmatte: I have events from 2009-12-08 to 2009-11-03, so if I set that range I should still see all of the events...
10:37:16 AM rmatte: I said the dates backwards, but you get the idea
10:37:17 AM rmatte: lol
10:37:35 AM bbibeault1: I just saw something odd around this, myself.
10:38:01 AM rmatte: ah, it looks like it does actually work now
10:38:17 AM rmatte: but I'm still not sure if it's really perfect
10:38:23 AM bbibeault1: I get events in the middle, but on my test system I start with more events, and when I filter I get a smaller subset.
10:38:34 AM bbibeault1: Trying to figure out the root cause here.
10:38:34 AM rmatte: if I set the last seen as 2009-12-08 the event for that date dissapears
10:38:40 AM rmatte: but if I set it to 2009-12-09 it appears
10:39:01 AM mrayzenoss: I get this stack trace everytime I hit the event console on the alpha build: http://pastebin.org/63148
10:39:07 AM bbibeault1: Note the default time is 00:00:00
10:39:09 AM rmatte: k cool, definitely need to get that right since that's an important tool
10:39:28 AM rmatte: right, but there's no option to set time in the calendar
10:39:38 AM rmatte: lol
10:40:00 AM rmatte: I suppose you could type it in, but that seems unnecessarily tedious
10:41:35 AM rmatte: OOOOH, I just remember something else I had noticed
10:41:57 AM rmatte: click on one of the fields at the top to sort a row, then click on it again, the filter bar turns all gray (input fields vanish)
10:42:17 AM rmatte: hmmmm
10:42:28 AM rmatte: it's not doing it now, I think fields need to actually be populated for it to happen
10:42:33 AM rmatte: let me work out how to reproduce it
10:42:45 AM rmatte: yeh, that's it
10:42:52 AM rmatte: populate the first time and last time fields
10:42:58 AM rmatte: then click on "Summary" at the top to sort
10:43:01 AM rmatte: then click on it again
10:43:08 AM rmatte: all of the input fields on the filter bar vanish
10:43:26 AM bbibeault1: rmatte: I'm getting overloaded researching and typing these in. Can you document that one in trick please?
10:43:37 AM rmatte: yup
10:43:52 AM bbibeault1: trac, that is. Also, getting some good feedback on the time/date seen issue.
10:45:31 AM Alvaro1: i think that the default time for the Last Seen field should be 23:59
10:45:52 AM rmatte: Components: Events and Alerts?
10:45:59 AM rmatte: in Trac
10:46:07 AM bbibeault1: Yes please. 1 favor, please add a keyword of "testday".
10:46:18 AM rmatte: done
10:46:24 AM bbibeault1: Just trying to keep track of what comes out of this, thanks.
10:47:15 AM rmatte: bbibeault1: http://dev.zenoss.org/trac/ticket/5920
10:47:22 AM mrayzenoss: bbibeault1: just added http://dev.zenoss.org/trac/ticket/5919
10:47:42 AM bbibeault1: Thanks guys
10:48:24 AM rmatte: bbibeault1: did you log one for the pixelated image?
10:49:00 AM bbibeault1: Not yet, still getting through the first seen last seen.
10:49:16 AM rmatte: k cool
10:49:18 AM bbibeault1: http://dev.zenoss.org/trac/ticket/5921 on times being rendered in the first place (not supposed to be there)
10:49:27 AM bbibeault1: Still working on the filtering on date.
10:49:28 AM rmatte: yeh
10:50:08 AM rmatte: Ian shall have his work cut out for him
10:50:09 AM rmatte:
10:50:24 AM bbibeault1: As will QA (more test cases needed)
10:50:33 AM rmatte: yup
10:56:26 AM rmatte: seeing if I can find any other strange behaviour...
10:56:38 AM rmatte: *points at zenethian *
10:56:40 AM rmatte: there's some
10:57:02 AM bbibeault1: I am not having much luck figuring out these start and end dates for events.
10:57:16 AM bbibeault1: The behavior I see isn't matching up, sometimes I get a superset of events, sometimes a subset, it seems.
10:57:29 AM rmatte: yup
10:57:33 AM rmatte: it's quite wonky
10:58:00 AM bbibeault1: Well if we can figure out the nature on the wonky-ness, the change of fixing it goes up 5%.
10:58:09 AM rmatte: yup
11:08:47 AM bbibeault1: Still digging on this event filtering by first seen/last seen.
11:10:31 AM mrayzenoss: I'm rebuilding a 2.5.1 box to test some of the ZenUser event console issues
11:29:13 AM bbibeault1: http://dev.zenoss.org/trac/ticket/5921 updated; still trying to figure out what is going on here.
11:34:29 AM cumanzor: Be careful when you set both First seen and last Seen filter using the today button, both dates will have the hour as 00:00:00, no events will be displayed because of that
11:38:07 AM bbibeault1: http://dev.zenoss.org/trac/ticket/5922 - Error with display count of displayed tickets
11:42:46 AM bbibeault1: http://dev.zenoss.org/trac/ticket/5923 - Empty row at bottom of event console (throws off the DISPLAYING count)
11:43:39 AM bbibeault1: Welcome
12:11:40 PM wquesada: created :http://dev.zenoss.org/trac/ticket/5924
12:19:24 PM bbibeault1: http://dev.zenoss.org/trac/ticket/5925 - Event history does not have export as XML option
12:19:44 PM bbibeault1: Note : Test cases are being created as we go through the event console, as well. Anyone can contribute if they have some time.
12:20:36 PM bbibeault1: Matt, how is your 2.5.1 machine that we were going to use to discuss message/43102 coming along?
12:21:41 PM mrayzenoss: heh, sitting on the new install wizard
12:33:44 PM rmatte: hehe
12:33:55 PM mrayzenoss: logged in as the readonly Zenuser account and sent all the events to history... fudge
12:34:27 PM mrayzenoss: from the Event History: 009/12/10 03:53:53.000 readonly said:
Deleted by user
12:45:38 PM rmatte: that's extremely useful
12:45:39 PM rmatte: lol
1:04:05 PM Jane_Curry: I bet you can undelete it too - for another logged comment by user!
1:18:27 PM bbibeault1: Feedback from #zenoss:
1:19:45 PM bbibeault1: cain22 ok, not sure if i'm loving the new event viewer
1:19:45 PM bbibeault1: RoundQube cain22 what are you issues with it?
1:19:46 PM bbibeault1: cain22 well, it took me second to realize how to open up the event in detail....
1:19:50 PM bbibeault1: daveborg98 That took me a minute as well.
1:19:54 PM bbibeault1: cain22 and maybe its jsut me, but since its smaller font, it alot of the info seems to blend in, making it harder to recongize events at a glance
1:19:59 PM bbibeault1: mrayzenoss cain22: Configure->Show severity row colors
1:20:03 PM bbibeault1: cain22 i did. colors makes it easier...but font size is what i was refering to...
1:20:07 PM bbibeault1: daveborg98 I personally like it. I am at 1680x1050 res. and I can see a lot of the event details on that screen. It does make it a little more difficult on my 1920x1200 screen though.
1:26:57 PM mrayzenoss: Jane_Curry: http://dev.zenoss.org/trac/ticket/5926
2:11:10 PM bbibeault1: Performing a defect review now.
3:30:34 PM bbibeault1: A few new tickets have been added, and right now a few of us are updating some of the Event Console test cases.
3:30:46 PM bbibeault1: Any other community feedback? Issues or questions that you have had?
3:34:46 PM Alvaro2: I included this defect about the horizontal scrollbar. http://dev.zenoss.com/trac/ticket/5927
4:02:24 PM bbibeault1: Note : I am adding test cases around the Event Fields (admin guide, section 7.1.x)
4:03:02 PM bbibeault1: TC created - javascript:ET(3107)javascript:ET(3107)
4:03:07 PM cumanzor: Adding a few testcases about event manager options that affect the event console
4:14:47 PM bbibeault1: TC created - javascript:ET(3109)javascript:ET(3109)
4:21:46 PM bbibeault1: TC created - javascript:ET(3111)javascript:ET(3111)
4:32:28 PM Fuzzy_T: 2009-12-10 16:31:45,171 WARNING zen.zenmib: Unable to find a file providing the OID RFC1215
4:34:13 PM cumanzor: new testcase added (3115)
4:34:24 PM bbibeault1: Fuzzy, where did that message come from?
4:38:03 PM cumanzor: Fuzzy_T, which MIB are you currently using?
4:38:45 PM Fuzzy_T: nevermind
4:53:26 PM bbibeault1: Guys I am going to sign off, I think that overall this was a productive day, got a good number of defects in, and a few test cases created, as well!
4:54:56 PM mrayzenoss: Thanks guys, I'll grab a transcript of today and post it on the Community IRC page
mrayzenoss has changed the topic to: Help Improve Zenoss' Testing: community/testing (4:55:22 PM)
mrayzenoss has changed the topic to: Zenoss QA Test Day: Event Console Testing: http://tr.im/zenoss_qa (7:58:35 AM)
8:48:58 AM bbibeault1: Morning everyone.
8:56:15 AM wquesada: Morning
9:01:05 AM cumanzor: Good morning
9:24:26 AM wquesada: Hey ke4qqq ...
9:24:26 AM wquesada: Do you have any experience that would like to share regarding the Event Console ?
9:29:57 AM bbibeault1: All - I am bringing up another installation of 2.5.1 for testing.
9:30:37 AM bbibeault1: message/43102;jsessionid=AD705A62A8AB7E1B8D54C32FD8EC2AFF.node0#43102 (jcurry) message/43102
9:32:48 AM bbibeault1: And for anyone that wants to follow the forum post defining some of the items we will be reviewing - message/43204
9:43:54 AM bbibeault1: Welcome.
9:43:57 AM ckrough: Hello
9:45:46 AM wquesada: hi there ..
9:56:57 AM bbibeault1: Hello Jane.
9:57:44 AM Jane_Curry: Hi there - need to monitor this and standard IRC channel for next hour so please bear with me....
9:59:44 AM bbibeault1: That is fine, I appreciate the participation.
10:01:01 AM bbibeault1: Welcome!
10:01:10 AM rmatte:
10:01:38 AM bbibeault1: Due to some destructive testing I am bringing up a fresh 2.5.1 installation for testing.
10:01:52 AM rmatte: I've already got one running, so I'm good
10:02:51 AM rmatte: now is this purely performance related or can we point out missing features?
10:02:55 AM mrayzenoss: yes
10:03:00 AM mrayzenoss:
10:03:08 AM rmatte: yes to which
10:03:10 AM bbibeault1: Everything around the event console, please.
10:03:11 AM rmatte:
10:03:15 AM cumanzor: I have fresh 2.5.1 ready on a RHEL 5.4 machine
10:03:26 AM rmatte: bbibeault1: right, that's what I meant
10:03:41 AM mrayzenoss: so we're looking for things not covered by current test plans and for issues not covered by tickets yet
10:03:44 AM bbibeault1: Also, I am going to do some freshening and updating of the test cases around the Event Console, if anyone would like to follow along and/or offer feedback.
10:03:49 AM bbibeault1: http://dev.zenoss.com/testlink/index.php
10:03:50 AM mrayzenoss: so let's open new test cases and new tickets
10:03:52 AM rmatte: bbibeault1: first thing, which I've pointed out a few times, when you go to Event History, there is no quick way to specify a range of dates to view history for
10:04:25 AM bbibeault1: 1s
10:04:38 AM rmatte: k
10:04:51 AM mrayzenoss: rmatte: http://dev.zenoss.org/trac/ticket/5659
10:05:21 AM rmatte: mrayzenoss: k, just wanted to make sure it wasn't forgotten
10:05:29 AM rmatte: I forgot about that trac ticket
10:05:51 AM zenethian:
10:06:09 AM rmatte:
10:09:09 AM rmatte: a couple other cosmetic things... when you double click on an event, to the right to the big event severity icon in the top left of the events details window, there is this ">" graphic. It looks pixelated like it was created smaller but stretched to be larger. Aesthetically, it really takes away from the whole new smooth look of the event console.
10:09:44 AM rmatte: In the event details window, when a trap is received, the trap's details, which were previously stored under their own details tab, are now mashed together with all of the other info for the event
10:10:27 AM mrayzenoss: hmmm… my alpha VM game me a server connection error the first time I went to the event console
10:10:33 AM rmatte: It would be nice if there were a second link such as the "Show more details..." link which expands to reveal the details, but only reveals the details for traps
10:10:52 AM bbibeault1: There are some known issues with the alpha, but I wasn't aware of the server connection error.
10:11:13 AM bbibeault1: rmatte, are any of these in Trac already? If not, I'll get entering.
10:11:37 AM rmatte: bbibeault1: I'll have to search around and see, but I doubt it
10:11:46 AM rmatte: bbibeault1: I think they were only mentioned on the forums thus far
10:11:51 AM bbibeault1: I will start searching on those, keep the feedback coming.
10:11:55 AM rmatte: thanks
10:13:16 AM rmatte: oh, another stupid cosmetic issue, but which also takes away from the overall look of the console is the filter list at the top. It doesn't fully expand to the width of the event console, it leaves a fairly large gap at the right-hand edge (This is in Firefox, I haven't checked with IE)
10:13:56 AM rmatte: There also used to be an option to toggle the filters on or off, which appears to have vanished, but I found it was a nice feature
10:15:09 AM mrayzenoss: bbibeault1: here's the gap he mentioned http://imagebin.org/74922
10:15:35 AM bbibeault1: On my machine, that gap is just the width of the scroll bar for the events themselves.
10:15:51 AM mrayzenoss: well I've got no events, so all I have is a gap
10:15:59 AM rmatte: oh, I guess it's because the scrollbar doesn't show up until you have events flooding off the screen
10:16:10 AM bbibeault1: Ahh, but we always leave the space there.
10:16:12 AM rmatte: it should really auto-expand when the scrollbar appears in my opinion
10:16:22 AM rmatte: just looks cleaner
10:16:27 AM mrayzenoss: which log should have the "Server connection error"?
10:16:39 AM rmatte: mrayzenoss: I'd imagine zenhub
10:17:17 AM mrayzenoss: hm… nothing there and nothing in z2.log
10:17:23 AM rmatte: hmmm
10:17:35 AM rmatte: well, Z2 is just web request log as far as I can tell
10:19:31 AM rmatte: oh, check zeo.log
10:19:39 AM mrayzenoss: found this in my event.log http://pastebin.org/63140
10:19:41 AM rmatte: actually, that might just be zope related
10:19:59 AM rmatte: ah, my event.log files are all clean
10:20:28 AM bbibeault1: rmatte: http://dev.zenoss.org/trac/ticket/5917
10:20:46 AM rmatte: thanks
10:23:37 AM bbibeault1: rmatte: For the option on toggling filters on or off, you mean rendering of the filters themselves, or all filtering in ttal?
10:23:40 AM bbibeault1: total?
10:23:51 AM rmatte: it would just make the filter bar dissapear
10:24:01 AM bbibeault1: ok
10:24:06 AM rmatte: there was an option for it in 2.5
10:24:10 AM rmatte: but it dissapeared
10:24:18 AM bbibeault1: In 2.5? It disappeared between 2.5 and 2.5.1?
10:24:21 AM rmatte: or it might have actually been as far back as one of the betas
10:24:32 AM rmatte: I don't recall exactly when it dissapeared
10:25:01 AM cumanzor: to mrayzenoss: about that gap http://imagebin.org/74922, gap width is 19px and it's consistent on all browsers
10:25:21 AM rmatte: yup
10:25:31 AM rmatte: I like the little frowny face
10:25:33 AM rmatte:
10:29:34 AM bbibeault1: rmatte: http://dev.zenoss.org/trac/ticket/5918 (ticket regarding the hiding of the filters)
10:31:34 AM rmatte: cool
10:34:40 AM bbibeault1: rmatte: With viewing the event history by a date range, doesn't setting "First Seen" and "Last Seen" get you the filter you want?
10:35:12 AM rmatte: bbibeault1: no, doing that will only show you events with a start and end date that specifically matches what you set
10:35:23 AM rmatte: bbibeault1: instead of an actual range
10:35:32 AM bbibeault1: o.O
10:35:46 AM bbibeault1: 1m testing on a trunk system...
10:36:19 AM rmatte: I haven't tried in a while, maybe they did change the behaviour of it, I'll check...
10:36:49 AM rmatte: I have events from 2009-12-08 to 2009-11-03, so if I set that range I should still see all of the events...
10:37:16 AM rmatte: I said the dates backwards, but you get the idea
10:37:17 AM rmatte: lol
10:37:35 AM bbibeault1: I just saw something odd around this, myself.
10:38:01 AM rmatte: ah, it looks like it does actually work now
10:38:17 AM rmatte: but I'm still not sure if it's really perfect
10:38:23 AM bbibeault1: I get events in the middle, but on my test system I start with more events, and when I filter I get a smaller subset.
10:38:34 AM bbibeault1: Trying to figure out the root cause here.
10:38:34 AM rmatte: if I set the last seen as 2009-12-08 the event for that date dissapears
10:38:40 AM rmatte: but if I set it to 2009-12-09 it appears
10:39:01 AM mrayzenoss: I get this stack trace everytime I hit the event console on the alpha build: http://pastebin.org/63148
10:39:07 AM bbibeault1: Note the default time is 00:00:00
10:39:09 AM rmatte: k cool, definitely need to get that right since that's an important tool
10:39:28 AM rmatte: right, but there's no option to set time in the calendar
10:39:38 AM rmatte: lol
10:40:00 AM rmatte: I suppose you could type it in, but that seems unnecessarily tedious
10:41:35 AM rmatte: OOOOH, I just remember something else I had noticed
10:41:57 AM rmatte: click on one of the fields at the top to sort a row, then click on it again, the filter bar turns all gray (input fields vanish)
10:42:17 AM rmatte: hmmmm
10:42:28 AM rmatte: it's not doing it now, I think fields need to actually be populated for it to happen
10:42:33 AM rmatte: let me work out how to reproduce it
10:42:45 AM rmatte: yeh, that's it
10:42:52 AM rmatte: populate the first time and last time fields
10:42:58 AM rmatte: then click on "Summary" at the top to sort
10:43:01 AM rmatte: then click on it again
10:43:08 AM rmatte: all of the input fields on the filter bar vanish
10:43:26 AM bbibeault1: rmatte: I'm getting overloaded researching and typing these in. Can you document that one in trick please?
10:43:37 AM rmatte: yup
10:43:52 AM bbibeault1: trac, that is. Also, getting some good feedback on the time/date seen issue.
10:45:31 AM Alvaro1: i think that the default time for the Last Seen field should be 23:59
10:45:52 AM rmatte: Components: Events and Alerts?
10:45:59 AM rmatte: in Trac
10:46:07 AM bbibeault1: Yes please. 1 favor, please add a keyword of "testday".
10:46:18 AM rmatte: done
10:46:24 AM bbibeault1: Just trying to keep track of what comes out of this, thanks.
10:47:15 AM rmatte: bbibeault1: http://dev.zenoss.org/trac/ticket/5920
10:47:22 AM mrayzenoss: bbibeault1: just added http://dev.zenoss.org/trac/ticket/5919
10:47:42 AM bbibeault1: Thanks guys
10:48:24 AM rmatte: bbibeault1: did you log one for the pixelated image?
10:49:00 AM bbibeault1: Not yet, still getting through the first seen last seen.
10:49:16 AM rmatte: k cool
10:49:18 AM bbibeault1: http://dev.zenoss.org/trac/ticket/5921 on times being rendered in the first place (not supposed to be there)
10:49:27 AM bbibeault1: Still working on the filtering on date.
10:49:28 AM rmatte: yeh
10:50:08 AM rmatte: Ian shall have his work cut out for him
10:50:09 AM rmatte:
10:50:24 AM bbibeault1: As will QA (more test cases needed)
10:50:33 AM rmatte: yup
10:56:26 AM rmatte: seeing if I can find any other strange behaviour...
10:56:38 AM rmatte: *points at zenethian *
10:56:40 AM rmatte: there's some
10:57:02 AM bbibeault1: I am not having much luck figuring out these start and end dates for events.
10:57:16 AM bbibeault1: The behavior I see isn't matching up, sometimes I get a superset of events, sometimes a subset, it seems.
10:57:29 AM rmatte: yup
10:57:33 AM rmatte: it's quite wonky
10:58:00 AM bbibeault1: Well if we can figure out the nature on the wonky-ness, the change of fixing it goes up 5%.
10:58:09 AM rmatte: yup
11:08:47 AM bbibeault1: Still digging on this event filtering by first seen/last seen.
11:10:31 AM mrayzenoss: I'm rebuilding a 2.5.1 box to test some of the ZenUser event console issues
11:29:13 AM bbibeault1: http://dev.zenoss.org/trac/ticket/5921 updated; still trying to figure out what is going on here.
11:34:29 AM cumanzor: Be careful when you set both First seen and last Seen filter using the today button, both dates will have the hour as 00:00:00, no events will be displayed because of that
11:38:07 AM bbibeault1: http://dev.zenoss.org/trac/ticket/5922 - Error with display count of displayed tickets
11:42:46 AM bbibeault1: http://dev.zenoss.org/trac/ticket/5923 - Empty row at bottom of event console (throws off the DISPLAYING count)
11:43:39 AM bbibeault1: Welcome
12:11:40 PM wquesada: created :http://dev.zenoss.org/trac/ticket/5924
12:19:24 PM bbibeault1: http://dev.zenoss.org/trac/ticket/5925 - Event history does not have export as XML option
12:19:44 PM bbibeault1: Note : Test cases are being created as we go through the event console, as well. Anyone can contribute if they have some time.
12:20:36 PM bbibeault1: Matt, how is your 2.5.1 machine that we were going to use to discuss message/43102 coming along?
12:21:41 PM mrayzenoss: heh, sitting on the new install wizard
12:33:44 PM rmatte: hehe
12:33:55 PM mrayzenoss: logged in as the readonly Zenuser account and sent all the events to history... fudge
12:34:27 PM mrayzenoss: from the Event History: 009/12/10 03:53:53.000 readonly said:
Deleted by user
12:45:38 PM rmatte: that's extremely useful
12:45:39 PM rmatte: lol
1:04:05 PM Jane_Curry: I bet you can undelete it too - for another logged comment by user!
1:18:27 PM bbibeault1: Feedback from #zenoss:
1:19:45 PM bbibeault1: cain22 ok, not sure if i'm loving the new event viewer
1:19:45 PM bbibeault1: RoundQube cain22 what are you issues with it?
1:19:46 PM bbibeault1: cain22 well, it took me second to realize how to open up the event in detail....
1:19:50 PM bbibeault1: daveborg98 That took me a minute as well.
1:19:54 PM bbibeault1: cain22 and maybe its jsut me, but since its smaller font, it alot of the info seems to blend in, making it harder to recongize events at a glance
1:19:59 PM bbibeault1: mrayzenoss cain22: Configure->Show severity row colors
1:20:03 PM bbibeault1: cain22 i did. colors makes it easier...but font size is what i was refering to...
1:20:07 PM bbibeault1: daveborg98 I personally like it. I am at 1680x1050 res. and I can see a lot of the event details on that screen. It does make it a little more difficult on my 1920x1200 screen though.
1:26:57 PM mrayzenoss: Jane_Curry: http://dev.zenoss.org/trac/ticket/5926
2:11:10 PM bbibeault1: Performing a defect review now.
3:30:34 PM bbibeault1: A few new tickets have been added, and right now a few of us are updating some of the Event Console test cases.
3:30:46 PM bbibeault1: Any other community feedback? Issues or questions that you have had?
3:34:46 PM Alvaro2: I included this defect about the horizontal scrollbar. http://dev.zenoss.com/trac/ticket/5927
4:02:24 PM bbibeault1: Note : I am adding test cases around the Event Fields (admin guide, section 7.1.x)
4:03:02 PM bbibeault1: TC created - javascript:ET(3107)javascript:ET(3107)
4:03:07 PM cumanzor: Adding a few testcases about event manager options that affect the event console
4:14:47 PM bbibeault1: TC created - javascript:ET(3109)javascript:ET(3109)
4:21:46 PM bbibeault1: TC created - javascript:ET(3111)javascript:ET(3111)
4:32:28 PM Fuzzy_T: 2009-12-10 16:31:45,171 WARNING zen.zenmib: Unable to find a file providing the OID RFC1215
4:34:13 PM cumanzor: new testcase added (3115)
4:34:24 PM bbibeault1: Fuzzy, where did that message come from?
4:38:03 PM cumanzor: Fuzzy_T, which MIB are you currently using?
4:38:45 PM Fuzzy_T: nevermind
4:53:26 PM bbibeault1: Guys I am going to sign off, I think that overall this was a productive day, got a good number of defects in, and a few test cases created, as well!
4:54:56 PM mrayzenoss: Thanks guys, I'll grab a transcript of today and post it on the Community IRC page
mrayzenoss has changed the topic to: Help Improve Zenoss' Testing: community/testing (4:55:22 PM)
