[Bedrock AgentCore] Release Testing - Validator Changes #425
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
This PR is part 1 of the release testing changes to support the incoming release of the latest Bedrock AgentCore/Agentic AI Observability changes done in ADOT Python which contains all of the changes to
validatorWe need to validate that we are correctly emitting all 3 telemetry signals to CW backend.
Expands
Contextclass to also take in a given traceId - as a part of the Agent Observability, we've split off user input/output prompts from Gen AI span events as a separate log event. The idea is that users will be able to rebuild their entire Gen AI span event by querying for logs with the same trace id inaws/spansand a custom log group. As a part of this testing we need to verify that trace Id is being propagated from theirAgentic AI application + ADOT --> CWcorrectly and can be linked together.Updated
AWS OTLP log filterpatterns to capture and validate GenAI input/output prompt log events.Updated
TraceValidatorto validate pre-generated trace IDs for GenAI release testingUpdated
MetricValidatorto handle GenAI metrics special case: ADOT Python captures all OTel metrics from the Agentic AI application Instrumentor and converts them to EMF format. Validation for this path just checks for any metric emission to a custom namespace since the exact metric structure is unknownEnsure you've run the following tests on your changes and include the link below:
Example of a successful run of this test: https://github.com/liustve/aws-application-signals-test-framework/actions/runs/16172487807/job/45649328445
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.