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: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
