[
https://issues.apache.org/jira/browse/SOLR-10531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065018#comment-16065018
]
Walter Underwood commented on SOLR-10531:
-----------------------------------------
New Relic fixed their problem. The fix is in the 3.40.0 Java agent.
https://docs.newrelic.com/docs/release-notes/agent-release-notes/java-release-notes
> JMX cache beans names / properties changed in 6.4
> -------------------------------------------------
>
> Key: SOLR-10531
> URL: https://issues.apache.org/jira/browse/SOLR-10531
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: metrics
> Affects Versions: 6.4, 6.5
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Attachments: branch_6_3.png, branch_6x.png
>
>
> As reported by [~wunder]:
> {quote}
> New Relic displays the cache hit rate for each collection, showing the query
> result cache, filter cache, and document cache.
> With 6.5.0, that page shows this message:
> New Relic recorded no Solr caches data for this application in the last
> 24 hours
> If you think there should be Solr data here, first check to see that JMX
> is enabled for your application server. If enabled, then please contact
> support.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
