-
Notifications
You must be signed in to change notification settings - Fork 1.4k
feat: adding support for dot net specific payloads #22084
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
Conversation
…5-morning-2 Daily release/09 22 25 morning 2
…5-morning Daily release/09 23 25 morning
…5-morning Daily release/09 24 25 morning
…5-morning Daily release/09 25 25 morning
…5-morning Daily release/09 26 25 morning
…5-morning-2 Daily release/09 26 25 morning 2
…night Daily merge 09 29 25/night
…night Daily merge 09 30 25/night
…latenight Daily merge 09 30 25/latenight
…5-night Daily release/01 10 25 night
…night Daily merge 10 03 25/night
…5-night Daily release/10 07 25 night
…5-latenight Daily release/10 07 25 latenight
…5-evening Daily release/10 08 25 evening
…5-night Daily release/10 09 25 night
…5-evening Daily release/10 10 25 evening
…night Daily merge 10 13 25/night
…10-25 Daily merge night 10 10 25
…14-25 Daily merge night 10 14 25
…night Daily merge 10 15 25 night
…16-25 Daily merge night 10 16 25
…night Daily merge 10 17 25 night
…17-25 Daily merge night 10 17 25
Whats new post update
…5-morning Daily release/21 10 25 morning
…5-morng Daily release/21 10 25 morng
…5-morng Daily release/22 10 25 morng
…5-morng Daily release/23 10 25 morng
…5-morng Daily release/24 10 25 morng
…5-morningg Daily release/24 10 25 morningg
…5/night Daily release/27 10 25/night
…5-morning Daily release/28 10 25 morning
…5-night Daily release/28 10 25 night
…5-night Daily release/29 10 25 night
…5-night Daily release/30 10 25 night
…5-night Daily release/31 10 25 night
…night Daily merge 11 03 25/night
|
Hi @hrai-nr 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local. If you really require a preview url, reach out to one of the writers and they will generate one for you. |
|
|
|
||
| ### Changed | ||
|
|
||
| * Introduced a new environment variable `NEW_RELIC_FORMAT_LOGS` to enable proper processing of `.NET` specific log payload formats. |
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.
lgtm.
PallaviWrite
left a comment
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.
LGTM
Please follow conventional commit standards
in your commit messages and pull request title.
Give us some context
What problems does this PR solve?
This is release note for the below mentioned fix we did for logging:
Problem: The log-ingestion Lambda was unable to process the unique payload formats generated by .NET Lambda functions, leading to integration issues with New Relic. These payloads differed from those initially supported, causing disruptions in data parsing and instrumentation.
Solution: This PR updates the log-ingestion lambda function to support the specific .NET payload formats, resolving the compatibility issue. By implementing the necessary changes, .NET Lambda functions can now integrate seamlessly with New Relic, restoring proper functionality and instrumentation.
PR link : feat: added support for log format using NEW_RELIC_FORMAT_LOGS. aws-log-ingestion#128
Add any context that will help us review your changes such as testing notes,
links to related docs, screenshots, etc.
If your issue relates to an existing GitHub issue, please link to it.