Mailing-List: contact dev-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
Date: Wed, 15 Mar 2017 17:36:41 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: dev@geode.apache.org
Message-ID: <JIRA.13038524.1485549280000.29074.1489599401710@Atlassian.JIRA>
In-Reply-To: <JIRA.13038524.1485549280000@Atlassian.JIRA>
References: <JIRA.13038524.1485549280000@Atlassian.JIRA> <JIRA.13038524.1485549280365@jira-lw-us.apache.org>
Subject: [jira] [Commented] (GEODE-2379) Document new behavior of export
 logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 15 Mar 2017 17:36:51 -0000


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

ASF subversion and git services commented on GEODE-2379:
--------------------------------------------------------

Commit f329f4a54c2bdfa254f2a9a9be1f535a9899cd85 in geode's branch refs/heads/develop from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=f329f4a ]

GEODE-2379 Document new behavior of export logs
This closes #425


> Document new behavior of export logs
> ------------------------------------
>
>                 Key: GEODE-2379
>                 URL: https://issues.apache.org/jira/browse/GEODE-2379
>             Project: Geode
>          Issue Type: Sub-task
>          Components: docs
>            Reporter: Joey McAllister
>            Assignee: Dave Barnes
>
> the new command help: 
> NAME
>     export logs
> IS AVAILABLE
>     false
> SYNOPSIS
>     Export the log files for a member or members.
> SYNTAX
>     export logs [--dir=value] [--group=value(,value)*] [--member=value(,value)*] [--log-level=value] [--only-log-level=value] [--merge-log=value] [--start-time=value] [--end-time=value] [--logs-only(=value)?] [--stats-only(=value)?]
> PARAMETERS
>     dir
>         Local directory to which log files will be written. This is only used when you are exporting logs using http connection. If not specified, user.dir will be used.
>         Required: false
>     group
>         Group of members whose log files will be exported.
>         Required: false
>     member
>         Name/Id of the member whose log files will be exported.
>         Required: false
>     log-level
>         Minimum level of log entries to export. Valid values are: fatal, error, warn, info, debug, trace and all.  The default is "INFO".
>         Required: false
>         Default (if the parameter is not specified): INFO
>     only-log-level
>         Whether to only include those entries that exactly match the --log-level specified.
>         Required: false
>         Default (if the parameter is not specified): false
>     merge-log
>         Whether to merge logs after exporting to the target directory.  -- deprecated
>         Required: false
>         Default (if the parameter is not specified): false
>     start-time
>         Log entries that occurred after this time will be exported. The default is no limit. Format: yyyy/MM/dd/HH/mm/ss/SSS/z OR yyyy/MM/dd
>         Required: false
>     end-time
>         Log entries that occurred before this time will be exported. The default is no limit. Format: yyyy/MM/dd/HH/mm/ss/SSS/z OR yyyy/MM/dd
>         Required: false
>     logs-only
>         Whether to only export logs
>         Required: false
>         Default (if the parameter is specified without value): true
>         Default (if the parameter is not specified): false
>     stats-only
>         Whether to only export statistics
>         Required: false
>         Default (if the parameter is specified without value): true
>         Default (if the parameter is not specified): false
> changes are:  --dir is not required anymore. added logs-only and stats-only options. --merge-log is deprecated, group and member can be comma separated strings.
> Also note down in the docs: when this command is executed over jmx, the exported logs will be saved as exportedlogs_xxx.zip in the connected locator's working directory. If executed over http, the zip will be saved in specified dir in the user's client machine.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)