tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aurélien Terrestris <>
Subject Re: Monitoring Connections
Date Mon, 02 Nov 2015 22:54:46 GMT
Either my reply was not read, or I'm surprised nobody is answering here.

"1. Java doesn't directly support SNMP;"

It does, officially :
management/snmp.html and it's working pretty well with Tomcat besides being
easy to set up.

"2. If the JVM is braindead, the SNMP agent can't announce any state   to
the managers."

Agent ? This is the SNMP server which is polling the Tomcat here. When
Tomcat is dead, the server cannot poll anymore and raises an alert.

You see how alerting is even easier without instrumenting, but maybe you
want to go deeper. But then, you probably start mixing what's necessary for
N1 support with what's helpful for developers. They have different jobs.

best regards

2015-10-24 14:18 GMT+02:00 Christopher Schultz <

> Aurélien,
> On 10/23/15 6:47 PM, Aurélien Terrestris wrote:
> > "Live monitoring is the only way to go, unless you want your customers
> > to surprise you with performance problems on your own site. :)"
> >
> > Monitoring, ok, but alerting is critical for large scale production
> > environments.
> Apologies... I already considered "alerting" to be a critical component
> of "monitoring", so I didn't mention it specifically. Instrumentation is
> the hard part; alerting is relatively easy once instrumentation has been
> done.
> > You mention JMX callbacks for alerting, but it would be worth
> > that you mention SNMP since it's very easy to set up and efficient.
> SNMP is great, but there are a few problems with using it with Java:
> 1. Java doesn't directly support SNMP; instead, you have to use
>    a 3rd-party library (which isn't difficult to find). This may be
>    a barrier for certain organizations who only want to use their
>    own code in their own applications.
> 2. If the JVM is braindead, the SNMP agent can't announce any state
>    to the managers. This requires the use of probe-based instrumentation
>    (active probing from the outside of the application), unless you want
>    to have an agent send a heartbeat for every status change.
> > We also can raise alerts on deltas with this method, and see a
> > problem before the CPU says something bad is going to happen.
> There's nothing stopping you from doing deltas with other techniques. My
> presentation even includes a tool that allows you to do deltas.
> -chris
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message