We are running 6.5.0 in prod and New Relic is not showing cache stats. I think this means it cannot find the MBeans.
I gleaned that from the discussion here: https://discuss.newrelic.com/t/solr-data-not-appearing-in-apm-solr-tabs-caches-updates/37507/4 <https://discuss.newrelic.com/t/solr-data-not-appearing-in-apm-solr-tabs-caches-updates/37507/4> https://docs.newrelic.com/docs/agents/java-agent/troubleshooting/solr-data-not-appearing-apm-solr-tab-java <https://docs.newrelic.com/docs/agents/java-agent/troubleshooting/solr-data-not-appearing-apm-solr-tab-java> wunder Walter Underwood [email protected] http://observer.wunderwood.org/ (my blog) > On Mar 3, 2017, at 7:26 AM, Andrzej Białecki > <[email protected]> wrote: > > >> On 2 Mar 2017, at 16:45, Otis Gospodnetić <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi, >> >> While I love all the new metrics in Solr, I think metrics should be treated >> like code/features in terms of how backwards compatibility/deprecation is >> handled. Otherwise, on upgrade, people's monitoring breaks.... and >> monitoring is kind of important... >> Note: Looks like recent Solr metrics changes broke/changed >> previously-existing MBeans... >> Don't have the details about what was changed and how exactly, but I see >> people using Sematext SPM for monitoring Solr are reporting this with Solr >> 6.4.1. >> > > Otis, > > Yes, we’ll be more careful, but we need proper feedback too. My understanding > was that SOLR-10035 addressed this by adding back-combat registration under > old names. Are you saying there are still some issues in 6.4.1? Can you > please be more specific? 6.4.2 is almost out, but if it’s something serious > then we should fix it. > >> >> Otis >> -- >> Monitoring - Log Management - Alerting - Anomaly Detection >> Solr & Elasticsearch Consulting Support Training - http://sematext.com/ >> <http://sematext.com/> >> >
