Kieker's main repository
Switch branches/tags
Clone or download
avanhoorn Merge pull request #189 from kieker-monitoring/KIEKER-1740-jms-creden…
…tials

KIEKER 1740: Added properties for username and password for the JMSWr…
Latest commit 1d02cb8 Sep 14, 2018
Permalink
Failed to load latest commit information.
.settings Merge branch 'KIEKER-1686-replace-kieker-logging-by-slf4j' into Mar 10, 2018
bin updated Kieker version Mar 16, 2018
config included and activated the custom PMD rules from TeeTime; May 4, 2018
gradle/wrapper updated Gradle wrapper to version 4.6 Mar 28, 2018
kieker-analysis KIEKER-1740: Lowered quality check threshold to the current levels. Aug 22, 2018
kieker-checkstyle-extension updated Gradle wrapper to version 4.6 Mar 28, 2018
kieker-common created a new option to save and transfer paramters for probes via th… Aug 2, 2018
kieker-documentation fixed all tests in analysis Mar 31, 2018
kieker-examples still debugging moobench Aug 23, 2018
kieker-extension-kafka included and activated the custom PMD rules from TeeTime; May 4, 2018
kieker-monitoring KIEKER-1740: Lowered quality check threshold to the current levels. Aug 22, 2018
kieker-tools KIEKER-1740: Lowered quality check threshold to the current levels. Aug 22, 2018
lib updated license file for TeeTime Mar 16, 2018
.checkstyle fixed checkstyle issues Sep 29, 2016
.gitattributes Introduce end-of-line normalization Nov 22, 2011
.gitignore removed jdt.core settings file from the ignore list Feb 21, 2018
.pmd changed joinpoint adressing Nov 21, 2017
HISTORY KIEKER-1562 release notes Sep 29, 2017
Jenkinsfile changes Jenkinsfile to support clover main report Feb 22, 2018
LICENSE adding original Apache license Sep 4, 2012
README.md add link to Jira Apr 9, 2018
TROUBLESHOOTING added TROUBLESHOOTING file Nov 22, 2016
build.gradle included and activated the custom PMD rules from TeeTime; May 4, 2018
build.properties renamed architecture model to type model and introduced assembly model Dec 19, 2016
gradle.properties KIEKER-1740: Lowered quality check threshold to the current levels. Aug 22, 2018
gradlew Upgrade gradle wrappers to version 4.0.1 and added a script to upgrad… Jul 26, 2017
gradlew.bat Updated gradle wrapper to version 3.3. Feb 3, 2017
kieker-eclipse-cleanup.xml updated Eclipse Settings export (minimal changes) Aug 16, 2012
kieker-eclipse-formatter.xml Correcting wrong formatter etc settings Apr 11, 2012
kieker-eclipse-templates.xml added comment templates for Kieker. Feb 14, 2018
kieker-eclipse.importorder updated Eclipse Settings export (minimal changes) Aug 16, 2012
settings.gradle monitoring and analysis for kafka in one Gradle/Eclipse project Oct 4, 2017

README.md

Kieker Monitoring Framework

The internal behavior of large-scale software systems cannot be determined on the basis of static (e.g., source code) analysis alone. Kieker provides complementary dynamic analysis capabilities, i.e., monitoring and analyzing a software system’s runtime behavior — enabling application performance monitoring and architecture discovery.

Detailed information about Kieker is provided at http://kieker-monitoring.net/

Usage

Kieker releases (stable, nightly, etc.) can be downloaded from our website's Download Section.

Documentation on how to use Kieker can be found here: Kieker Documentation

Development and Contribution

Gradle is used as the build tool. A build.gradle file is provided.

For issue tracking and bug reports, JIRA is used at https://kieker-monitoring.atlassian.net/.

Further instructions for developers are available at https://kieker-monitoring.atlassian.net/wiki/display/DEV/

Eclipse Setup for Contributors

  • Get Gradle support by installing the Eclipse plugin "Buildship: ..." in version 2 or above.
  • If you have already imported Kieker in Eclipse, delete it
  • Import Kieker in Eclipse by importing it as gradle project (Eclipse will also import all submodules automatically)
  • Whenever you change a build.gradle file, regenerate the .project and .classpath files for Eclipse by using "Gradle->Refresh Gradle Project"

Read our Confluence pages for more information.

Code Conventions

Read and follow our code conventions

Debugging and Logging Kieker's Execution

Kieker uses the Simple Logging Facade for Java (SLF4J) to support the logging framework of your choice. In order to see or store log messages, you need to bind a logging framework at deployment time.

A fast and flexible logging framework that can be used with SLF4J is Logback. In order to use it, you have to download it and add the following Jar files to the classpath:

  • logback-classic-<version>.jar
  • logback-core-<version>.jar

Moreover, you have to set up a logback.xml file for configuration and add its containing folder to the classpath. An example of such a file is provided below:

<configuration>
  <!-- log to console -->
  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    <encoder>
      <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
    </encoder>
  </appender>
  <!-- for logging to files see: https://logback.qos.ch/manual/appenders.html -->

  <!-- standard log level is "warn" -->
  <root level="warn">
    <appender-ref ref="STDOUT" />
  </root>
  <!-- set log level for TCP writer down to "info" -->
  <logger name="kieker.monitoring.writer.tcp" level="INFO" />
</configuration>

Logbacks official documentation provides more information on how to use and configure it.