Hm, interesting. I'll check with my colleagues, but I haven't heard of issues with Solr JMX.
This works well: https://sematext.com/docs/integration/solr/ The agent itself is OSS: https://github.com/sematext/sematext-agent-java Configured with YML: https://github.com/sematext/sematext-agent-integrations Otis -- Monitoring & Alerting: Performance, Logs, Websites, APIs, SSL Certs.... Solr / Elasticsearch / OpenSearch Consulting Support Training - https://sematext.com/ On Fri, Mar 31, 2023 at 1:32 PM matthew sporleder <[email protected]> wrote: > In my experience solr jmx is weirdly unstable (mbeans disappear) and > it's better to query the api (CLUSTERSTATUS and friends). > > I wrote this ages ago for putting solr stats in datadog: > https://github.com/msporleder-work/dd-solrcloud > > On Fri, Mar 31, 2023 at 12:47 PM mtn search <[email protected]> wrote: > > > > Hello, > > > > We are transitioning from Solr 6 to Solr8/9. In the past we have enabled > > JMX in production to access MBean solr and jvm metrics. > > > > It appears a good bit has changed in terms of Solr metrics configuration > as > > I read the docs. However, it looks like enabling JMX is still an option > - > > https://solr.apache.org/guide/8_11/using-jmx-with-solr.html. > > > > However, according to this page: > > "We don’t recommend enabling remote JMX access in production, but it can > > sometimes be useful when doing performance and user-acceptance testing > > prior to going into production." > > > > What are the reasons for not enabling JMX in prod? Some of the metrics > are > > very useful in production. > > > > Thanks, > > Matt >
