Over a million developers have joined DZone.

Introducing Top Database Operations

DZone 's Guide to

Introducing Top Database Operations

A new release of Sematext's SPM introduces database operations to help you run Elasticsearch and Solr with your JDBC apps.

· Database Zone ·
Free Resource

If you run Elasticsearch, Solr, or any datastore you connect to via JDBC, you’ll like what we’ve just added to SPM.  We call it Database Operations and in SPM you can find it in the new Database report:

If you didn’t watch the video, here’s what Database Operations gives you:

  • Top 5 operation types across all your data stores or filtered to a specific data store type.
  • Top 5 operation types by speed, throughput, or simply their volume.
  • Time-series reports for volume, throughput, and latency broken down by operation type.
  • Ability to view all collected operations, not just the slowest ones, filter by database type or by operation type, sorted by average or total duration, or throughput.
  • Sparklines that show last 5 minute values and trends.
  • Top 10 slowest individual operations and drill-in details.

Integration with Transaction Tracing, so you can correlate slow data store operations with the actual transaction/request that triggered slow operations


  • To get this information add SPM agent to the application that is talking to a data store (e.g. Solr or Elasticsearch). This is because the SPM agent captures operations at that client layer, not in the server itself.
  • To start capturing this information enable Transaction Tracing in your SPM agents.

This, including Distributed Transaction Tracingworks for all Java applications.



Don’t forget – when you enable Database Operations you will also automatically get Transaction Tracing, as well as the cool AppMaps – enjoy! :)

Got ideas how we could make Database Operations better and more useful to you? Let us know via comments, email or @sematext.

performance and monitoring ,java ,solr ,elasticsearch

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}