Skip to content
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

Seeing Errors when Env Variable is set to SPLUNK_LAMBDA_LOCAL_COLLECTOR_ENABLED=false #285

Open
storl0rd opened this issue Aug 22, 2024 · 0 comments

Comments

@storl0rd
Copy link


Exception while exporting metrics HTTPConnectionPool(host='localhost', port=4318): Max retries exceeded with url: /v1/metrics (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f527b1b8590>: Failed to establish a new connection: [Errno 111] Connection refused'))

We are seeing this error on our Lambda functions instrumented using separate layers for apm and metrics
arn:aws:lambda:ca-central-1:254067382080:layer:splunk-apm-python:8
arn:aws:lambda:ca-central-1:254067382080:layer:splunk-lambda-metrics:8

They are configured to send the data to a collector running in gateway mode on an EC2 instance.
The local collector has been disabled by SPLUNK_LAMBDA_LOCAL_COLLECTOR_ENABLED=false , however the logs indicate that the instrumentation is still trying to send metrics to 'localhost'

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

No branches or pull requests

1 participant