Skip to content
Reiner Jung edited this page Feb 6, 2025 · 8 revisions

Model-driven instrumentation allows you to specify instrumentation for a software system in a unified way regardless the underlying technologies. While this approach is still under development, we already realized two languages addressing the issue. First, we developed an implementation independent notation for monitoring data, called the instrumentation record language (IRL). And second, we started to develop an instrumentation aspect language (IAL) which allows you to define the monitoring advice and join points.

Instrumentation Record Language

Instrumentation Aspect Language

  • Developer Documentation
    • Feature overview
    • Grammar overview
    • Semantics
    • Writing your own generator

Kieker Architecture Visualization

The Kieker Architecture Visualization can display Kieker architecture models. Thy can be colored following a coloring schema utilizing tags applied to model elements.

The color schema are stored in a file color-model.map in the architecture model director. Separate colors can be defined for components and operations, as well as, tags attached to model elements. The following example depicts a mapping for model tags static, dynamic and the combination of static and dynamic. The mapping defines first colors for static components with two different colors. These two colors are use to give components different colors depending on the depth of nesting.

component: static=#a0ffa0, #90f090
component: dynamic=#a0a0ff, #9090f0
component: static, dynamic=#ffffff, #d0d0d0
operation: static=#d0ffd0, #c0ffc0
operation: dynamic=#d0d0ff, #c0c0ff
operation: static, dynamic=#f0f0f0, #e0e0e0
  • Diagram types
    • Assembly Diagram
    • Deployment Diagram

Both supports showing operations and data storage, like common blocks in Fortran, global variables or databases.

Clone this wiki locally