[jboss-jira] [JBoss JIRA] (WFCORE-4032) Add CLI request logging option

Martin Stefanko (JIRA) issues at jboss.org
Tue Aug 14 08:27:01 EDT 2018


Martin Stefanko created WFCORE-4032:
---------------------------------------

             Summary: Add CLI request logging option
                 Key: WFCORE-4032
                 URL: https://issues.jboss.org/browse/WFCORE-4032
             Project: WildFly Core
          Issue Type: Enhancement
          Components: CLI
    Affects Versions: 6.0.0.Alpha5
            Reporter: Martin Stefanko
            Assignee: Martin Stefanko
            Priority: Minor


We should improve a logging capabilities of CLI. CLI logging is disabled by default, but it can be enabled by altering the jboss-cli-logging.properties.

Here is my test scenario.
{noformat}
[pkremens at localhost bin]$ ./jboss-cli.sh -c
[standalone at localhost:9990 /] /system-property=foo:add(value=bar bar)
{"outcome" => "success"}
[standalone at localhost:9990 /] shutdown 
{noformat}

Set CLI logger level to ALL (logger.org.jboss.as.cli.level=ALL) to see all logs produced by CLI

actual content of jboss-cli.log - only server response is logged
{noformat}
13:45:48,041 DEBUG [org.jboss.as.cli.CommandContext] connecting to localhost:9990 as null
13:46:04,033 INFO  [org.jboss.as.cli.CommandContext] {"outcome" => "success"}
{noformat}

I can imagine content like following could be helpful for troubleshooting
{noformat}
...
<TIME> <LEVEL>  [org.jboss.as.cli.CommandContext] /system-property=foo:add(value=bar bar)
{
    "address" => [("system-property" => "foo")],
    "operation" => "add",
    "value" => "barbar"
}
<TIME> <LEVEL>  [org.jboss.as.cli.CommandContext] {"outcome" => "success"}
{noformat}

AFAICT the only possibility to get the actual CLI requests in raw form is to map the content of $HOME/.jboss-cli-history file with configuration history or audit log now.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list