github.com/Cloud-Foundations/Dominator@v0.3.4/cmd/logtool/README.md (about)

     1  # logtool
     2  A utility to control the built-in logger for services.
     3  
     4  The *logtool* utility connects to running services to control their built-in
     5  logging subsystem.
     6  
     7  ## Usage
     8  *Logtool* supports several sub-commands. There are many command-line flags
     9  which provide parameters for these sub-commands. The most commonly used
    10  parameter is `-loggerHostname` which specifies the service instance to control.
    11  At startup, *logtool* will read parameters from the
    12  `~/.config/logtool/flags.default` and `~/.config/logtool/flags.extra` files.
    13  These are simple `name=value` pairs. The basic usage pattern is:
    14  
    15  ```
    16  logtool [flags...] command [args...]
    17  ```
    18  
    19  Built-in help is available with the command:
    20  
    21  ```
    22  logtool -h
    23  ```
    24  
    25  Some of the sub-commands available are:
    26  
    27  - **debug**: inject a debug log message at the specified level
    28  - **print**: inject a log message
    29  - **set-debug-level**: set the debug logging level for service to the level
    30                         specified
    31  - **watch**: watch for subsequent log messages generated by the service and
    32               write to stdout. Debug messages above the specified level are
    33               shown. If the *loggerHostname* FQDN resolves to multiple addresses
    34               all instances will be connected to and their logs displayed
    35  
    36  ## Security
    37  The various services in this ecosystem restrict RPC access using TLS client
    38  authentication. *Logtool* will load certificate and key files from the
    39  `~/.ssl` directory. *Logtool* will present these certificates to the
    40  service. If one of the certificates is signed by a certificate authority
    41  that the service trusts, the service will grant access.