contained in a script • shell:stack-traces-print prints the full stack trace in the console when the execution of a command throws an exception • shell:tac captures the STDIN and returns it as a string • defined in etc/ org.apache.karaf.log.cfg . You can also change the pattern dynamically (for one execution) using the -p option: The pattern is a regular Log4j pattern where you can use keywords like %d Without the query argument, the config:list command display all configurations, with PID, attached bundle and properties defined in the configuration: The query argument accepts a query using a LDAP

list of all configurations available, or the properties in a given configuration (PID). Without the query argument, the config:list command display all configurations, with PID, attached bundle and properties fileinstall.filename = file:/opt/ apache-karaf-3.0.0/etc/org.apache.karaf.log.cfg ... The query argument accepts a query using a LDAP syntax. For instance, you can display details on one specific configuration 0)(!(version>=4.0.0))) [81.0] osgi.wiring.package; (&(osgi.wiring.package=org.jboss.netty.handler.execution)(version>=3.4.0)(!(version>=4.0.0))) [81.0] osgi.wiring.package; (&(osgi.wiring.package=org.mortbay

(attribute values) are send to the appenders. In addition, the JMX collector also supports the execution of operations on dedicated ObjectName that Apache Karaf Decanter 2.x - Documentation - 6 you configure Decanter Scheduler). This collector executes operating system commands (or scripts) and send the execution output to the appenders. The decanter-collector-system feature installs the system collector: name=system_command The collector will execute each command described in this file, and send the execution output to the appenders. For instance, if you want to periodically send the free space available

Decanter Scheduler). This collector executes operating system commands (or scripts) and send the execution output to the appenders. The decanter-collector-system feature installs the system collector: using the format: The collector will execute each command described in this file, and send the execution output to the appenders. For instance, if you want to periodically send the free space available level query and fetch threshold logging. For Elasticsearch 2.x: #index.search.slowlog.threshold.query.warn: 10s #index.search.slowlog.threshold.query.info: 5s #index.search.slowlog.threshold.query.debug:

command execution have elapsed, the list is moved to a blocking queue from which the result can be retrieved. The following code snippet shows what happens when a command is sent for execution: public

command execution have elapsed, the list is moved to a blocking queue from which the result can be retrieved. The following code snippet shows what happens when a command is sent for execution: public