Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
The monitoring data is gathered by the Kieker monitoring component. At the moment, we are only supporting to monitor Java applications. Other languages will appear shortly.
Version 1.2.0 and later (latest version)
Download the monitoring example configuration.
Currently the following Kieker aspects are configured:
- aspectj.operationExecution.FullInstrumentationNoGetterAndSetter (Java application calls)
- aspectj.database.Fullinstrumentation (JDBC related database calls)
This set up is provided to instrument directly executed Java applications. The set up for application servers is under revision right now and will be released later.
- Start the monitoring:
The monitoring script is running until termination.
Choose the packages, which should be monitored
Exclude packages, which should not be monitored
<exclude within="org.apache.commons.logging..*" />
Change the name of the application
Change the ip address of the ExplorViz server
(only necessary, if the server and monitoring are running on different hosts)
Version 1.1.1 and earlier
This section deals with the monitoring configuration regarding to which components of the software are analyzed and afterwards visualized.
Download the monitoring component from here.
The monitoring configuration file aop.xml resides in the folder
META-INFwhich is stored in your application server’s (lib) folder.
Open the jar file with an extractor for example winzip or winrar. Navigate to the folder META-INF and extract the file aop.xml.
Hint: You can use an editor to open the file.
Open the extracted file aop.xml and update the
<include within="*"/>statement according to your needs. For instance replace it with:
<include within="com.ibatis..*" />to monitor only method calls in the com.ibatis package and its subpackages. Add further
<include within="more.packages..*“/>statements below to include more than one package. The mentioned statement and especially the last advice is shown in the picture below.
- After modifying the file just replace it in the jar file.
The ExplorViz configuration file explorviz.live_trace_processing.default.properties also resides in the file explorviz-monitoring.jar which is stored in your server’s lib folder.
Open the jar file with an extractor for example with winzip or winrar. Navigate to the META-INF folder and extract the file explorviz.live_trace_processing.default.properties.
Open the extracted file explorviz.live_trace_processing.default.properties and look up the the options in the table below.
Hint: You can use an editor to open the file. If you have formatting problems using windows editor alternatively use WordPad.
After modifying the file just replace it in the jar file.
|writer_target_ip||127.0.0.1||Defines the target ip where the analysis component/visualization server is running.|
|writer_target_port||10133||Defines the target port where the analysis component/visualization server is running.|
|writer_load_balancing_enabled||false||Used for cloud scaling. If true, the writer_target_ip paramter is ignored. Instead the monitoring queries the load balancer for an ip adress.|
||The name of the system belonging to the application|
|ip_address||one ip address of the server||The IP address of the server where the application is running|
|host_name||hostname of the server||The hostname of the server where the application is running|
||The displayed name of the application|
|programming_language||Java||The programming language of the application|