[ https://issues.apache.org/jira/browse/GEODE-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850451#comment-15850451 ]
Jared Stewart edited comment on GEODE-2267 at 2/2/17 8:37 PM: -------------------------------------------------------------- Per discussion on the dev list, we have decided to implement this as a change to the existing `export logs` command rather than as a new `export artifacts` command. The default behavior should be to include stat files, but to provide an option like `--exclude-stats`. We likely also want to run `export stacktrace` automatically for a user as the first step of running `export logs` to make the support/troubleshooting processes as easy as possible. was (Author: jstewart): Per discussion on the dev list, we have decided to implement this as a change to the existing `export logs` command rather than as a new `export artifacts` command. The default behavior should be to include stat files, but to provide an option like `--exclude-stats`. We likely also want to run `export stacktrace` automatically for a user as the first step of running `export logs` to make the support/troubleshooting processes as easy as possible. > Add gfsh command to export all cluster artifacts > ------------------------------------------------ > > Key: GEODE-2267 > URL: https://issues.apache.org/jira/browse/GEODE-2267 > Project: Geode > Issue Type: New Feature > Components: configuration, gfsh > Reporter: Diane Hardman > Labels: ExportClusterArtifacts, export, gfsh, logging, statistics > > We would like a single gfsh command to collect and export all logfiles and > stat files into a single package that will be returned to the gfsh client > machine. This package (zipfile) can then be saved and attached to emails and > Jira tickets to help evaluate the Geode cluster status. -- This message was sent by Atlassian JIRA (v6.3.15#6346)