changed lambda expiration to quarterly #1802
Merged
Conversation
This file contains 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
|
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
vlopeziglesias
force-pushed
the
lambda-expirationExtension
branch
from
e0bb242 to
e40453f
Compare
vlopeziglesias
force-pushed
the
lambda-expirationExtension
branch
from
e40453f to
a689035
Compare
Related to this issue newrelic#1792
vlopeziglesias
force-pushed
the
lambda-expirationExtension
branch
from
a689035 to
5cd48bf
Compare
vlopeziglesias
approved these changes
Dec 12, 2024
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.
What is the problem the customer is trying to solve?
There are many functions that invoke infrequently. They expect the associated entities to stick around in New Relic for at least as long as APM entities
, which is quarterly.
Why is it important for users that we fix that problem?
Lambda function entities that get deleted after 24 hours
lose tags and other entity-related data. It makes alerting on these entities difficult/impossible.
What is the objective they are pursuing?
Make infrequently invoked functions more useable in New Relic.
How does the ideal solution look for them?
Change the entityExpirationTime for Lambda functions to the same as APM entities (quarterly).
Related to this issue
#1792
Checklist
identifierwill be unique and valid.