Recomendation for TCP port monitoring - Manage plugin vs ?

[alexupton]

Hello all,

I've looked at all solutions I can identify for use with Cacti:

TCP Port Template
Manage Plugin
NTOP With Flowviewer plugin.

I'm curious what the favored solution is? I've tried the Manage plugin and it doesn't seem very stable/accurate, though it has a dependancy on the TCP Port Templates which makes me think that simply using the templates and thold might be the simplest and most accurate way to generate alerts for downed TCP ports.

The problem with the TCP Port Template is that it's usage from start to finish of greating a TCP port alert for a single or group of ports is a bit confusing.

In the Manage plugin I've created a simple device port monitor for TCP 80 and I was able to trigger an alert by stopping the service on the monitored host, however after re-enabling the service and confirming that TCP 80 was listening. The Manage plugin failed to realize that the port was up and contined to alert upon the event.

So what's everyone's favorite tcp port monitoring and alerting solution for use with Cacti?

Thank you.

[prospero63]

Having just spent some time setting exactly this up, here's my $.02.

Manage is simply an overlay to the TCP Port graphs and charts. I found it to be very buggy and it required a lot of effort to get working, but I like the display. It's my choice for the visual depiction when I want to see at a glance what's going on.

TCP Port template is what drives manage and I use those in my graph tree. Those too required some tweaking to make work properly. There's something wonky with the consolidation function, but I don't know necessarily what.

For alerting I actually use thold in conjunction with the TCP Port template as my notification mechanism.

I don't have NTOP so I can't speak one way or the other on that.

So to recap, TCP Port and Manage, Manage to view, TCP Port for graphing and thold for notification. YMMV.