Page History

...

The GET /admin/metrics API will continue to exist, allowing users to scrape metrics with a pull based system. However, the removal of Dropwizard means the current format, its naming conventions and usage will change. The endpoint will now output Prometheus standard formatted metrics and filters will be around tags instead of regex. Below are some use-cases and how the user would migrate:

...

Manual Access to Solr metric endpoint

For example, users who curl Solr with the following to see number of /select requests and errors:

...

Scrape and pull metric models will not change. Only changes are new metrics, naming conventions, and tags.

...

Tests asserting metrics

Solr uses the /admin/metrics for some integration testing. For example, the PeerSyncReplicationTest asserts on REPLICATION.peerSync.errors for any failures on its integration testing. This workflow will stay the same, but developers should pull an Open Telemetry metric reader SDK MetricReader to find these metrics to assert on for their tests.

...

Users will now be open to the option of using Open Telemetry and its push model with OTLP metrics, similar to how traces and spans are being exported.

• Open Telemetry module of OTel Java agent

Users can enable the Open Telemetry module to push metrics or use industry standard plugins to work with their metric pipelines as a new option.