Many customers have noted that it is very time consuming, especially in large node count environments, to gather the required riak-debug output and upload to the ticket and/or uploads.
A couple of things that might make things easier:
Automatic upload of debug output after riak-debug completion. The ability to automatically upload the debug output to uploads and/or customer specified location for processing. This could be a default off case and perhaps an additional /etc/riak/riak-debug.conf file that could contain customer information and credentials to be included in the riak-debug output and used in secure upload process.
Ability to cron running of riak-debug. Having riak-debug run on a set schedule may be helpful for customers to keep track of configuration settings, load and point in time comparisons. When paired with the automatic upload feature, this would allow for cluster health check automation the customer may wish to do.
Change default riak debug output to also include the date/time that the output was taken. This would allow customers to upload riak-debug output without worrying about over-writing or creating new directories for analysis. It would also allow for fairly easy rotation tools to be put in place to archive or remove older debug output.
Ability for riak-debug to coordinate with other nodes in the cluster to gather/trigger riak-debug on other nodes in the cluster in a safe way. This may require additional SSL setup and/or rpc calls which may not be wise on a cluster that is already at the point of overload and may not retrieve the needed debugs due to partitioning, etc.
Many customers have noted that it is very time consuming, especially in large node count environments, to gather the required riak-debug output and upload to the ticket and/or uploads.
A couple of things that might make things easier:
riak-debugcompletion. The ability to automatically upload the debug output to uploads and/or customer specified location for processing. This could be a default off case and perhaps an additional /etc/riak/riak-debug.conf file that could contain customer information and credentials to be included in the riak-debug output and used in secure upload process.riak-debugto coordinate with other nodes in the cluster to gather/triggerriak-debugon other nodes in the cluster in a safe way. This may require additional SSL setup and/or rpc calls which may not be wise on a cluster that is already at the point of overload and may not retrieve the needed debugs due to partitioning, etc.