admin/metrics API or read JMX by jolokia?

[S G <sg...@gmail.com>]

Hi,

The API admin/metrics
<https://cwiki.apache.org/confluence/display/solr/Metrics+Reporting#MetricsReporting-MetricsAPI>
in
6.x version of Solr seems to be very good.
Is it performance friendly as well?

We want to use this API to query the metrics every minute or so from all
Solr nodes and push to grafana.
How does this compare with the performance overhead of reading JMX metrics
via Jolokia?

Rest API is surely easier to understand and parse.
However it involves making a REST call that will pass through jetty,
probably take up a thread for each request? etc.
Is Jolokia lighter-weight in this respect?

Some recommendation on this would be great.

Thanks
SG

Re: admin/metrics API or read JMX by jolokia?

[Tech Id <te...@gmail.com>]

Yes, this is really good to know.

With Jolokia, it is difficult to parse the output a bit because of the
presence of special characters in the mbean name like '
http://localhost:17330/jolokia/read/solr!/my!-collection_shard1_replica2:*'

The presence of slashes etc. makes parsing and querying a bit messy.
And if we know for sure that Jolokia based metrics are less performant
anyways, then we can just use the metric APIs forever.

Thanks
TI





On Sun, Jun 25, 2017 at 6:29 PM, S G <sg...@gmail.com> wrote:

> Hi,
>
> The API admin/metrics
> <https://cwiki.apache.org/confluence/display/solr/Metrics+Reporting#
> MetricsReporting-MetricsAPI>
> in
> 6.x version of Solr seems to be very good.
> Is it performance friendly as well?
>
> We want to use this API to query the metrics every minute or so from all
> Solr nodes and push to grafana.
> How does this compare with the performance overhead of reading JMX metrics
> via Jolokia?
>
> Rest API is surely easier to understand and parse.
> However it involves making a REST call that will pass through jetty,
> probably take up a thread for each request? etc.
> Is Jolokia lighter-weight in this respect?
>
> Some recommendation on this would be great.
>
> Thanks
> SG
>