dpol1 commented on issue #9155:
URL: https://github.com/apache/storm/issues/9155#issuecomment-6412677054
In a prototype with Java agent 2.31.1 and one worker in a LocalCluster, an
agent extension fed ended spans to a Storm spout with their trace, span and
parent IDs intact. Transporting and exporting the records also generated spans,
feeding them back into the queue; a filter stopped the loop in this setup but
let through the export endpoint's server spans, whose parents are remote.
```mermaid
flowchart LR
T["user topology"] -->|"spans"| X["agent extension (SpanProcessor)"]
X -->|"byte[] per span"| Q[("bounded queue in System.getProperties()")]
Q --> S["spout"] --> B["bolt"] -->|"POST batches"| E["local /export
endpoint"]
S -.->|"emit spans, filtered"| X
B -.->|"execute and HTTP client spans, filtered"| X
E -.->|"server spans, not filtered"| X
```
The queue handoff through `System.getProperties()` is provisional, and
supervisor-launched workers, multiple workers and overhead remain untested.
Next I'd define what workers send to the reporter bolt.
Drafted with AI assistance; findings checked against local prototype runs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
