Changelog
Kong Gateway 3.8.x
-
Added support for OpenTelemetry-formatted logs. #13291
As part of the rework, the following parameter has been deprecated and will be removed in a future major version:
-
config.endpoint
is deprecated, useconfig.traces_endpoint
instead.
-
- Fixed an issue where migration failed when upgrading from versions earlier than 3.3.x to 3.7.x. #13391
- Removed redundant deprecation warnings. #13220
- Improved the accuracy of sampling decisions. #13275
Kong Gateway 3.7.x
-
The propagation module has been reworked. The new options allow better control over the configuration of tracing header propagation. #12670.
As part of the rework, the following parameters have been deprecated and will be removed in a future major version:
-
config.header_type
is deprecated, useconfig.propagation
instead. -
config.batch_span_count
is deprecated, useconfig.queue.max_batch_size
instead. -
config.batch_flush_delay
is deprecated, useconfig.queue.max_coalescing_delay
instead.
-
-
Fixed an OTEL sampling mode Lua panic bug, which happened when the
http_response_header_for_traceid
option was enabled. #12544
Kong Gateway 3.6.x
- The tracing sampling rate can now be set via the
config.sampling_rate
property of the OpenTelemetry plugin instead of just being a global setting for Kong Gateway. #12054
Kong Gateway 3.5.x
-
Added support for Google Cloud Project’s X-Cloud-Trace-Context header
-
Added a new value to the parameter
header_type
, which allows Kong Gateway to inject Datadog headers into the headers of requests forwarding to the upstream. -
Fixed an issue that resulted in traces with invalid parent IDs when
balancer
instrumentation was enabled. #11830
Kong Gateway 3.4.x
-
Added support for AWS X-Ray header propagation.
The field
header_type
now accepts theaws
value to handle this specific propagation header. #11075 -
The
endpoint
parameter is now referenceable, and can be stored as a secret in a vault.
Kong Gateway 3.2.x
- This plugin can now be scoped to individual services, routes, and consumers.
Kong Gateway 3.1.x
- The
headers
field is now marked as referenceable, which means it can be securely stored as a secret in a vault.