Releases: r0mdau/fluentforwardexporter
v0.3.1
v0.3.0
What's Changed
Breaking change 1
Add by default all otel attributes into the log record.
If some attributes are not wanted, you must use the processor/attributesprocessor, example to remove the hostname
attribute
processors:
attributes:
actions:
- key: hostname
action: delete
Breaking change 2
The default_labels_enabled
property act upon standard fields required by a Fluent endpoint and the OpenTelemetry logs/data-model definition.
This property allows to include or exclude the 3 fields timestamp
, level
and message
.
Best practice, keep them all. To disable one, set to false.
default_labels_enabled:
timestamp: true
level: true
message: true
Breaking change 3
In the exported log record, the field severity
is now labeled level
as it is usual to see level in ElasticSearch usage.
Full Changelog: v0.2.0...v0.3.0
v0.2.0
What's Changed
- Add TCP address resolution validation at startup by @csatib02 in #9
- Update to opentelemetry v0.115.0 by @r0mdau in #10
Breaking change
Configuration change from:
exporters:
fluentforward:
endpoint: localhost:24224
To this minimal working configuration:
exporters:
fluentforward:
endpoint:
tcp_addr: localhost:24224
Full Changelog: v0.1.5...v0.2.0
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0
This is the first testable version of the OpenTelemetry Fluent Forward exporter.
It is not tested in a live production environment.
Features :
- 6ec83c2 Share Key authentication
- 40cde1a efeedd1 TLS support
- d39886f Require Ack support
- 1b34373 Gzip support
- b49dcd7 Custom Fluent tag
- a81fad6 Dynamic opentelemetry attributes as keys in log record
- Handling re connections
- Logging
- https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/exporterhelper/README.md Queued retry capabilities