Closed nbuffon closed 4 weeks ago
- [x] Tests all working as described.
One comment, though:
copycat
reports several informational messages that look like errors:INFO [libits::client::application::pipeline] Cannot trace exchange, missing gateway component name in node configuration
This is because of the old KPI logging system which requires the Information message to be received once first, and test.mosquitto.org obviously does not send one As KPI computation is planned to now be made using telemetry traces these function calls can be removed, I opened a new issue to do so (#199)
What's new
Closes #124
How to test
Start a Jaeger/OTLP collector image
Create the test script
(or download it as txt test_copycat.txt)
Listen to MQTT messages with MQTTv5 properties
Edit the
examples/config.ini
file to fill the telemetry section with the following contentStart the copycat example with the telemetry feature
Launch the test script
=> Several reception must be logged
=> One message publication must be logged
The published message should be carrying the W3C context (logged by mosquitto_sub command)
The test scripts did prompt asking for a trace parent, answer it using the published message's one
Check the spans content on the local jaeger interface => You must see 8 traces
=> The 7th (the second most recent) must have a link to another span