Apache SolrMetricsolr_search_handler_errors
Number of errors per second encountered by the handler.Dimensions:None
Available on:
Datadog (1)
Datadog (1)Interface Metrics (1)
Datadog
Dimensions:None
Knowledge Base (4 documents, 0 chunks)
referenceMonitoring Solr | Apache Solr Reference Guide 8.11126 wordsscore: 0.85This is an index/navigation page from the official Apache Solr Reference Guide that provides an overview of monitoring and administration capabilities. It links to detailed documentation on metrics reporting, logging, JMX integration, Prometheus/Grafana monitoring, and distributed tracing for Solr.
blog postMonitoring Apache Solr and Lucidworks with Zabbix - Lucidworks860 wordsscore: 0.85This blog post provides practical guidance on monitoring Apache Solr and Lucidworks in production using Zabbix monitoring software. It covers how to use JMX interfaces to collect metrics and provides specific examples of important graphs and monitoring configurations including cache statistics, search performance, document operations, and system health checks.
troubleshootingApache Solr Logging and Troubleshooting Common Issues | Reintech media1587 wordsscore: 0.65This guide covers Apache Solr's logging architecture using Log4j 2 and troubleshooting common issues including slow queries, indexing failures, memory problems, and SolrCloud coordination issues. It focuses on log-based diagnostics rather than metrics-based monitoring, providing log patterns to identify performance problems and operational issues.
other[SOLR-1972] Need additional query stats in admin interface - median, 95th and 99th percentile - ASF Jira464 wordsscore: 0.75This is a JIRA issue tracking the implementation of enhanced query statistics in Apache Solr's admin interface, specifically adding percentile metrics (median, 95th, 99th percentile) for request times. The issue was resolved in Solr 4.1/6.0 and led to the integration of the Metrics library for more comprehensive performance monitoring.
Related Insights (2)
Deep Pagination Memory Explosioncritical
Queries with large 'start' parameters (deep pagination) or requesting excessive rows force Solr to allocate memory for all results up to that offset, causing unexpected memory exhaustion even for simple queries.
▸
Failed Shard Causing Distributed Query Timeoutscritical
A single failed or unresponsive shard in a distributed collection causes cascading timeouts across the cluster as queries attempt to reach all shards, eventually making other nodes unresponsive even though they are healthy.
▸