Version 1.26.0 #5429
Unanswered
Version 1.26.0
#5429
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This release represents the release candidate ("RC") release for the Logs Bridge API / SDK. In the next release (1.27.0),
opentelemetry-api-logs
will be merged intoopentelemetry-api
,opentelemetry-sdk-logs
will be marked as stable,opentelemetry-exporter-otlp-logs
will be merged intoopentelemetry-exporter-otlp
,opentelemetry-sdk-logs-testing
will be merged intoopentelemetry-sdk-testing
,opentelemetry-sdk-extension-autoconfigure
will enableotlp
log exporter by default (i.e.otel.logs.exporter=otlp
). For more details, see tracking issue #5340. 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.opentelemetry-opentracing-shim
is now stable!SDK
Resource
. (#5365)Metrics
Logs
InMemoryLogRecordExporter
toopentelemetry-sdk-logs-testing
. RenameInMemoryLogRecordExporter#getFinishedLogItems
togetFinishedLogRecordItems
. MoveSdkEventEmitterProvder
to internal package. (#5368)Exporters
OpenTracing Shim
SDK Extensions
Semantic Conventinos
Project Tooling
🙇 Thank you
This release was possible thanks to the following contributors who shared their brilliant ideas and awesome pull requests:
@breedx-splk
@carlosalberto
@chicobento
@chukunx
@DondekarShraddha
@Donnerbart
@jack-berg
@jkwatson
@mateuszrzeszutek
@ShadowySpirits
@trask
@tylerbenson
This discussion was created from the release Version 1.26.0.
Beta Was this translation helpful? Give feedback.
All reactions