Agreed. I tried to do my share of being a voice of maintaining backwards compatibility (register MBeans in old place still along with the new place) but apparently those changes weren't enough? Andrzej attempted to get your input https://issues.apache.org/jira/browse/SOLR-9947?focusedCommentId=15815089&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15815089 but you didn't respond or notice. If he hadn't '@' you, I would have as it's obvious you might have opinions on this matter ;-) And also related: https://issues.apache.org/jira/browse/SOLR-10035
On Thu, Mar 2, 2017 at 10:45 AM Otis Gospodnetić <[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 > -- > Monitoring - Log Management - Alerting - Anomaly Detection > Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > > -- Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker LinkedIn: http://linkedin.com/in/davidwsmiley | Book: http://www.solrenterprisesearchserver.com
