You are viewing an older version of this section. View current production version.
MemSQL Ops has been deprecated
Please follow this guide to learn how to migrate to SingleStore tools.
Generate a comprehensive report that contains diagnostic information about your entire MemSQL cluster for troubleshooting purposes.
The size of the log files to be collected can be specified, as well as the MemSQL nodes from which information should be collected.
The report generated is compressed into a file called
usage: memsql-ops report [--settings-file SETTINGS_FILE] [--async] [--tracelog-mb TRACELOG_MB] [--include-log-archives] [--exclude-schema] [--memsql-ids [MEMSQL_IDS [MEMSQL_IDS ...]]] [--timeout TIMEOUT] Generate a report that contains diagnostic information for MemSQL Ops. optional arguments: --settings-file SETTINGS_FILE A path to a MemSQL Ops settings.conf file. If not set, we will use the file in the same directory as the MemSQL Ops binary. --async If this option is true, we will exit without waiting for the report to be fully built. --tracelog-mb TRACELOG_MB If specified, we will truncate MemSQL tracelogs such that all of the tracelogs combined will be less than this size. The default value is 50. --include-log-archives Include the log_archives directory from each agent. --exclude-schema If specified, we will not include any information about MemSQL database and table schemas in the report. --memsql-ids [MEMSQL_IDS [MEMSQL_IDS ...]] A list of MemSQL IDs for which we will gather tracelogs. If not specified, we will gather tracelogs for all MemSQL nodes. --timeout TIMEOUT If specified, we will wait at most this many seconds for a report to be built for each MemSQL Ops agent.