-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #12504 from kiranhew/whats-new-04-06-lambda-streaming
Whats new 04 06 lambda streaming
- Loading branch information
Showing
2 changed files
with
13 additions
and
0 deletions.
There are no files selected for viewing
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
13 changes: 13 additions & 0 deletions
13
src/content/whats-new/2023/04/whats-new-04-06-lambda-streaming.md
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
--- | ||
title: 'Monitor your Lambda Response Streaming with New Relic' | ||
summary: 'Keep track of volume of data and throughput for you Lambda Streaming function and prevent unexpected overages ' | ||
releaseDate: '2023-04-06' | ||
--- | ||
|
||
|
||
New Relic has integrated with a new capability for AWS Lambda functions, AWS Lambda Response Streaming, which allows response payloads to be streamed back to clients. Customers can improve time to first byte (TTFB) performance on their latency sensitive applications by sending partial responses to clients as they become available. This feature also allows customers to return larger than 6MiB payload sizes and return binary content. | ||
|
||
Using New Relic, along with other health and performance telemetry, you will now receive additional metrics to monitor the number of bytes (streamed outbound bytes) and throughput (streamed outbound throughput) of data generated by your streaming functions. As you are billed based on the number of bytes generated and streamed out of your Lambda function, having these metrics available ensures there you have visibility around your costs associated with this feature. | ||
|
||
![AWS Lambda Streaming metrics displayed in New Relic](./images/LambdaStreaming.png "AWS Lambda Streaming metrics displayed in New Relic") | ||
<figcaption>AWS Lambda Streaming metrics displayed in New Relic</figcaption> |