container. • Dynamic Configuration: Apache Karaf provides a set of commands focused on managing its own configuration. All configuration files are centralized in the etc folder. Any change in a configuration default, all Apache Karaf files are "gathered" in one directory: KARAF_HOME . You can define your own directory layout, by using some Karaf environment variables: • KARAF_DATA is the location of the data command) • log:list displays all loggers and level (alias to log:get ALL command) You can create your own aliases in the etc/shell.init.script file. Key binding Like on most Unix environments, the Karaf

• all other values (like any) will be part of the collected data. It means that you can add your own custom data, and easily create queries bases on this data. You can also filter the lines read from target=(parserId=regex) Apache Karaf Decanter 2.x - Documentation - 5 CUSTOM PARSER You can write your own parser by implementing the org.apache.karaf.decanter.api.parser.Parser interface and declare it into object.name.. • any other values will be part of the collected data. It means that you can add your own property if you want to add additional data, and create queries based on this data. • the operation

default, all Apache Karaf files are "gather" in one directory: the KARAF_HOME. You can define your own directory layout, by using some Karaf environment variables: • KARAF_DATA is the location of the command) • log:list displays all loggers and level (alias to log:get ALL command) You can create your own aliases in the etc/shell.init.script file. Key binding Like on most Unix environment, Karaf console install the bundles. Again, these "dependency" bundles may require other bundles to satisfy their own dependencies. More over, typically, an application requires configuration (see the Configuration

• all other values (like any ) will be part of the collected data. It means that you can add your own custom data, and easily create queries bases on this data. For instance, instead of the log collector object.name. . • any other values will be part of the collected data. It means that you can add your own property if you want to add additional data, and create queries based on this data. You can retrieve a larger and shared production platform, we recommend to dedicate a Elasticsearch instance on its own JVM. It allows you some specific tuning for elasticsearch. Another acceptable configuration is to

default as it can have side effects (especially when a node is stopped). Enabling listeners is at your own risk. The nodes list could be discovered (using unicast or multicast), or "staticly" defined (using in the etc/org.apache.karaf.cellar.node.cfg configuration file. NB: enabling listeners is at your own risk. We encourage you to use cluster dedicated commands and MBeans to manipulate the resources on

default as it can have side effects (especially when a node is stopped). Enabling listeners is at your own risk. The nodes list could be discovered (using unicast or multicast), or "static" defined (using in the etc/org.apache.karaf.cellar.node.cfg configuration file. NB: enabling listeners is at your own risk. We encourage you to use cluster dedicated commands and MBeans to manipulate the resources on

simple filesystem backend. As the Cave backend is designed in a plugin way, you can implement your own backend (for instance, JDBC or LDAP backend). • Repository Metadata Generation: Cave creates the

simple filesystem backend. As the Cave backend is designed in a plugin way, you can implement your own backend (for instance, JDBC or LDAP backend). • OBR Metadata Generation: Karaf Cave automatically