Open rju opened 2 weeks ago
author Florian Fittkau -- Thu, 1 Aug 2013 16:21:42 +0200
Could also be part of the topic "Evaluation der Vollinstrumentierung von Software-Systemen":
PDF
author André van Hoorn -- Sun, 24 Nov 2013 11:32:12 +0100
As reported in http://dx.doi.org/10.1109/SISY.2013.6662557, DiSL has been used together with Kieker as part of the work on the Kieker-based DProf approach.
author Jan Waller -- Sun, 24 Nov 2013 11:40:29 +0100
We also tested a DISL probe with Kieker (will be added to master soon).
The performance is similar (and slightly below) an AspectJ based probe.
However DISL offers possibilities for additional probe lcoations, not possible with AspectJ
author Jan Waller -- Mon, 2 Dec 2013 15:26:37 +0100
I added a simple DISL probe to Kieker.
But it is not really tested and configured.
However, this probe can serve as an example to create own probes for DISL.
see: fa52366344470bb6316f66daba3cc3659c14eaa1
JIRA Issue: KIEKER-1000 Evaluation of DiSL as an instrumentation technology for Kieker Original Reporter: Andre van Hoorn
We currently make use of various (AOP-based) instrumentation technologies for Java instrumentation, e.g., AspectJ, Servlet filters, Spring interceptors, etc. DiSL is a new (domain-specific) language/library/tool for Java byte code instrumentation, which is developed on top of the low-level bytecode manipulation library ASM. As opposed to AspectJ, DiSL allows the instrumentation at the level of Java bytecode instructions (e.g., loops, operators) and to extend the available set of "advices" (this term is not used in the DiSL context). It would be interesting to see how DiSL can be used for Kieker monitoring probes. Or one could develop DiSL-based probes for tracing and compare their overhead with the AspectJ-based probes. Also, model-based instrumentation with DiSL as a target language could be interesting.
This topic probably is not a topic for itself but could be integrated into a topic aiming to investigate a new dynamic analysis approach or in the context of (micro)benchmarking.
Checklist: