Skip to content

Orphaned Spans on long living Messenger Consume Commands #9

Description

@schromp

We are using the messenger component with doctrine.
Now in Kubernetes we have Workers which are started with the messenger:consume command.
These create orphaned traces whenever they read the database to check of messages are in the queue.

Image

If i filter for Consumer Spans i do see spans where messages were consumed but im guessing there is info being lost due to the orphaned spans. Also it does Spam the Root Spans.

Image

Can you give me help on how to work around this or is there a way to fix this in the library?

(Thank you for your work on this library. Its leagues better than what has existed before! :) )

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions