Wednesday, July 22, 2009 3:00
The topic for #zenoss is: Zenoss Developers will be here Thursday at 11am Eastern (9:58:26 AM)
9:58:39 AM jb: sup matt
9:58:52 AM mrayzenoss: morning all
9:59:07 AM bedwards: hello
9:59:08 AM jmp242: morning
9:59:09 AM mrayzenoss: bedwards and I will be answering questions this morning, other Zenossians may join in
mrayzenoss has changed the topic to: Zenoss Developers are here for your questions (9:59:23 AM)
9:59:32 AM bwest: hello all
10:01:30 AM jb: mrayzenoss: it would be nice to get zenwinperf stats on the collector graphs..
10:02:37 AM twm1010: jb: I bet you can add it.
10:02:42 AM toninog: zenback/zenrestore... does anyone use it ?
10:03:06 AM mrayzenoss: jb: that sounds like a good ticket or enhancement suggestion, you can enter it on the customer portal
10:03:42 AM jb: k
10:04:00 AM toninog: hi all...
10:04:06 AM twm1010: but zenwinperf is a daemon in enterprise
10:04:16 AM twm1010: specifically for collecting perf data over WMI?
10:04:23 AM toninog: I was wondering if anyone had any sucess stories for using drbd ?
10:04:28 AM stefanlsd: What kind of questions will you guys be answering? I have a technical question...
10:04:40 AM chudler: toninog: we use drbd with success
10:04:49 AM LiamW: They answer all questions
10:04:52 AM mrayzenoss: twm1010: yes
10:05:00 AM mrayzenoss: stefanlsd: whatever you want to ask
10:05:16 AM toninog: chudler: mike here is frightfully afraid of it... is there any compelling evidence I can use to attack his fear?
10:05:43 AM LiamW: mray: When monitoring SSH devices how do I get zenoss to create an event when the interface is down?
10:06:01 AM jb: http://dev.zenoss.org/trac/ticket/5357
10:06:09 AM chudler: probably not, it is a terrible situation to be afraid of technology. Perhaps if mike could elucidate on his fears.
10:06:32 AM stefanlsd: thanks! I've written a custom command to log to our helpdesk. Im using a transform on a ping to suppress any further notifications on a device which works, (we get one email) but it seems like it still runs the custom command for each device it should suppress. ie. how can i suppress the custom command also...
10:06:40 AM chudler: drbd is not just something someone cooked up in their basement, FWIW
10:06:56 AM toninog: chudler: hehe - hence is fear
10:07:21 AM toninog: its is a pity that the zoDB cannot be distributed like a mysql (or any other sql server) can
10:08:03 AM bedwards: LiamW: you need to add an event to the result object returned by the parser
10:08:14 AM mrayzenoss: LiamW: is there a ping down event associated with the interface?
10:08:17 AM chudler: it is very well thought out, clean and performs well. There are probably thousands of happy users out there. I think it will be in the mainline kernel Real Soon Now
10:09:06 AM LiamW: mray: I am not receiveing any events when an interface goes down, whether it is SNMP or SSH
10:09:07 AM toninog: chudler: have you had a time when you actually tested its failover and did so successfully?
10:09:16 AM chudler: toninog: yes
10:09:30 AM toninog: chudler: is your drbd systems geographically dispersed ?
10:10:17 AM jb: be careful with DRBD if your boxes aren't local to each other.. DRBD isn't very happy over high latency links.
10:10:35 AM chudler: toninog: no
10:10:50 AM toninog: jb: have you had experience with the drbd over low latency links ?
10:10:56 AM jb: yep
10:11:03 AM jb: i use DRBD for several heartbeat clusters
10:11:12 AM jb: im talking < 5ms though
10:11:24 AM toninog: jb: ok - and do you have any scary stories ?
10:11:27 AM rmatte: when using the stack installer to upgrade, it shouldn't write over my current zenoss config files (in $ZENHOME/etc)? Or will it?
10:11:41 AM jb: nope
10:11:48 AM jb: occasinally a split brain occurs..
10:11:52 AM toninog: jb: excellent.. is it just lag then ?
10:12:38 AM jb: yeah, just test it..
10:13:14 AM toninog: jb: excellent... I think I will
10:13:19 AM LiamW: rocket: will you be adding memory to the Linux monitor addon zenpack?
10:13:34 AM mrayzenoss: rmatte: there may be a ticket about that
10:13:58 AM mrayzenoss: LiamW: what kind of memory?
10:14:07 AM mrayzenoss: LiamW: like a perf graph?
10:14:12 AM rmatte: mrayzenoss: just looking for a will or won't, that way I'll know whether or not I need to back them up and restore them afterwards (no big deal if I do)
10:14:26 AM rmatte: I guess I'll know after this upgrade lol
10:14:51 AM LiamW: buffer, cache, used etc
10:15:37 AM toninog: chudler: jb: thanks for the info ...
10:15:58 AM mrayzenoss: rmatte: http://dev.zenoss.org/trac/ticket/4967 Looks like it's supposed to work and we haven't had customer issues with it, but someone lost their etc on a failed upgrade
10:16:02 AM mrayzenoss: so back it up to be safe
10:16:13 AM rmatte: mrayzenoss: ok, sounds good, thanks
10:17:11 AM rmatte: I finally got this clones vm to work on our test box, it was geared up to run on one of our super servers in our blade enclosure at a data center, then I copied it down to a server in our lab environment and it kept crashing lol
10:17:19 AM rmatte: cloned*
10:17:22 AM mrayzenoss: LiamW: You can open tickets against community ZenPacks in the Community ZenPack repository: http://community.zenoss.org
10:17:35 AM LiamW: ok
10:17:36 AM mrayzenoss: LiamW: and submit patches
10:17:43 AM twm1010: Is there a good tutorial/guide on creating custom device reports?
10:18:16 AM twm1010: I'm looking to create one that shows me all the gigabit ports on my core switches that are currently linked at 100Mb.
10:18:26 AM bedwards: stefanlsd: I don't know of a way to suppress custom commands. you can open an enhancement request.
10:18:44 AM rmatte: twm1010: you'd probably have to code that
10:19:02 AM rmatte: twm1010: using the easy report interface under the edit tab in custom reports is very limited
10:19:16 AM mrayzenoss: twm1010: http://www.zenoss.com/community/docs/zenoss-dev-guide/2.4.2/ch14.html and http://www.zenoss.com/community/docs/zenoss-guide/2.4.2/ch12s08.html
10:19:30 AM mrayzenoss: twm1010: King Crab will have some more hooks to make zendmd calls easier
10:19:33 AM LiamW: Where do I check to ensure that the zenoss cron jobs are running?
10:20:09 AM rmatte: mrayzenoss: any chance that the report exporting gets fixed by King Crab?
10:20:25 AM mrayzenoss: rmatte: Chet took your tickets that you opened, so those should get fixed
10:20:36 AM rmatte: good stuff
10:21:08 AM rmatte: the one is like a two second fix, the other one is really just Zenoss directly accessing the values in Zope rather than taking in to account the final values displayed in the report
10:21:31 AM twm1010: mrayzenoss: any good examples out there I can use to backwards build what i need? like someone who created an interface inventory report or something?
10:22:16 AM rmatte: twm1010: you could just look at the interface utilization report, it includes speeds of interfaces
10:22:17 AM mrayzenoss: LiamW: not sure, you could check the stuff in $ZENHOME/logs for whatever you're calling, or I like to add "MARK-CRON" stuff to logs as a notifier that my cronjobs are running
10:22:37 AM rmatte: twm1010: you then just have to add something to the report that only lists interfaces that are 100mbps
10:22:53 AM twm1010: now how did i miss that...
10:23:09 AM rmatte:
10:23:42 AM twm1010: ah, well, excel can do that easy enough
10:24:06 AM rmatte: yeh, the problem is that when you export to excel, it doesn't show the same values as in the report
10:24:16 AM rmatte: instead of 100mbps you'll see like 100000000
10:24:18 AM rmatte: or something
10:24:21 AM twm1010: eh, thats okay
10:24:22 AM mrayzenoss: the MAC Address report has more stuff with Interfaces for another example
10:24:48 AM mrayzenoss: trac-zenpacks/wiki/ZenPackssodonnellMACReport
10:25:00 AM twm1010: im looking for gigabit ports linked at 100Mbps... we've had people using up our expensive reports for management cards that only link at 100
10:25:00 AM rmatte: twm1010: also, that export is broken for exporting, you won't see the interfaces column, but it's easy to fix
10:25:01 AM twm1010: nice huh?
10:25:35 AM twm1010: that particular report won't export is what you're saying?
10:25:36 AM rmatte: twm1010: http://dev.zenoss.org/trac/ticket/5350
10:25:36 AM mrayzenoss: feel free to send in any custom reports as ZenPacks
10:25:45 AM rmatte: it'll export, the interfaces column will be missing
10:25:58 AM rmatte: read that track ticket I posted, it explains how to fix it
10:26:11 AM twm1010: mrayzenoss: I'd love to write some, but the problem is that I don't know the variables/column names to query?
10:26:40 AM rmatte: after you edit the file, run: python $ZENHOME/Products/ZenReports/ReportLoader.py --force
10:26:40 AM twm1010: rmatte: thanks, I'll edit the report
10:26:47 AM rmatte: as zenoss user, to load the report
10:26:49 AM rmatte: then it'll work
10:27:20 AM rmatte: the report writing is pretty brutal, I'm just starting to wrap my mind around it
10:27:26 AM jb: rocket: around?
10:29:39 AM twm1010: Yeah I jumped over to our SolarWinds box to try and get what I need, but thanks to licensing, we only monitor some of the ports, not what I need here
10:30:28 AM rmatte: ah, yeh, we're using solarwinds for reporting as well
10:30:39 AM jb: we are too
10:30:50 AM rmatte: I'd prefer to use Zenoss, but the reporting in it is a bit shaky at the moment
10:31:00 AM rmatte: I'm sure it'll improve down the road
10:31:03 AM jb: we monitor all network stuff with solarwinds..
10:31:16 AM rmatte: for actual monitoring we use Zenoss
10:31:21 AM rmatte: for reporting we use solarwinds
10:35:10 AM rmatte: the fact that solarwinds only runs in windows is a bit of a deal breaker for the monitoring aspect
10:48:54 AM mrayzenoss: kinda quiet after the first bunch of questions...
10:52:46 AM jmp242: 4
10:53:47 AM rmatte: yeh lol
10:54:54 AM rmatte: I'm running a test upgrade right now, waiting to see how well it works. We're going to be deploying it to our production servers provided it works properly
10:55:01 AM mrayzenoss: ok, let's see. There will probably be a 2.4.3 in a few weeks. We're still shooting for a beta testing for King Crab around late next month
10:55:33 AM rmatte: cool
10:55:59 AM rmatte: I'll probably load up the beta version of King crab on a VM in our lab
10:56:23 AM mrayzenoss: excellent. We sent out a ton of t-shirts to beta testers last release
10:56:50 AM rmatte: are there t-shirts for this release?
10:57:06 AM mrayzenoss: yeah, there will be beta tester t-shirts again
10:57:11 AM rmatte: nice
10:57:11 AM mrayzenoss: we should be putting up a demo server for feedback on the new event console soon
10:57:24 AM mrayzenoss: Ian demoed it Monday, it's very nice
10:57:37 AM rmatte: yeh, I can't wait to see that, does that mean the device list view is going to be a bit different too? (since it's similar)
10:57:43 AM mrayzenoss: not yet
10:57:52 AM rmatte: ah
10:57:55 AM mrayzenoss: We're tackling one screen at a time
10:58:01 AM rmatte: gotcha
10:58:11 AM mrayzenoss: this will clear up the Event Console and Event Views
10:58:37 AM mrayzenoss: let you save queries, better filtering and ordering, it's very slick
10:58:51 AM rmatte: actually, I just remembered a trac ticket that I wanted to log for Zenoss auto-clearing events... It's not possible to auto-clear above error, so the Critical events never get cleared
11:00:10 AM mrayzenoss: don't know the history of that, wonder if that's intentional
11:00:27 AM rmatte: possibly, but seems like the user should be able to do it if they wish to
11:00:34 AM mrayzenoss: agreed
11:01:15 AM rmatte: in our case, we have it sending events to our ticketing system, so no one actually goes in to Zenoss to acknowledge or clear events, so we have it set to auto-clear them every hour
11:01:35 AM rmatte: by "clear" I mean move to history
11:01:37 AM mrayzenoss: well that's a shame, you won't get the full glory of the new Event Console
11:02:17 AM rmatte: well, I still use the event console for tuning, but the analysts just use the ticketing system, easier to work with, plus it allows us to run multiple instances of Zenoss and have all the events displayed in one spot
11:02:25 AM rmatte: and we can sort alerts out by queue if need be
11:03:37 AM rmatte: where we're lacking right now is in the reporting aspect, which is something we're working on
11:04:19 AM mrayzenoss: yeah, reporting just missed the cut for King Crab, it's a known weakness
11:04:36 AM rmatte: well, the upgrade didn't trash my ldap settings, that's good news
11:05:15 AM rmatte: it'd be nice to see a better gui based report designer
11:05:38 AM rmatte: where you can pick common components, such as intefaces, disk, etc... and build reports then apply filters or whatever and save the report
11:05:50 AM mrayzenoss: that would be nice
11:06:17 AM rmatte: By the way, when I get the message that the google maps API is not valid, the map loads anyways, so how necessary is that actual key?
11:06:27 AM mrayzenoss: that seems odd
11:06:35 AM mrayzenoss: do you have an API key in there?
11:06:37 AM rmatte: I've never had the map not load from a bad key
11:06:42 AM rmatte: yeh, there's a key in there
11:07:04 AM rmatte: it just complains that it's not valid (since I'm accessing the box using a different IP/hostname than it is on the prod version of the image)
11:07:07 AM rmatte: but the map loads anyways
11:07:27 AM mrayzenoss: perhaps the API key was made by IP and it changed? Or by hostname and the IP changed?
11:07:33 AM mrayzenoss: yup
11:07:37 AM rmatte: yeh, that's probably it
11:07:54 AM rmatte: but the fact that it still works means you could potentially just use 1 key, and just find a way to eliminate that error message
11:07:54 AM mrayzenoss: minor annoyance, I don't know if there's a fix
11:07:58 AM rmatte: provided it works regardless
11:08:08 AM mrayzenoss: possibly, I don't know
11:08:20 AM mrayzenoss: maybe they figure the annoyance is enough
11:08:21 AM rmatte: does the enterprise version just generate keys on the fly?
11:08:46 AM mrayzenoss: I'm not sure, I think they provide the API key for you
11:09:04 AM rmatte: ah
11:09:07 AM mrayzenoss: I really don't have any exposure to that part
11:09:18 AM rmatte: alright hehe, just curious
11:09:36 AM rmatte: ummm weird
11:10:05 AM rmatte: oh wait, nevermind, it worked
11:10:20 AM rmatte: I was looking at "Available Zenoss Version" which still says 2.3.3
11:10:40 AM rmatte: but the upgrade worked, very smoothly
11:11:14 AM mrayzenoss: is it firewalled? that's weird. Mine says 2.4.2
11:16:47 AM mrayzenoss: Alright, I'm gonna let bedwards off the hook and call it a session. I'll be around per usual, but thanks to everyone who stopped by
mrayzenoss has changed the topic to: Help Zenoss Expand our Testing: http://tinyurl.com/ntyu7b (11:17:52 AM)
The topic for #zenoss is: Zenoss Developers will be here Thursday at 11am Eastern (9:58:26 AM)
9:58:39 AM jb: sup matt
9:58:52 AM mrayzenoss: morning all
9:59:07 AM bedwards: hello
9:59:08 AM jmp242: morning
9:59:09 AM mrayzenoss: bedwards and I will be answering questions this morning, other Zenossians may join in
mrayzenoss has changed the topic to: Zenoss Developers are here for your questions (9:59:23 AM)
9:59:32 AM bwest: hello all
10:01:30 AM jb: mrayzenoss: it would be nice to get zenwinperf stats on the collector graphs..
10:02:37 AM twm1010: jb: I bet you can add it.
10:02:42 AM toninog: zenback/zenrestore... does anyone use it ?
10:03:06 AM mrayzenoss: jb: that sounds like a good ticket or enhancement suggestion, you can enter it on the customer portal
10:03:42 AM jb: k
10:04:00 AM toninog: hi all...
10:04:06 AM twm1010: but zenwinperf is a daemon in enterprise
10:04:16 AM twm1010: specifically for collecting perf data over WMI?
10:04:23 AM toninog: I was wondering if anyone had any sucess stories for using drbd ?
10:04:28 AM stefanlsd: What kind of questions will you guys be answering? I have a technical question...
10:04:40 AM chudler: toninog: we use drbd with success
10:04:49 AM LiamW: They answer all questions
10:04:52 AM mrayzenoss: twm1010: yes
10:05:00 AM mrayzenoss: stefanlsd: whatever you want to ask
10:05:16 AM toninog: chudler: mike here is frightfully afraid of it... is there any compelling evidence I can use to attack his fear?
10:05:43 AM LiamW: mray: When monitoring SSH devices how do I get zenoss to create an event when the interface is down?
10:06:01 AM jb: http://dev.zenoss.org/trac/ticket/5357
10:06:09 AM chudler: probably not, it is a terrible situation to be afraid of technology. Perhaps if mike could elucidate on his fears.
10:06:32 AM stefanlsd: thanks! I've written a custom command to log to our helpdesk. Im using a transform on a ping to suppress any further notifications on a device which works, (we get one email) but it seems like it still runs the custom command for each device it should suppress. ie. how can i suppress the custom command also...
10:06:40 AM chudler: drbd is not just something someone cooked up in their basement, FWIW
10:06:56 AM toninog: chudler: hehe - hence is fear
10:07:21 AM toninog: its is a pity that the zoDB cannot be distributed like a mysql (or any other sql server) can
10:08:03 AM bedwards: LiamW: you need to add an event to the result object returned by the parser
10:08:14 AM mrayzenoss: LiamW: is there a ping down event associated with the interface?
10:08:17 AM chudler: it is very well thought out, clean and performs well. There are probably thousands of happy users out there. I think it will be in the mainline kernel Real Soon Now
10:09:06 AM LiamW: mray: I am not receiveing any events when an interface goes down, whether it is SNMP or SSH
10:09:07 AM toninog: chudler: have you had a time when you actually tested its failover and did so successfully?
10:09:16 AM chudler: toninog: yes
10:09:30 AM toninog: chudler: is your drbd systems geographically dispersed ?
10:10:17 AM jb: be careful with DRBD if your boxes aren't local to each other.. DRBD isn't very happy over high latency links.
10:10:35 AM chudler: toninog: no
10:10:50 AM toninog: jb: have you had experience with the drbd over low latency links ?
10:10:56 AM jb: yep
10:11:03 AM jb: i use DRBD for several heartbeat clusters
10:11:12 AM jb: im talking < 5ms though
10:11:24 AM toninog: jb: ok - and do you have any scary stories ?
10:11:27 AM rmatte: when using the stack installer to upgrade, it shouldn't write over my current zenoss config files (in $ZENHOME/etc)? Or will it?
10:11:41 AM jb: nope
10:11:48 AM jb: occasinally a split brain occurs..
10:11:52 AM toninog: jb: excellent.. is it just lag then ?
10:12:38 AM jb: yeah, just test it..
10:13:14 AM toninog: jb: excellent... I think I will
10:13:19 AM LiamW: rocket: will you be adding memory to the Linux monitor addon zenpack?
10:13:34 AM mrayzenoss: rmatte: there may be a ticket about that
10:13:58 AM mrayzenoss: LiamW: what kind of memory?
10:14:07 AM mrayzenoss: LiamW: like a perf graph?
10:14:12 AM rmatte: mrayzenoss: just looking for a will or won't, that way I'll know whether or not I need to back them up and restore them afterwards (no big deal if I do)
10:14:26 AM rmatte: I guess I'll know after this upgrade lol
10:14:51 AM LiamW: buffer, cache, used etc
10:15:37 AM toninog: chudler: jb: thanks for the info ...
10:15:58 AM mrayzenoss: rmatte: http://dev.zenoss.org/trac/ticket/4967 Looks like it's supposed to work and we haven't had customer issues with it, but someone lost their etc on a failed upgrade
10:16:02 AM mrayzenoss: so back it up to be safe
10:16:13 AM rmatte: mrayzenoss: ok, sounds good, thanks
10:17:11 AM rmatte: I finally got this clones vm to work on our test box, it was geared up to run on one of our super servers in our blade enclosure at a data center, then I copied it down to a server in our lab environment and it kept crashing lol
10:17:19 AM rmatte: cloned*
10:17:22 AM mrayzenoss: LiamW: You can open tickets against community ZenPacks in the Community ZenPack repository: http://community.zenoss.org
10:17:35 AM LiamW: ok
10:17:36 AM mrayzenoss: LiamW: and submit patches
10:17:43 AM twm1010: Is there a good tutorial/guide on creating custom device reports?
10:18:16 AM twm1010: I'm looking to create one that shows me all the gigabit ports on my core switches that are currently linked at 100Mb.
10:18:26 AM bedwards: stefanlsd: I don't know of a way to suppress custom commands. you can open an enhancement request.
10:18:44 AM rmatte: twm1010: you'd probably have to code that
10:19:02 AM rmatte: twm1010: using the easy report interface under the edit tab in custom reports is very limited
10:19:16 AM mrayzenoss: twm1010: http://www.zenoss.com/community/docs/zenoss-dev-guide/2.4.2/ch14.html and http://www.zenoss.com/community/docs/zenoss-guide/2.4.2/ch12s08.html
10:19:30 AM mrayzenoss: twm1010: King Crab will have some more hooks to make zendmd calls easier
10:19:33 AM LiamW: Where do I check to ensure that the zenoss cron jobs are running?
10:20:09 AM rmatte: mrayzenoss: any chance that the report exporting gets fixed by King Crab?
10:20:25 AM mrayzenoss: rmatte: Chet took your tickets that you opened, so those should get fixed
10:20:36 AM rmatte: good stuff
10:21:08 AM rmatte: the one is like a two second fix, the other one is really just Zenoss directly accessing the values in Zope rather than taking in to account the final values displayed in the report
10:21:31 AM twm1010: mrayzenoss: any good examples out there I can use to backwards build what i need? like someone who created an interface inventory report or something?
10:22:16 AM rmatte: twm1010: you could just look at the interface utilization report, it includes speeds of interfaces
10:22:17 AM mrayzenoss: LiamW: not sure, you could check the stuff in $ZENHOME/logs for whatever you're calling, or I like to add "MARK-CRON" stuff to logs as a notifier that my cronjobs are running
10:22:37 AM rmatte: twm1010: you then just have to add something to the report that only lists interfaces that are 100mbps
10:22:53 AM twm1010: now how did i miss that...
10:23:09 AM rmatte:
10:23:42 AM twm1010: ah, well, excel can do that easy enough
10:24:06 AM rmatte: yeh, the problem is that when you export to excel, it doesn't show the same values as in the report
10:24:16 AM rmatte: instead of 100mbps you'll see like 100000000
10:24:18 AM rmatte: or something
10:24:21 AM twm1010: eh, thats okay
10:24:22 AM mrayzenoss: the MAC Address report has more stuff with Interfaces for another example
10:24:48 AM mrayzenoss: trac-zenpacks/wiki/ZenPackssodonnellMACReport
10:25:00 AM twm1010: im looking for gigabit ports linked at 100Mbps... we've had people using up our expensive reports for management cards that only link at 100
10:25:00 AM rmatte: twm1010: also, that export is broken for exporting, you won't see the interfaces column, but it's easy to fix
10:25:01 AM twm1010: nice huh?
10:25:35 AM twm1010: that particular report won't export is what you're saying?
10:25:36 AM rmatte: twm1010: http://dev.zenoss.org/trac/ticket/5350
10:25:36 AM mrayzenoss: feel free to send in any custom reports as ZenPacks
10:25:45 AM rmatte: it'll export, the interfaces column will be missing
10:25:58 AM rmatte: read that track ticket I posted, it explains how to fix it
10:26:11 AM twm1010: mrayzenoss: I'd love to write some, but the problem is that I don't know the variables/column names to query?
10:26:40 AM rmatte: after you edit the file, run: python $ZENHOME/Products/ZenReports/ReportLoader.py --force
10:26:40 AM twm1010: rmatte: thanks, I'll edit the report
10:26:47 AM rmatte: as zenoss user, to load the report
10:26:49 AM rmatte: then it'll work
10:27:20 AM rmatte: the report writing is pretty brutal, I'm just starting to wrap my mind around it
10:27:26 AM jb: rocket: around?
10:29:39 AM twm1010: Yeah I jumped over to our SolarWinds box to try and get what I need, but thanks to licensing, we only monitor some of the ports, not what I need here
10:30:28 AM rmatte: ah, yeh, we're using solarwinds for reporting as well
10:30:39 AM jb: we are too
10:30:50 AM rmatte: I'd prefer to use Zenoss, but the reporting in it is a bit shaky at the moment
10:31:00 AM rmatte: I'm sure it'll improve down the road
10:31:03 AM jb: we monitor all network stuff with solarwinds..
10:31:16 AM rmatte: for actual monitoring we use Zenoss
10:31:21 AM rmatte: for reporting we use solarwinds
10:35:10 AM rmatte: the fact that solarwinds only runs in windows is a bit of a deal breaker for the monitoring aspect
10:48:54 AM mrayzenoss: kinda quiet after the first bunch of questions...
10:52:46 AM jmp242: 4
10:53:47 AM rmatte: yeh lol
10:54:54 AM rmatte: I'm running a test upgrade right now, waiting to see how well it works. We're going to be deploying it to our production servers provided it works properly
10:55:01 AM mrayzenoss: ok, let's see. There will probably be a 2.4.3 in a few weeks. We're still shooting for a beta testing for King Crab around late next month
10:55:33 AM rmatte: cool
10:55:59 AM rmatte: I'll probably load up the beta version of King crab on a VM in our lab
10:56:23 AM mrayzenoss: excellent. We sent out a ton of t-shirts to beta testers last release
10:56:50 AM rmatte: are there t-shirts for this release?
10:57:06 AM mrayzenoss: yeah, there will be beta tester t-shirts again
10:57:11 AM rmatte: nice
10:57:11 AM mrayzenoss: we should be putting up a demo server for feedback on the new event console soon
10:57:24 AM mrayzenoss: Ian demoed it Monday, it's very nice
10:57:37 AM rmatte: yeh, I can't wait to see that, does that mean the device list view is going to be a bit different too? (since it's similar)
10:57:43 AM mrayzenoss: not yet
10:57:52 AM rmatte: ah
10:57:55 AM mrayzenoss: We're tackling one screen at a time
10:58:01 AM rmatte: gotcha
10:58:11 AM mrayzenoss: this will clear up the Event Console and Event Views
10:58:37 AM mrayzenoss: let you save queries, better filtering and ordering, it's very slick
10:58:51 AM rmatte: actually, I just remembered a trac ticket that I wanted to log for Zenoss auto-clearing events... It's not possible to auto-clear above error, so the Critical events never get cleared
11:00:10 AM mrayzenoss: don't know the history of that, wonder if that's intentional
11:00:27 AM rmatte: possibly, but seems like the user should be able to do it if they wish to
11:00:34 AM mrayzenoss: agreed
11:01:15 AM rmatte: in our case, we have it sending events to our ticketing system, so no one actually goes in to Zenoss to acknowledge or clear events, so we have it set to auto-clear them every hour
11:01:35 AM rmatte: by "clear" I mean move to history
11:01:37 AM mrayzenoss: well that's a shame, you won't get the full glory of the new Event Console
11:02:17 AM rmatte: well, I still use the event console for tuning, but the analysts just use the ticketing system, easier to work with, plus it allows us to run multiple instances of Zenoss and have all the events displayed in one spot
11:02:25 AM rmatte: and we can sort alerts out by queue if need be
11:03:37 AM rmatte: where we're lacking right now is in the reporting aspect, which is something we're working on
11:04:19 AM mrayzenoss: yeah, reporting just missed the cut for King Crab, it's a known weakness
11:04:36 AM rmatte: well, the upgrade didn't trash my ldap settings, that's good news
11:05:15 AM rmatte: it'd be nice to see a better gui based report designer
11:05:38 AM rmatte: where you can pick common components, such as intefaces, disk, etc... and build reports then apply filters or whatever and save the report
11:05:50 AM mrayzenoss: that would be nice
11:06:17 AM rmatte: By the way, when I get the message that the google maps API is not valid, the map loads anyways, so how necessary is that actual key?
11:06:27 AM mrayzenoss: that seems odd
11:06:35 AM mrayzenoss: do you have an API key in there?
11:06:37 AM rmatte: I've never had the map not load from a bad key
11:06:42 AM rmatte: yeh, there's a key in there
11:07:04 AM rmatte: it just complains that it's not valid (since I'm accessing the box using a different IP/hostname than it is on the prod version of the image)
11:07:07 AM rmatte: but the map loads anyways
11:07:27 AM mrayzenoss: perhaps the API key was made by IP and it changed? Or by hostname and the IP changed?
11:07:33 AM mrayzenoss: yup
11:07:37 AM rmatte: yeh, that's probably it
11:07:54 AM rmatte: but the fact that it still works means you could potentially just use 1 key, and just find a way to eliminate that error message
11:07:54 AM mrayzenoss: minor annoyance, I don't know if there's a fix
11:07:58 AM rmatte: provided it works regardless
11:08:08 AM mrayzenoss: possibly, I don't know
11:08:20 AM mrayzenoss: maybe they figure the annoyance is enough
11:08:21 AM rmatte: does the enterprise version just generate keys on the fly?
11:08:46 AM mrayzenoss: I'm not sure, I think they provide the API key for you
11:09:04 AM rmatte: ah
11:09:07 AM mrayzenoss: I really don't have any exposure to that part
11:09:18 AM rmatte: alright hehe, just curious
11:09:36 AM rmatte: ummm weird
11:10:05 AM rmatte: oh wait, nevermind, it worked
11:10:20 AM rmatte: I was looking at "Available Zenoss Version" which still says 2.3.3
11:10:40 AM rmatte: but the upgrade worked, very smoothly
11:11:14 AM mrayzenoss: is it firewalled? that's weird. Mine says 2.4.2
11:16:47 AM mrayzenoss: Alright, I'm gonna let bedwards off the hook and call it a session. I'll be around per usual, but thanks to everyone who stopped by
mrayzenoss has changed the topic to: Help Zenoss Expand our Testing: http://tinyurl.com/ntyu7b (11:17:52 AM)
