Update?
JerKart
Zenoss?
Duncan McGreggor
>
> Have you had a chance to work on CoyMon or integrating Netflow into
> Zenoss?
A while back, I did have some time to work on CoyMon. Sadly, the
original Plone code was so out of date with current Plone that the
level of effort for a "quick fix" of getting it running actually
involved a pretty serious audit and overhaul.
I'm not contracting for Zenoss anymore, either (I'm actually working
for the guys that created Twisted Python, which is used in both CoyMon
and Zenoss). I tried a couple times to advocate Netflow integration
into Zenoss (as did several other community members), but it just
wasn't high enough on their list of priorities. Not sure what their
plans are now, but I haven't heard anything about Netflow from them in
over a year.
Working on CoyMon is still on my wishlist, but it's the same ol' open
source dev story: most of my time goes to the code that pays the
bills. I'd like to spend more time on it, but I just don't know when
that will be :-( I think about it all the time, and have a whole slew
of new ideas, but I refrain from posting them to the list, since
previous posts of that sort haven't produced anything but
disappointment for you guys.
One sliver of hope is that Divmod is a product-oriented company: we've
got several commercial apps and a new Web 2.0 social networking app
currently hovering towards beta. I've already talked to team leaders
about AJAX/COMET-enabled sys/network admin app ideas.
On that note, if we did re-package CoyMon as an AJAX/COMET app, we'd
want to make it light-weight with a few important target features --
no bloat, no scope creep (so we could get it out the door). That being
said, what would be your top set of features? What would it absolutely
have to do in order for you to use it and love it?
d
JerKart
customize and graph on the fly. The best features were allowing the
inclusion/exclusion of any port and how it differentiated directions
(outbound flows graphed below 0 on the x axis and inbound above), it
also allowed for selection of which devices (flows) you wanted to
include. The interface was very clunky and unfriendly, and I don't
remember there being a static "last day" style page for all flows.
Our favorite tool at this time is cacti, my boss really likes being
able to click to select time spans, and the network management team
likes the trees to be able to track things important to whatever
project we are working on.
So to go with bullet points:
Need:
- Flexibility of JKFlow
- Usability of Cacti
- Ability to graph based on # of connections or bits xfered
Want:
- Ability to choose which interface of the router to see the flow on
- Alerting based on # of connections per host per time period or
bandwidth utilized
On Sep 25, 12:27 pm, "Duncan McGreggor" <duncan.mcgreg...@gmail.com>
wrote:
JerKart
customize and graph on the fly. The best features were allowing the
inclusion/exclusion of any port and how it differentiated directions
(outbound flows graphed below 0 on the x axis and inbound above), it
also allowed for selection of which devices (flows) you wanted to
include. The interface was very clunky and unfriendly, and I don't
remember there being a static "last day" style page for all flows.
Our favorite tool at this time is cacti, my boss really likes being
able to click to select time spans, and the network management team
likes the trees to be able to track things important to whatever
project we are working on.
So to go with bullet points:
Need:
- Flexibility of JKFlow
- Usability of Cacti
- Ability to graph based on # of connections or bits xfered
Want:
- Ability to choose which interface of the router to see the flow on
- Alerting based on # of connections per host per time period or
bandwidth utilized
On Sep 25, 12:27 pm, "Duncan McGreggor" <duncan.mcgreg...@gmail.com>
wrote: