-
Currently the correlation ID is only exposed via the existing HttpContext.TraceIdentifier. This requires either access to the HttpContext or an IHttpContextAccessor to be able to get to the correlatio…
-
since `CorrelationContextAccessor` returns the correlation context of an request, it is probably a bad idea to have it as singleton, because parallel requests will overwrite the `CorrelationContext`. …
-
using version 2.0.0.M9, i dont want to put "spring.sleuth.baggageKeys: foo" everywhere.
the previous way "span.setBaggageItem(baggageKey, baggageValue);" is good enough, why change?
when can it use …
-
Californium implements in UdpMatcher.receiveResponse() discard of responses that do not belong to the same DTLS session as the request on CoAP-Client side.
This implements the requirement of CoAP spe…
-
I'm using this in conjunction with Bot Framework on Node.js. Is there a ES6 polyfill that I need? It seems internal to Telemetry
```
TypeError: telemetry.time.toISOString is not a function
…
-
I did a short test using the principal names as endpoint identity for DTLS and notifies.
This extents the exporting of the `CorrelationContext` over the scope of the implementation of `ObservationS…
boaks updated
6 years ago
-
Currently, Observation is identify by token in observation store.
We should identify it by token + a peer identifier.
I recommend that peer identifier was :
- peer-address for unsecure con…
-
Hi,
It seems that if I use this library, the `RequestId` is getting replaced with the` CorrelationId`, retrieved/generated by this library.
Is there a way to use this library, but still preserv…
-
When a request to a LWM2M client, e.g. read request, gets triggered, Leshan looks up the client with the desired endpoint name from the client registry and sends the request to the IP:Port saved there…
-
RawData
public boolean isSecure() {
return (correlationContext != null &&
correlationContext.get(DtlsCorrelationContext.KEY_SESSION_ID) != null);
}
Remove DTLS dependeny by i…
boaks updated
6 years ago