[jira] [Commented] (SOLR-9587) Script for creating a redacted tech support package

["Shawn Heisey (JIRA)" <ji...@apache.org>]

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

Shawn Heisey commented on SOLR-9587:
------------------------------------

SolrCLI would also be able to reach into zookeeper for cloud installs to pull out cloud-wide config and collection state information, but the locally stored info (core.properties, etc) might only be for the solr instance where the script was run.  I notice that the "Files" API only looks in conf ... maybe it needs extending so it can obtain other things like core.properties.

> Script for creating a redacted tech support package
> ---------------------------------------------------
>
>                 Key: SOLR-9587
>                 URL: https://issues.apache.org/jira/browse/SOLR-9587
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: scripts and tools
>            Reporter: Shawn Heisey
>            Priority: Minor
>
> When users need help with Solr from the project, relevant config and log information from their install is usually the best way that we can help them.  If we had an easy way to gather all useful information into a single compressed file that a user could place onto a file sharing site, we'd be in awesome shape.
> If the script was smart enough to try and keep the final size of the package under 1MB, which might be challenging until we have a better handle on logfile rotation, most users would be able to share the package using Apache's own pastebin, which can be found here: http://apaste.info
> If we pass control to the SolrCLI Java class as part of the script functionality, we can also automatically redact any *config* information that we *know* to be sensitive, like passwords.  Automatic redaction of logfiles might be nearly impossible, but we should be making efforts in our standard INFO-level logging to never log anything most users would consider to be sensitive.  If the user bumps to DEBUG or TRACE, all bets are off.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org