Support for different trace source and types

Description

Kieker supports different stacks for trace analysis. While the old variants used in the trace-analysis-tool are still in place and work as intended, they are not extensible. Therefore, a new cleaner setup was introduced by . This approach separates the architectural reconstruction in multiple separate models and separates visualization from the model representation. Thus, this feature aims to extend this setup.

The rationale for the feature is, as follows: Currently, the architectural model cannot distinguish between sources for call references. however, for a combined analysis with dynamic and static parts, this information can be of relevance to detect unused model parts and therefore code automatically. Secondly, the model only shows call references, but it lacks data flow traces. This features aims to extend the current model specification to allow for both extensions.

Activity

Show:
Reiner Jung
8 days ago

Extension implemented and minor related fixes.

Reiner Jung
8 days ago

Fixed multiple issues.

Reiner Jung
April 8, 2021, 6:10 AM

Filters must be adapted accordingly.

Fixed

Assignee

Reiner Jung

Reporter

Reiner Jung

Labels

None

External issue ID

None

Components

Affects versions

Priority

Medium