-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Switch Lambda Extension Logs Endpoint #8175
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we don't want the Serverless Agent to use something else than the HTTP endpoints, I think that would be a better implementation if we had BuildServerlessHTTPEndpoints()
directly called from pkg/logs/logs.go
with a if serverless
. It would have many benefits:
- can't use TCP endpoints from the Serverless Agent through a configuration change
- no propagation of the
serverless
flag in theconfig
package - no signature change of the
BuildEndpoints
function so no changes in the security nor cluster agent (but that's a bonus)
Please not that it means that we would have to sanitize the API key in BuildServerlessHTTPEndpoints
as well.
WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
What does this PR do?
Send logs from the Lambda Extension to the Lambda HTTP intake.
Motivation
Use the same endpoint in the Lambda Extension as the Datadog Forwarder.
Describe how to test your changes
Manually tested that logs still reach Datadog.