-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Lambda Extension #1139
Comments
The Lambda functionality is published as layers over at https://github.com/newrelic/newrelic-lambda-layers. The layers include some additional code that is used to interface with the lambda extension. An outdated version of the additional functionality is published to PyPi as It's easiest to set up lambda monitoring using our Lambda CLI. You can find an example for Python located here. |
Log forwarding should be on by default however, maybe your lambda had it turned off since you were using a different forwarder before. See the following for the necessary configuration options: |
Is your feature request related to a problem? Please describe.
We are trying to switch from the old log group subscription approach to your Lambda extension. https://github.com/newrelic/newrelic-lambda-extension
It seems that the Python agent doesn't support it though. Even with the layer installed, it still outputs telemetry directly to the logs. And I don't see any mention of the special named pipe (/tmp/newrelic-telemetry) in this repo.
Feature Description
Automatically detect and use the named pipe from the extension, like the other language agents do.
Describe Alternatives
None.
Additional context
None.
Priority
Must Have. Until this is fixed, we are unable to get all of our Python lambda functions to use a unified log group.
The text was updated successfully, but these errors were encountered: