The Common Trace API (CTA) is an interface-based specification of a common trace representation to allow a monitoring-tool-format-independent access of trace data. The CTA supports the exchange of monitoring data between stakeholders (e.g., Ops and Dev, or different research groups) while the consumer accesses the data with the CTA.
...
A trace that traverses multiple locations is divided into subtraces. Hence, a subtrace is identified by the Location tuple (Host (e.g. IP), Container(e.g. JVM Id), Application Id, Business Transaction Id). Subtraces are structured along a composite pattern (tree structure). In this way, subtraces provide a coarse-frained grained view on the logical trace. A subtrace, in turn, contains a tree of Callables, hence, a trace covering one Location.
Gliffy
...
returns the parent callable of the current callable within the tree structure of the corresponding sub trace.
If the current callable is the root of the current sub trace that has been called by another sub trace then this method returns the TraceInvocation instance of the (other) calling sub trace.
If the current callable is a root and the current sub trace is a root of the entire logical trace then this method returns null.
...
shell we leave this information here, or move it to CTA AIC (additional information part).
Rationale: this information might be not language independent, at least the encoding of the returned integer
...
JavaDoc
Interface Diagram
| Gliffy | ||||
|---|---|---|---|---|
|
Support
You can request new Features and report experienced Bugs in our JIRA. We are pleased to improve CTA daily and appreciate any feedback.