CfP/CfPart: 9th Symposium on Software Performance (SSP 2018) will take place in Hildesheim

The 9th Symposium on Software Performance (SSP 2018) will take place in Hildesheim, Germany on November 8-9, 2018. It will be a joint meeting of the Descartes, Kieker, and Palladio research groups.

In addition to invited talks from practitioners and researchers, we welcome contributions from academic, scientific, or industrial contexts in the field of software performance, including but not limited to approaches employing Descartes, Kieker, and/or Palladio.

We solicit technical papers (maximum 3 pages) and extended abstracts for industry or experience talks (maximum 700 words).

Details are provided on the symposium web site: http://www.performance-symposium.org/

Kieker Trace Diagnosis 3.1.0 Released

We are pleased to anounce, that we released Version 3.1.0 of our Kieker Trace Diagnosis tool on June 02, 2018. As usual, you can download the release from https://github.com/kieker-monitoring/kieker-trace-diagnosis-ui/releases.

Some distinct and selected features:

  • Monitoring logs can now be read directly from a ZIP file.
  • The internal documentation has been improved.
  • The signatures of method calls are now taken from the after operation events rather than from the before operation events. For most users, this is not important. However, some applications take the methods’ results into account for the records, which means that their after operation events have an enriched method signature compared to their before operation events.

We also fixed some minor bugs. You can find the full changelog in the release archive.

Switcheroo: Changing the Kieker Configuration at Runtime

An article by Nils Ehmke (nils AT rhocas.de)

I think the original idea from Kieker was quite simple: put some monitoring probes into your application, add a properties file, and start the monitored application. After some time (or maybe after the application was stopped), you would collect the data and analyze it. Although this might be enough for some applications, this is not flexible enough for an enterprise business application. Such applications often have a different lifecycle compared to desktop applications, as they can not simply be restarted at any given time. In such scenarios one should be able to enable/disable the monitoring and even change the configuration, without the need to start and stop the whole application. Unfortunately, it is not possible to change the configuration of a started monitoring controller in Kieker. And the monitoring controller follows the singleton pattern, so we can’t do anything … or can we?

Continue reading

Kieker Trace Diagnosis 3.0.0 Released

We are pleased to anounce, that we released Version 3.0.0 of our Kieker Trace Diagnosis tool on January 23, 2018. As usual, you can download the release from https://github.com/kieker-monitoring/kieker-trace-diagnosis-ui/releases.

Some distinct and selected features:

  • Kieker Trace Diagnosis uses and requires now Java 9.
  • The monitoring log import has been further accelerated.
  • The tool supports now the writing and reading of ASCII monitoring logs.

We also fixed some minor bugs. You can find the full change log in the release archive.

Kieker Trace Diagnosis UI Release

An article by Nils Ehmke

While the Kieker Monitoring Framework is very suitable for collecting huge amount of monitoring data of your application, the question arises, how these monitoring logs can be analyzed. The tools shipped with Kieker (like the trace analysis tool) can help you only partially, because most of them build upon graph representations which tend to become huge, complex, and incomprehensible for larger applications.

To support the performance analysis of your application, we developed the Kieker Trace Diagnosis tool including a graphical user interface, which we want to introduce in this blog post.

Continue reading