[Feature]: OTel plugin: emit severityText and severityNumber on enriched logs

Open
#938 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
67/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
observability

Research direction

Start with packages/aws-durable-execution-sdk-python-otel/src/aws_durable_execution_sdk_python_otel/log_filter.py, especially OtelContextLogFilter.filter(), and trace how enriched records from the Invocation and Execution plugins reach serialized structured logs. Check existing tests for durable context logs, stdlib logs, and replay behavior. Add coverage for the specified severity mappings and field types across initial and resumed invocations; done means both views emit top-level severity fields while disabled enrichment and default logging remain unchanged.

Written by the indexing model from the issue text.

Description

enhancement needs-triage pkg:otel
What would you like?

When aws-durable-execution-sdk-python-otel log enrichment is enabled, include OpenTelemetry severityText and severityNumber on the emitted structured application logs, alongside the existing native log level and trace correlation fields.

This is the Python counterpart of https://github.com/aws/aws-durable-execution-sdk-js/issues/1228.

The current OtelContextLogFilter.filter() adds traceId, spanId, and otelTraceSampled, but does not add either severity field. Both Invocation and Execution OTel plugins use this filter when enrich_logger=True. This finding is based on source inspection of main at 54883810bc417c59017540bae31e35fa9b35bd8c.

OTel-aware consumers, including CloudWatch Logs Analyze logs as described in the JS issue, need the standard severity fields to recognize, filter, and group log severity.

Possible Implementation

Extend the OTel logging enrichment path to set severityText from the source log level and map Python log levels to OpenTelemetry severity numbers:

Python level severityText severityNumber
DEBUG DEBUG 5
INFO INFO 9
WARNING WARNING 13
ERROR ERROR 17
CRITICAL, when logged through stdlib logging CRITICAL 21

WARNING is Python's spelling of the WARN severity range. logger.exception() should receive ERROR severity, like logger.error().

Follow the OTel log data model. The telemetry exporter's existing severity mapping is based on execution status and cannot be reused directly as an application log-level mapping.

Keep this additive and scoped to active OTel log enrichment. Preserve the existing native level, trace correlation, durable metadata, and replay suppression. Ensure the fields reach the serialized structured log output as top-level fields, with numeric severityNumber, rather than existing only as internal LogRecord attributes.

Acceptance criteria:

  • Both Invocation and Execution views emit the fields with the correct types and mappings.
  • Cover the durable context logger and stdlib logs that already flow through the enrichment filter.
  • Cover an initial invocation and a resumed invocation, preserving suppression of completed durable logs during replay.
  • Without the plugin, or with log enrichment disabled, the default logging behavior remains unchanged.
Is this a breaking change?

No.

Does this require an RFC?

No.

Additional Context
Dominant language
Python
Stars
59
Forks
32
Avg merge
1d 5h
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-durable-execution-sdk-python

All issues in aws/aws-durable-execution-sdk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.