[ 
https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291422#comment-13291422
 ] 

Shawn Heisey commented on SOLR-3238:
------------------------------------

bq. Yes, use normal solr requests. If you turn on firebug (or equivalent) you 
can see what the UI is actually calling to get out the machine readable values. 
For cache stats, that will be something like: 
http://localhost:8983/solr/admin/mbeans?stats=true&wt=json

Awesome!  I can even use wt=xml and modify my Perl script for any differences 
between 3.x and 4.x.  I have just tried the same URL on 3.x and found that it 
works there, too.  My scripts currently use the stats.jsp and a couple of other 
URLs, not mbeans.  I will have to experiment, but do you know of any 
documentation that covers everything that's available?

With SolrJ, currently I can use ModifiableSolrParams and set qt to 
/admin/mbeans to make this work.  In the wake of issues like SOLR-3161, SolrJ 
might need a new way to specify the base URL path.
                
> Sequel of Admin UI
> ------------------
>
>                 Key: SOLR-3238
>                 URL: https://issues.apache.org/jira/browse/SOLR-3238
>             Project: Solr
>          Issue Type: Improvement
>          Components: web gui
>    Affects Versions: 4.0
>            Reporter: Stefan Matheis (steffkes)
>            Assignee: Stefan Matheis (steffkes)
>             Fix For: 4.0
>
>         Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch, 
> solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to