[jira] [Commented] (SOLR-7796) Implement a gather support info button
[ https://issues.apache.org/jira/browse/SOLR-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652014#comment-14652014 ] Alexandre Rafalovitch commented on SOLR-7796: - Great idea. Might be also useful to include number of records in each shard. This would give overall data size as well as showing off some dis-balances in routing. 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7796) Implement a gather support info button
[ https://issues.apache.org/jira/browse/SOLR-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7796) Implement a gather support info button
[
https://issues.apache.org/jira/browse/SOLR-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628672#comment-14628672
]
Stefan Matheis (steffkes) commented on SOLR-7796:
-
I absolutely like the idea!
While [~elyograg], [~eribeiro] and i were throwing ideas around in #solr, the
following things came up - which i'm just including here for reference:
{code}15.2129 @ steffkes elyograg: +1 on SOLR-7796, gathering support
relevant information is a really nice idea!
15.2133 @ elyograg yep. It's somewhat painful to tailor each request for
info to the situation, and I hate to have people spend a lot of time gathering
info that might ultimately
turn out to be useless ... so instead of relying on
their skill level or taking up tons of their time, do it instantly.
15.2141 eribeiro elyograg: steffkes: if no one more knowledgeable
contributor picks up SOLR-7796 in a day or two, I am gonna try to take a stab
at it. ;-)
15.2147 @ steffkes eribeiro: nice! if you need help .. feel free to ping
me or Upayavira
15.2148 eribeiro okay, thanks. :)
15.2149 @ steffkes implementation might differ a bit, depending on where
you're going to include it - but the basic idea should be the same for both, i
guess
15.2150 @ steffkes eribeiro: true that. while reading i was thinking if
it might be possible to solve it in one shot .. but we're indeed talking about
a few things that might be
interesting here ..
15.2150 @ steffkes like the whole schema .. in case we stick to something
text based .. that might get a loong document
15.2150 eribeiro yeah...
15.2151 eribeiro +1 about the zip thing then
15.2151 @ steffkes which we have to do on the server, rather then the
client side .. :/
15.2151 @ steffkes otherwise i wouldn't bet that it's easy to implement.
generate a zip in everyones browser .. i don't know :D
15.2152 eribeiro haha, let's find out. :)
15.2152 @ steffkes on the other hand .. just thinking out load: if
pressing that button would open a modal layer .. which contains a bunch of
checkboxes .. where you could decide
*what* to actually prepare for export?
15.2153 @ steffkes i mean, even if someone is going to include his schema
.. it's not really a problem. it's just a few lines of text. we he/she is
already used to
15.2154 @ steffkes pastie.org has a nice feature where you can use ## at
the beginning of a line to indicate a section, like this one:
http://pastie.org/10295224
15.2154 eribeiro that would be awesome. something alike tools like
phpMySQLAdmin does when backing up and restoring the DB.
15.2154 @ steffkes not sure if apaste.info does support something like
that as well
15.2155 @ steffkes and .. to go really crazy .. we could probably try to
include the possibility to directly *post* this content to a paste-site. that
would be reeeaaallly nifty
15.2155 @ steffkes like .. hitting a button and getting back a url you
can share, which includes all the things you've previously checked :o
15.2156 eribeiro wow, indeed.
15.2156 @ steffkes but .. i don't want to set the bar to high :D
15.2157 @ steffkes just throwing ideas around while thinking about it
15.2158 eribeiro haha, got it. I will start small and see what I get. :)
15.2158 @ steffkes the last thing (posting directly) might require a
change for apaste.info but only easy things like additional headers, so that a
javascript client is allowed to go
crossdomain, which is normally forbidden by the
browsers security policy{code}
just to be sure that the last idea (POSTing it directly somewhere) isn't
entirely out of reach, i dropped by #asinfra's hipchat and talked with
[~humbedooh] about the idea:
{quote}10:01 Stefan Matheis we were just throwing ideas around in #solr over at
freenode. Shawn come up with an idea to include a gather support
information-button in the admin ui
10:02 Daniel Gruno (Humbedooh) ehm..
10:02 Stefan Matheis based on the my idea was we could probably include a
possibility to directly POST this information to apaste.info - which would
require a rather small change on apaste.info's configuration
10:02 Daniel Gruno (Humbedooh) ah
10:02 Stefan Matheis ;
10:02 Gavin McDonald (McDuck) @Humbedooh is yoiur man
10:02 Daniel Gruno (Humbedooh) well, we _could_ add a token account
10:02 Stefan Matheis like enabling CORS header
10:02 Daniel Gruno (Humbedooh) or err
10:02 Daniel Gruno (Humbedooh) with a token
10:02 Daniel Gruno (Humbedooh) role account
10:02 Daniel Gruno (Humbedooh) oh, sure, CORS should be easy enough
10:02 Daniel Gruno (Humbedooh) that's just a matter of editing the yaml for the
TLS terminator
10:02 Daniel Gruno (Humbedooh) in fact, it's actually all something you'd do on
that machine
10:02
[jira] [Commented] (SOLR-7796) Implement a gather support info button
[ https://issues.apache.org/jira/browse/SOLR-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628819#comment-14628819 ] Shawn Heisey commented on SOLR-7796: Some other things discussed in IRC were potential confidentiality concerns. One idea put forth was to give the user a list of checkboxes to choose what info they want to include. For the first button I mentioned above (the one that generates a text structure for copy/paste), I don't like the idea of giving the user the option to exclude info. My reasons: That info will typically contain very little that might be confidential, and a person in a support role will be able to help more if all that info is included. I think it's sufficient to include a warning telling the user that they should review the information for anything confidential and redact it before sending it to anyone. For the second button, the one that includes more comprehensive info in a downloadable file, confidential info is far more likely, and in that situation it is prudent to give the user a chance to exclude anything sensitive, like their config file(s) for the dataimport handler. 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
