Skip to content

Add baggage env variable span processor and agent observability version config - #658

Merged
liustve merged 8 commits into
mainfrom
agentcore-v2
Feb 25, 2026
Merged

liustve merged 8 commits into
mainfrom
agentcore-v2

Conversation

@liustve

@liustve liustve commented Feb 18, 2026

Copy link
Copy Markdown
Contributor

Description of changes:

  • adds new baggage span processor to also propagate span attribute keys for users using OTEL_BAGGAGE_SPAN_ATTRIBUTE_KEYS

  • add AGENT_OBSERVABILITY_VERSION to support versioned agent observability configurations

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@liustve
liustve requested a review from a team as a code owner February 18, 2026 01:50

@wangzlei wangzlei left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@liustve
liustve merged commit 35ef26e into main Feb 25, 2026
16 checks passed
@liustve
liustve deleted the agentcore-v2 branch February 25, 2026 22:50
vastin added a commit that referenced this pull request Jul 1, 2026
…808)

## Summary

Wires the EKS Service Events E2E test into
`application-signals-e2e-test.yml` by adding a `service-events-eks` job
that calls the reusable `python-eks-service-events-test.yml` workflow
from `aws-application-signals-test-framework` (added in [test-framework
PR
#658](aws-observability/aws-application-signals-test-framework#658),
now merged).

Mirrors the existing `service-events-ec2` job and the `eks-*` jobs
already in this file: image-based via `adot-image-name` (passed through;
when empty, the cluster operator's default SE-capable ADOT image is
validated), `caller-workflow-name: 'main-build'`, cluster
`e2e-python-adot-test`.

## Why this is needed

Beyond adding EKS SE coverage, this is required to keep the
`validate-e2e-tests-are-accounted-for` check green. That check
enumerates every `python-*-test.yml` on the test-framework `main` branch
and fails if any is not referenced here. Now that
`python-eks-service-events-test.yml` exists on test-framework `main`,
this reference is mandatory.

## Validation

The reusable workflow was validated end-to-end 5/5 (all 5 Service Events
signals) against `e2e-python-adot-test` in us-east-1 prior to
test-framework PR #658 merging. See that PR for the run evidence.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants