-
Couldn't load subscription status.
- Fork 269
Open
Description
I have been investigating if Python's logging signal is ready to be stabilized. Could we get a TC member to look through the code and confirm that it is in line with the log spec and sem conv?
[UPDATE from @tigrannajaryan] Checklist to verify, borrowed from #1537 (checkmark means reviewed/verified against spec definition):
- Getting Started example works
- LoggerProvider.Get Logger
- Minor doc issues - Logs API:
LoggerProviderdocs issues opentelemetry-python#4318
- Minor doc issues - Logs API:
- LoggerProvider.Get Logger accepts attributes
- Minor doc issues - Logs API:
LoggerProviderdocs issues opentelemetry-python#4318
- Minor doc issues - Logs API:
- LoggerProvider.Shutdown
- LoggerProvider.ForceFlush
- Can get global LoggerProvider
- Can set global LoggerProvider
- Logger.Emit(LogRecord)
- SimpleLogRecordProcessor
- BatchLogRecordProcessor
- Can plug custom LogRecordProcessor
- OTLP/gRPC exporter
- OTLP/HTTP exporter
- OTLP File exporter - According to compatibility matrix, not yet implemented.
- Can plug custom LogRecordExporter
- Trace Context Injection
- yes, but only when using
LoggingHandlerbridge - Logs API: not possible to use without SDK opentelemetry-python#4319
- yes, but only when using
- LogRecord fields output
Metadata
Metadata
Assignees
Labels
No labels