Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Single OTLP trace for MQTT receive/publish #264

Open
nbuffon opened this issue Jan 22, 2025 · 1 comment
Open

Single OTLP trace for MQTT receive/publish #264

nbuffon opened this issue Jan 22, 2025 · 1 comment
Assignees
@nbuffon
Labels
Rust Rust code
Milestone
Sprint 7

Comments

@nbuffon
Copy link
Member

nbuffon commented Jan 22, 2025

Current behaviour

When an MQTT message is received and leads to publishing another one (e.g. DENM creation from dangerous situation) two traces with a single span are created

  • Reception : trace_id_123-span_id_456-00
  • Publish: trace_id_789-span_id_098-00

Expected behaviour

A single trace with two spans (at least) should be sent

  • Reception : trace_id_123-span_id_456-00
  • Publish: trace_id_123-span_id_098-00
@nbuffon nbuffon added the Rust Rust code label Jan 22, 2025
@nbuffon nbuffon self-assigned this Jan 22, 2025
@nbuffon nbuffon moved this to Ready in its-client Jan 22, 2025
@nbuffon nbuffon added this to the Sprint 7 milestone Jan 22, 2025
@nbuffon
Copy link
Member Author

nbuffon commented Jan 22, 2025

Problem is about trace context propagation and mostly through the different threads

See:

@nbuffon nbuffon moved this from Ready to In Progress in its-client Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nbuffon nbuffon

Labels
Rust Rust code
Projects
its-client
Status: In Progress
Milestone
Sprint 7
Development

No branches or pull requests
1 participant
@nbuffon