[
https://issues.apache.org/jira/browse/SOLR-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651942#comment-14651942
]
Shawn Heisey commented on SOLR-7796:
------------------------------------
I saw an update on SOLR-7555, and the issue description got me thinking.
If the basic info had a list of cores with the index size, volume size, and
free space for each one, that would be really nice. Having a data point on the
dashboard (and in the basic support info) for the total disk space consumed by
all indexes would be really nice. If we can separately calculate the size of
inactive transient cores, that would be very nice.
You might be wondering why I would be interested in space information for every
core. There have been questions on the mailing list about how to have
different cores put their index data on different filesystems, so I know that a
few users out there will have that setup. We could put information on the
dashboard for volume size and free space for the solr home directory, which
would be enough for the vast majority of users.
> Implement a "gather support info" button
> ----------------------------------------
>
> Key: SOLR-7796
> URL: https://issues.apache.org/jira/browse/SOLR-7796
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Reporter: Shawn Heisey
> Priority: Minor
>
> A "gather support info" button in the admin UI would be extremely helpful.
> There are some basic pieces of info that we like to have for problem reports
> on the user list, so there should be an easy way for a user to gather that
> info.
> Some of the more basic bits of info would be easy to include in a single file
> that's easy to cut/paste -- java version, heap info, core/collection names,
> directories, and stats, etc. If available, it should include server info
> like memory, commandline args, ZK info, and possibly disk space.
> There could be two buttons -- one that gathers smaller info into an XML,
> JSON, or .properties structure that can be easily cut/paste into an email
> message, and another that gathers larger info like files for configuration
> and schema along with the other info (grabbing from zookeeper if running in
> cloud mode) and packages it into a .zip file. Because the user list eats
> almost all attachments, we would need to come up with some advice for sharing
> the zipfile. I hate to ask INFRA for a file sharing service, but that might
> not be a bad idea.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
