Skip to content

Solr Logs Integration

To make use of the Sematext Solr Logs integration, you'll need to send parsed Solr logs to your Sematext Logs App. The easiest way is via Logagent, which can parse Solr logs out of the box.

Once data is in, you can explore it via the built-in reports:

Solr Logs Overview

Be sure to check out the Solr Monitoring integration as well, to get a complete view on Solr. For example, if you see logs of a node restarting, metrics let you see the impact on the rest of the cluster in terms of CPU, GC, and other metrics. Including query time metrics, even if you don't collect logs from [all] queries.

Setting up Logagent

With Node.js installed, you'd first need to install Logagent:

sudo npm i -g @sematext/logagent

Then, write a config file that tails your Solr logs and sends them to your Solr Logs App. Parsing happens out of the box, since we match the solr source:

# Global options
  # print stats every 60 seconds 
  printStats: 60
  # don't write parsed logs to stdout
  suppress: true

    - /var/solr/logs/solr.log

    module: elasticsearch
    # use for the EU region
      # send Solr logs to this Logs App
        - .*solr.*\.log

Finally, use logagent-setup to copy the config to /etc/sematext/logagent.conf, then set up the init script and start Logagent:

sudo logagent-setup -c /path/to/logagent.conf

If you already have Logagent installed, you can simply append to the files input the Solr log file, then the two lines (token+pattern) in the elasticsearch output. In the end, restart Logagent. And no, elasticsearch there is not a typo, it's just that Sematext Logs exposes the Elasicsearch API 😊.

Exploring logs

Once data is in, you can explore it using the built-in reports or create your own. For example, you can use the Queries report to see a breakdown of your queries and "zoom in" to the ones you're interested in:

Solr Queries Report

Other built-in reports include:

  • Errors: breakdown of what's wrong: which nodes/classes/collections/etc generate errors
  • Zookeeper: logs produced by Solr's Zookeeper client and other Zookeeper-related classes and threads. Look here for insights on SolrCloud's stability. For the Zookeeper ensemble itself, check out our Zookeeper monitoring integration
  • Overseer: logs produced by SolrCloud's Overseer thread and other Overseer activities (e.g. shard leader election)
  • Start & Stop: startup-related and shutdown-related logs. Look here if a node went down unexpectedly or doesn't show up in the cluster when started


If you have trouble sending logs, try out the latest version of Logagent via sudo npm i -g @sematext/logagent. Also, make sure Logagent is pointed to the right path and Logs App token.

If logs don't get parsed properly, or you need additional parsing, feel free to open an issue or to contribute to Logagent built-in patterns. These patterns are open-source, as well as Logagent itself.