...
Feature | New Kieker Analysis | Old Kieker Analysis/Trace Analysis Tool | |
---|---|---|---|
Pipe-and-Filter framework | TeeTime | Kieker´s old internal one | |
Pipe-and-Filter Configuration |
| Dynamic class in the Trace Analysis Tool that creates a Configuration based on the user´s input. This class is very large | |
Command Line Interface | currently not | yes | |
GUI | currently not | yes | |
Handling of Monitoring Records |
| should support all Kieker Monitoring Records ![]() | |
Analysis models | Implemented with Eclipse Modeling Framework | Implemented in Java | |
Statistics model | Separated to be more extendable | Statistics belong to entity | |
Median as statistics property | yes, efficient implementation: insert: O(log(n) | no | |
Statistics represented as time series | no, but some infrastructure exists | no | |
Traces | Creation of In-Memory Trace Models | yes | yes |
Creation of Traces/Call Trees (for Export) | Dot, GraphML, Blueprints | Dot, PDF from Dot | |
Creation of Sequence Diagrams (Export) | no | Pic, PDF from Pic | |
Aggregation of all traces | no (but very similar to operation dependency graphs so debatable if necessary) | Dot, PDF from Dot | |
Aggregation of equal traces | yes, but currently no mapping to output formats | no | |
Trace repair functionality | no | yes | |
Distinction between Event and Execution Traces | no | yes | |
Dependency Graphs | Creation of In-Memory Model(s) | yes | yes |
Creation of Dependency Graphs (for Export) | Dot, GraphML, Blueprints | Dot, PDF from Dot | |
Trace coloring | no | yes | |
System Model | HTML representation of System Model | no | yes |
Special treatment of assumed calls | no | yes, if desired | |
Ignoring self loops | no | yes, if desired | |
Selecting/Excluding of single traces and time stamps | yes | yes |
...
Use one or more Exporter to export this graphs
Example Architecture
An example connection of the individual filters is shown in the following diagram:
View file | ||||
---|---|---|---|---|
|