Version 1.27.0
The log bridge API / SDK are now stable! Some important notes:
- The contents of
opentelemetry-api-logs
have been merged intoopentelemetry-api
. - The contents of
opentelemetry-exporter-otlp-logs
have been merged intoopentelemetry-exporter-otlp
. - The contents of
opentelemetry-sdk-logs-testing
have been merged intoopentelemetry-sdk-testing
. - The
opentelemetry-sdk-logs
artifact has been marked stable. opentelemetry-sdk-extension-autoconfigure
has changed the default value ofotel.logs.exporter
fromnone
tootlp
.
NOTE: reminder that the Logs Bridge API is not meant for end users. Log appenders use the API to bridge logs from existing log frameworks (e.g. JUL, Log4j, SLf4J, Logback) into OpenTelemetry. Users configure the Log SDK to dictate how logs are processed and exported. See opentelemetry.io for documentation on usage.
API
SDK
- Ensure correct compiled output and sources are included in multi version jar (#5487)
Logs
- Fix broken link (#5451)
- Add meaningful
.toString
toNoopLogRecordProcessor
andDefaultOpenTelemetry
(#5493) - Promote log SDK to stable (#5341)
Metrics
- Reset exponential aggregator scale after collection (#5496)
- Experimental metric reader and view cardinality limits (#5494)
Exporter
Testing
- Merge sdk logs testing (#5431)
- Add a
hasBucketBoundaries()
variant that allows specifying precision (#5457)
SDK Extensions
- Enable otlp logs by default in autoconfigure (#5433)
Semantic Conventions
- Update to semconv 1.20.0 (#5497)
🙇 Thank you
This release was possible thanks to the following contributors who shared their brilliant ideas and awesome pull requests:
@alanwest
@bogdandrutu
@breedx-splk
@Emily-Jiang
@fmhwong
@iRevive
@Izzzu
@jack-berg
@jkwatson
@jsuereth
@kenfinnigan
@lu-xiaoshuang
@mateuszrzeszutek
@psx95
@the-vj
@tigrannajaryan
@trask