[
https://issues.apache.org/jira/browse/GEODE-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925051#comment-15925051
]
Swapnil Bawaskar edited comment on GEODE-2634 at 3/14/17 9:32 PM:
------------------------------------------------------------------
It looks like this is just a matter of fixing the auto complete. gfsh help for
export logs shows the log levels as: {{Valid values are: fatal, error, warn,
info, debug, trace and all}} however, auto complete on the command displays the
following log levels:
{noformat}
gfsh>export logs --dir=tmp --log-level=
=all =finest =finer =fine =config =info =warning
=error =severe =none
{noformat}
was (Author: swapnil.bawaskar):
It looks like this is just a matter of fixing the auto complete. gfsh help for
export logs shows the log levels as: {{Valid values are: fatal, error, warn,
info, debug, trace and all}} however, auto complete on the command displays the
following log levels:
{{{
gfsh>export logs --dir=tmp --log-level=
=all =finest =finer =fine =config =info =warning
=error =severe =none
}}}
> gfsh export logs command should be able to filter logs on log-level
> -------------------------------------------------------------------
>
> Key: GEODE-2634
> URL: https://issues.apache.org/jira/browse/GEODE-2634
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh
> Reporter: Swapnil Bawaskar
>
> If I try to filter the exported logs by a log level, I get the following
> exceptions:
> {noformat}
> gfsh>export logs --dir=tmp --log-level=config
> Invalid log level: config
> gfsh>export logs --dir=tmp --log-level=config
> Invalid log level: config
> gfsh>export logs --dir=tmp --log-level=warning
> Invalid log level: warning
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
