]
Martin Stefanko updated WFCORE-1583:
------------------------------------
Git Pull Request:
Enhance a CLI logging
---------------------
Key: WFCORE-1583
URL:
https://issues.jboss.org/browse/WFCORE-1583
Project: WildFly Core
Issue Type: Enhancement
Components: CLI
Reporter: Alexey Loubyansky
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@localhost bin]$ ./jboss-cli.sh -c
[standalone@localhost:9990 /] /system-property=foo:add(value=bar bar)
{"outcome" => "success"}
[standalone@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.