XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Minor
    • 7.2.0.CD13
    • 7.0.0.GA
    • CLI
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              mstefank Martin Stefanko
              pkremens@redhat.com Petr Kremensky (Inactive)
              Erich Duda Erich Duda (Inactive)
              Erich Duda Erich Duda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: