You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The table below contains the public base URIs of the Things used for protocol testing.
@@ -178,3 +196,24 @@ docker buildx build \
178
196
For running the things separately, using their `Dockerfile`'s, `docker build -t <image-tag> -f ./Dockerfile ../../` command must be used to give the context to be able to copy `tm.json` into the container.
179
197
180
198
For Node.js-based devices, we use npm workspaces and running `npm install` at the root directory installs all the packages needed for every device. After packages are installed, running `node main.js` would run the thing. For port configuration, running either `node main.js -p 1000` or `node main.js --port 1000` would start the thing on port 1000.
199
+
200
+
## Tracing
201
+
202
+
Distributed tracing is enabled using OpenTelemetry and Jaeger. To view all traces and logs, open [http://localhost:8084](http://localhost:8084) in your browser (Jaeger UI). Traces are sent to the Jaeger collector on port 8085.
203
+
204
+
Enhanced auto-tracing automatically injects `TracedBusinessLogic` for detailed span creation without redundancy. Function signatures determine tracing mode.
205
+
206
+
Also, there is comprehensive test suites that are also traced and visible in Jaeger:
207
+
208
+
- **Thing Description (TD) validation tests** - Test if the exposed TD is valid according to W3C WoT standards
209
+
- **Thing Model (TM) validation tests** - Validate the Thing Model against the schema
210
+
- **Integration tests** - Test actual interactions with the Things
211
+
212
+
When tests run, they appear in Jaeger with clear span names like `td.test` or `tm.test`. Failed tests show up as **error spans** with red highlighting in the Jaeger UI, making it easy to:
213
+
214
+
- **Debug test failures** by examining the error details and stack traces in span logs
215
+
- **Track test performance** and identify slow validation steps
216
+
- **Monitor CI/CD pipelines** by observing test execution patterns
217
+
- **Correlate test failures** with specific Thing operations or configurations
218
+
219
+
Test spans include detailed attributes about what was validated, error messages for failures, and timing information for performance analysis.
0 commit comments