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

ASF GitHub Bot commented on GEODE-2379:
---------------------------------------

GitHub user davebarnes97 opened a pull request:

    https://github.com/apache/geode/pull/425

    GEODE-2379 Document new behavior of export logs

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/davebarnes97/geode feature/GEODE-2379

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/geode/pull/425.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #425
    
----
commit 2439a0c7bf7024768fb0df648ba4f87160717a2f
Author: Dave Barnes <dbar...@pivotal.io>
Date:   2017-03-14T19:48:52Z

    GEODE-2379 Document new behavior of export logs

----


> 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
>
> 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)

Reply via email to