Skip to content

SolrCloud Monitoring Integration

Sematext offers simple and versatile SolrCloud monitoring agent written in Java and Golang with minimal CPU and memory overhead. It's easy to install and require no changes in the SolrCloud source code or your application's source code.

Sematext SolrCloud Monitoring Agent

This lightweight, open-source Monitoring Agent collects SolrCloud performance metrics and sends them to Sematext. It comes packaged with a Golang-based agent responsible for Operating System level metrics like network, disk I/O, and more. The SolrCloud Monitoring Agent can be installed with RPM/DEB package manager on any host running Linux or in a containerized environment using sematext/sematext-agent.

The Sematext SolrCloud Monitoring Agent can be run in two different modes - in-process and standalone. The in-process one is run as a Java agent, it is simpler to initially set up, but will require restarting your Solr node when you will want to upgrade your monitoring Agent, i.e. to get new features. The benefit of the standalone agent mode is that it runs as a separate process and doesn't require a Solr restart when it is installed or upgraded.

After creating a SolrCloud App in Sematext you need to install the Monitoring Agent on each host running your SolrCloud nodes to have the full visibility over the metrics from each host. The full installation instructions can be found in the setup instructions displayed in the UI.

For example, on CentOS, you need to add Sematext Linux packages and install them with the following command:

sudo wget -O /etc/yum.repos.d/sematext.repo
sudo yum clean all
sudo yum install sematext-agent

After that, setup the SolrCloud Monitoring Agent by running a command like this:

sudo bash /opt/spm/bin/setup-sematext  \
    --monitoring-token <your-monitoring-token-goes-here>   \
    --app-type solrcloud  \
    --agent-type javaagent  \
    --infra-token <your-infra-token-goes-here>

The command above will set up your SolrCloud Monitoring Agent in the in-process mode. To have it running in the standalone mode, run the command below instead of the one above:

sudo bash /opt/spm/bin/setup-sematext  \
    --monitoring-token <your-monitoring-token-goes-here>   \
    --app-type solr  \
    --agent-type standalone  \
    --infra-token <your-infra-token-goes-here>  \
    --jmx-params '-Dspm.remote.jmx.url=localhost:3000'

Keep in mind that your need to provide the Monitoring token and Infra token. They are both provided in the installation instructions for your SolrCloud App.

Finally, the last thing that needs to be done is adjusting the file and add the following section:

SOLR_OPTS="$SOLR_OPTS -javaagent:/opt/spm/spm-monitor/lib/spm-monitor-generic.jar=<your-monitoring-token-goes-here>::default"

Or if you would like to run the Solr Monitoring Agent in the standalone mode add the following section to the file:


Make sure that tag <jmx /> is enabled in your solrconfig.xml file.

You need to restart your SolrCloud node after the changes above.

Collected Metrics

The Sematext SolrCloud monitoring agent collects the following metrics.

Operating System

  • CPU usage
  • CPU load
  • Memory usage
  • Swap usage
  • Disk space used
  • I/O Reads and Writes
  • Network traffic

Java Virtual Machine

  • Garbage collectors time and count
  • JVM pool size and utilization
  • Threads and daemon threads
  • Files opened by the JVM


  • Requests rate and latency
  • Solr index stats and file system stats
  • Added and pending documents
  • Deletes by id and queries
  • Filter cache statistics
  • Document cache statistics
  • Query result cache statistics
  • Per segment filter cache statistics
  • Commit events
  • Warmup times


If you are having issues with Sematext Monitoring, i.e. not seeing SolrCloud metrics, see How do I create the diagnostics package.

For more troubleshooting information please look at Troubleshooting section.



Metric Name
Key (Type) (Unit)
cache lookups
(long counter)
lookups count
cache hits
(long counter)
hits count
cache size
(long gauge)
cache size (count of elements)
cache evictions
(long counter)
count of evictions
warmup time
(long counter) (ms)
warmup time
cache memory used
(long gauge) (bytes)
cache size in bytes
cache max size
(long gauge)
cache max size
autowarm count or %
(long gauge)
cache autowarm count or %
request time
(long counter) (ms)
request time
(long counter) (req)
request count
avg. request latency
(double gauge)
avg. request latency
request error count
(long counter)
request error count
request timeout count
(long counter)
request timeout count
index max doc
(long gauge) (docs)
max doc in the index
index num docs
(long gauge) (docs)
number of docs in the index
index segments
(long gauge)
index segments count
index num of files
(long gauge)
number of files in solr index
index size on the disk
(long gauge) (bytes)
size of solr index on the disk
(long counter)
total count of commits
(long counter)
count of optimizes
(long counter)
count of rollbacks
expunge deletes
(long counter)
count of expunge deletes
index docs added
(long counter) (docs)
added docs
deletes by id
(long counter)
deletes by id
deletes by query
(long counter)
deletes by query
update errors
(long counter)
count of update errors
(long counter)
count of auto commits
soft autocommits
(long counter)
count of soft auto commits
index docs pending
(long gauge) (docs)
count of pending docs
autocommit max time
(long gauge) (ms)
autocommit max time


How do I enable JMX in Solr?

Add or uncomment the <jmx/> directive in solrconfig.xml and restart Solr. See more info.

I don't see any data on Solr and JVM reports, what is the problem?

You should probably enable JMX in your Solr.Add or uncomment the<jmx />directive insolrconfig.xmland restart Solr. See more info.

I don't see any data only in Solr Components or Errors reports, what should I do?

Most likely you are using the standalone variant of Solr monitor. In that case, App Agent can't collect metrics which are available only when running in-process. If so, switch to in-process (javaagent) version of App Agent.

Why don't I see Solr index file size metric?

App Agent runs as 'spmmon' user. Make sure this user has appropriate access permissions on Solr's index directories. If you cannot give 'spmmon' user the read permissions you can switch to the in-process (javaagent) version of App Agent.