There are three scenarios where Kieker configuration parameters can be used Java applications and must be configured on command line or startup scripts.
Normal Java application without Kieker parts which should be instrumented and observed
Java applications which has already Kieker integrated or woven in with AspectJ
Java application which uses Kieker directly and accepts an Kieker property file
This works largely like the second option. However, you have to add the Kieker agent to the java invocation.
In case you have an application which need Kieker configuration
parameters set, but which does not provide a command line option for
such configuration file can add
-Dkieker.monitoring.configuration=$CONFIGUATION_FILE to the java
invocation statement. In many
gradle-based
builds this can be achieved by using the *_OPTS environment
variable. The * represents the name of the tool.
Add your configuration parameters to the application’s configuration file