newrelic / newrelic/newrelic-lambda-cli
New Relic log ingestion function Timeout set via environment variable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 54
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 3
Description
Summary
Hello, I don't use the AWS CLI to instrument my Lambda functions, because my stack is serverless automated via AWS CDK and I configure New Relic Lambda Layer with NEW_RELIC_NO_CONFIG_FILE: 'true'.
Desired Behaviour
Custom option to pass timeout value.
Possible Solution
I would need to set the timeout through an environment variable.
Implement an option to pass an environment variable to set the New Relic log ingestion function timeout.
Example: `NEW_RELIC_TIMEOUT: '90'`
Additional context
Currently I have an application with specific scenario that needs 30+ seconds, so I'm having problems with the default timeout of New Relic Layer 30 seconds.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the New Relic Lambda CLI path that configures the AWS Lambda layer when NEW_RELIC_NO_CONFIG_FILE is enabled, and inspect how existing environment-variable options are passed through. Trace the log ingestion function configuration and determine where NEW_RELIC_TIMEOUT would be applied. Done means a deployed ingestion function can use the requested timeout instead of the 30-second default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100