Releases: DataDog/datadog-firehose-nozzle-release
Releases · DataDog/datadog-firehose-nozzle-release
87
- [Added] Upgrade nozzle to 2.7.0. Read more about it here.
- [Added] Upgrade go to 1.21.3. See #125.
- [Added] Add properties for the application logs collection feature. See #124.
- [Added] Add scheme prefix handling for the property
nozzle.dca_url
. See #123. - [Added] Make
nozzle.dca_url
andnozzle.dca_token
properties optional. See #122.
86
85
- [Added] Upgrade nozzle to 2.4.1.
- See Nozzle changelog for more information.
- [Added] Add option to enable advanced tagging. See #113.
- [Added] Add configuration values for the DCA properties. See #110.
84
- [Added] Upgrade nozzle to 2.4.0.
- See Nozzle changelog for more information.
83
82
81
80
79
- Bump Nozzle version to 2.1.0 See Nozzle Release Notes
78
- Bump nozzle version to 2.0.0, see nozzle release notes.
- Migrated to loggregator V2 API.
- The
loggregator.traffic_controller_url
property was removed in favor ofloggregator.rlp_gateway_url
. Theloggregator.rlp_gateway_url
is optional whencc.endpoint
is provided. Ifcc.endpoint
is not specified, you need to setloggregator.rlp_gateway_url
to proper value. You can get this by replacinghttps://api.
byhttps://log-stream.
in the URL of your Cloud Controller. - It is recommended that the UAA client under which nozzle runs is given the
logs.admin
authority. While this is strictly not necessary right now, asdoppler.firehose
coverslogs.admin
, it's not guaranteed that this will stay this way in upcoming PCF releases.
- The
- Fixed issue where the
host
wasn't submitted along with metrics when the submitted payload was split into multiple parts because of its size. This would cause some metrics to miss host tags in random intervals.