Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-1583

Enhance a CLI logging

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Minor Minor
    • 4.0.0.Alpha1
    • None
    • CLI
    • None

      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.

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

      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

      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"}

      I can imagine content like following could be helpful for troubleshooting

      ...
<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"}

      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.

              mstefank Martin Stefanko
              olubyans@redhat.com Alexey Loubyansky
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: