On a day to day basis, it’s more common to read JMX metrics via automated, ‘read-only’ monitoring tools like Nagios, Ganglia, or AppNeta TraceView. These tools not only present a number of metrics at once, but they also generally let you filter down to a meaningful subset of the hundreds of lines exposed by Solr. On the other hand, “health check”-style metrics aren’t necessarily the only way to look the problem. Each request has a number of metrics it can generate, and bringing together these data sources in one application has some real advantages. Looking at an individual request can tell you exactly what went wrong, it’s often the context of JMX data that says why. Examining the concurrent host activity can disambiguate between whether a pause was due to a garbage collection event in the JVM or an overloaded document cache in Solr forcing additional disk access.
Read full article from Black Boxes: Monitoring Solr (JMX Edition) | AppNeta
No comments:
Post a Comment