You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2017/03/14 21:32:41 UTC

[jira] [Updated] (GEODE-2634) gfsh export logs command should be able to filter logs on log-level

     [ https://issues.apache.org/jira/browse/GEODE-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Swapnil Bawaskar updated GEODE-2634:
------------------------------------
    Description: 
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}

  was:
If I try to filter the exported logs by a log level, I get the following exceptions:
{{{
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
}}}


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