Add Python Processor support and container deployment model #27
+1,888
−293
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mheffner
commented
Jan 29, 2026
| push: | ||
| branches: | ||
| - main | ||
| - python-processor |
Contributor
Author
There was a problem hiding this comment.
Keeping for testing, but will remove.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The core change here is adding support for Python log processors through the environment variable
FORWARDER_OTLP_LOG_PROCESSORS. Processors are loaded at start time and deployed in the correct directory.The larger changes here are from the addition of the container deployment model which allows us to bundle the Python runtime. We actually use the AWS Lambda Python 3.14 image to build and deploy the forwarder when supporting Python processors. The pre-built .zip deployment is still available, but does not support the processors.
The Cloudformation scripts have been updated to use the new container deployment. Containers are deployed to public ECR and the CF uses CodeBuild to pull them to a private ECR, allowing them to be deployed to lambda.
There did not seem to be a noticeable performance impact when filtering VPC logs with a python processor.