v4.3.0

What's Changed

• Improvements in tracing package:
  • Configurable Jaeger exporter to enable send via HTTP.
  • Remove logic that attempts to modify packet size.
    • This is an imperfect workaround when sending via UDP through network interface (instead of loopback) at standard MTU of 1500 bytes. This MTU is too small for many Jaeger spans, so some packets will still get dropped. Recommended to use HTTP export, instead.
• Implement syncutil.Broadcaster methods: Remove() and Has().
• Bugfixes in clock package.

v4.2.5

This version introduces a mutex version of clock in a build tag called holster_test_mode. This allows you to pass the build tag when running tests in your project to prevent go from detecting a race condition when using clock.Freeze/Unfreeze.

ex:

go test -race -p 1 -tags holster_test_mode ./...

v4.2.4

What's Changed

• Fix errors.Wrap()/errors.Is() by @vtopc in #106

Full Changelog: v4.2.3...v4.2.4

Fix intermittent dropped tracing packets to Jaeger

• Update OpenTelemetry packages to get recent fix for oversized UDP packets.

v4.2.2

• Fix OpenTelemetry dropping packets

v4.2.1

Adding a DefaultResolver to mxresolv.

v4.1.3

• Fix race condition in tracing package.

v4.1.2

• Fix edge condition where InitTracing() might return a nil context.

v4.1.1

• Update OpenTelemetry dependencies.
• Update documentation about configuration of service name.

v4.1.0

• Tooling to use OpenTelemetry to send traces to a Jaeger Tracing server.
  • Use OpenTelemetry to generate traces visualizing behavior in your application. It's comprised of nested spans that are rendered as a waterfall graph. Each span indicates start/end timings and optionally other developer specified metadata and logging output.
  • Jaeger Tracing is the tool used to receive OpenTelemetry trace data. Use its web UI to query for traces and view the waterfall graph.