From e5a50c0379c4d541d063e76bd02590bbcec6171a Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Thu, 8 Aug 2024 13:38:19 +0530 Subject: [PATCH 01/13] WIP --- .../otel-adot-log-ingestion-serverless.mdx | 124 ++++++++++++++++++ src/nav/serverless-function-monitoring.yml | 2 + 2 files changed, 126 insertions(+) create mode 100644 src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx new file mode 100644 index 00000000000..0a413fc58b2 --- /dev/null +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx @@ -0,0 +1,124 @@ +--- +title: OTEL log ingestion solution for ADOT lambda layer collector +metaDescription: How to instrument your serverless applications on AWS Lambda with ADOT solution in New Relic. +freshnessValidatedDate: never +--- +You can now monitor AWS serverless application that sends OTEL log events data from CloudWatch Logs to the New Relic UI. +You can configure the ADOT lambda layer collector to successfully forward OTEL application logs with all necessary service and application context. +This includes ensuring that logs contain metadata such as service name, version, environment, and any other relevant attributes that can aid in observability and troubleshooting. + + +## Pre-requisites + +* Make sure you have a . + + + +## Procedure + +he following setup shows one approach for configuring environment variables. You can also configure them from the [Functions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html) page. + +Complete the following: + +Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amazon.com/applications) in your browser. +Under **Applications**, type `newrelic` in the search bar, and click the **Show apps that create custom IAM roles or resource policies** check-box to find `newrelic-aws-otel-log-ingestion`. +Open the `newrelic-aws-otel-log-ingestion` details and click **Deploy**. +In the function's **Configure** menu, go to **Environment Variables** and configure log forwarding using the following environment variables: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Key + + Description +
+ `DEBUG_LOGGING_ENABLED` + + A boolean to determine if you want to output debug messages in the CloudWatch console. **Optional**. + + To turn on debug logs, set this to `true`. Default is `false`. +
+ `LICENSE_KEY` + + is used for sending data to New Relic. **Required.** +
+ `LOGGING_ENABLED` + + Determines if logs are forwarded to New Relic. **Required.** To turn on logging, set this to `true`. +
+ `NR_TAGS` + + Specify tags to be added to all log events. **Optional**. + + Each tag is composed of a colon-delimited key and value. Multiple key-value pairs are semicolon-delimited; for example, `env:prod;team:myTeam`. +
+ `NR_LAMBDA_LOG_GROUP_PREFIX` + + If you've configured your Lambda log group to use a different path than `/aws/lambda`, you can specify it with this variable. **Optional**. +
+ `NR_VPC_LOG_GROUP_PREFIX` + + If you've configured your VPC log group to use a different path than `/aws/vpc/flow-log`, you can specify it with this variable. **Optional**. +
+ + +Acknowledge that the app creates custom IAM roles, and then click **Deploy**. + + + + + + +2. Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amazon.com/applications) in your browser. +3. Search for `newrelic` and check **Show apps that create custom IAM roles or resource policies** to find `newrelic-log-ingestion`. +4. Open the `newrelic-log-ingestion` details and click **Deploy**. +5. In the function's **Configure** menu, go to **Environment Variables** and configure log forwarding using the following environment variables: + + + +6. Acknowledge that the app creates custom IAM roles, and then click **Deploy**. + diff --git a/src/nav/serverless-function-monitoring.yml b/src/nav/serverless-function-monitoring.yml index f98a7447799..cf7ed59ebe2 100644 --- a/src/nav/serverless-function-monitoring.yml +++ b/src/nav/serverless-function-monitoring.yml @@ -25,6 +25,8 @@ pages: path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-java - title: Trace your .NET Lambda functions with New Relic and OpenTelemetry path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet + - title: OTEL log ingestion solution for ADOT lambda layer collector + path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless - title: UI and data pages: - title: Understand and use the UI From 98ba1d215b6c6c27edc368962b3380a242035c24 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Thu, 8 Aug 2024 17:10:56 +0530 Subject: [PATCH 02/13] wip --- .../otel-adot-log-ingestion-serverless.mdx | 97 ++++++++++++++++--- 1 file changed, 82 insertions(+), 15 deletions(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx index 0a413fc58b2..64fa16ae0dd 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx @@ -16,14 +16,27 @@ This includes ensuring that logs contain metadata such as service name, version, ## Procedure -he following setup shows one approach for configuring environment variables. You can also configure them from the [Functions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html) page. +The following setup shows one approach for configuring environment variables to your AWS Lambda application. You can also configure them from the [Functions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html) page. + -Complete the following: -Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amazon.com/applications) in your browser. -Under **Applications**, type `newrelic` in the search bar, and click the **Show apps that create custom IAM roles or resource policies** check-box to find `newrelic-aws-otel-log-ingestion`. -Open the `newrelic-aws-otel-log-ingestion` details and click **Deploy**. -In the function's **Configure** menu, go to **Environment Variables** and configure log forwarding using the following environment variables: + + + +Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amazon.com/applications) in your browser, and complete the following procedure. + + + +1. Under **Applications**, type `newrelic` in the search bar, and click the **Show apps that create custom IAM roles or resource policies** check-box to find `newrelic-aws-otel-log-ingestion`. + + + + +2. Open the `newrelic-aws-otel-log-ingestion` details and click **Deploy**. + + +3. In the function's **Configure** menu, go to **Environment Variables** and configure log forwarding using the following environment variables: + @@ -39,6 +52,19 @@ Complete the following: + + + + + + + @@ -106,19 +132,60 @@ Complete the following:
+ `OTEL_LOGGING_ENABLED` + + A boolean to determine if you want to output debug messages in the CloudWatch console. **Optional**. + + To turn on debug logs, set this to `true`. Default is `false`. +
`DEBUG_LOGGING_ENABLED` @@ -67,7 +93,7 @@ Complete the following: - Determines if logs are forwarded to New Relic. **Required.** To turn on logging, set this to `true`. + Set this flag to `false`.
-Acknowledge that the app creates custom IAM roles, and then click **Deploy**. - + +Acknowledge that the app creates custom IAM roles, and then click **Deploy**. + + + +Once the process in the step above completes, create a Lambda trigger to link your Lambda function to CloudWatch logs. +To get your logs streaming to New Relic UI, attach a trigger to the Lambda: + +1. From the left side menu, select **Functions**. +2. Find and select the previously created `newrelic-log-ingestion` function. +3. Under **Triggers**, click **Add Triggers**, and select **CloudWatch Logs** from the dropdown. +4. Select the the appropriate **Log group** for your application. +5. Enter a name for your filter. +6. Optional: Enter a [filter pattern](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/FilterAndPatternSyntax.html). +7. Check the **Enable trigger** checkbox, then click **Add** to create the trigger. + + +On the ingestion function, ensure that you set up a trigger, not a log subscription. Setting up a subscription in the Lambda console can lead to a cascade of logs generated and forwarded to New Relic. + + + + + + +You can set a custom logging endpoint if needed, this will allow you for example to use our FedRAMP compliant endpoints. + +For that, you should deploy the application and explained above and then: + + +1. Go to the recently deployed lambda function view in AWS. +2. Scroll down and click on the **Configuration** tab. +3. On the left menu inside the **Configuration** tab, click on **Environment Variables**. +4. Here you can see a list of the already existing environment variables, just click **Edit** on the top right of the **Environment Variables** table. +5. Update the `NR_LOGGING_ENDPOINT` with the appropiate endpoint: + - For US: `https://log-api.newrelic.com/log/v1` + - For EU: `https://log-api.eu.newrelic.com/log/v1` + - For FedRAMP: `https://gov-log-api.newrelic.com/log/v1` +6. Click **Save**. + + + + + + + + -2. Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amazon.com/applications) in your browser. -3. Search for `newrelic` and check **Show apps that create custom IAM roles or resource policies** to find `newrelic-log-ingestion`. -4. Open the `newrelic-log-ingestion` details and click **Deploy**. -5. In the function's **Configure** menu, go to **Environment Variables** and configure log forwarding using the following environment variables: - -6. Acknowledge that the app creates custom IAM roles, and then click **Deploy**. From cd82fc62818d7581e0de26801e37f78bec09e4fa Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Mon, 12 Aug 2024 10:24:01 +0530 Subject: [PATCH 03/13] WIP --- .../otel-adot-log-ingestion-serverless.mdx | 47 ++----------------- 1 file changed, 3 insertions(+), 44 deletions(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx index 64fa16ae0dd..9629526e07b 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx @@ -55,7 +55,7 @@ Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amaz - `OTEL_LOGGING_ENABLED` + `NR_OTEL_LOGGING_ENABLED` @@ -87,47 +87,6 @@ Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amaz - - - `LOGGING_ENABLED` - - - - Set this flag to `false`. - - - - - - `NR_TAGS` - - - - Specify tags to be added to all log events. **Optional**. - - Each tag is composed of a colon-delimited key and value. Multiple key-value pairs are semicolon-delimited; for example, `env:prod;team:myTeam`. - - - - - - `NR_LAMBDA_LOG_GROUP_PREFIX` - - - - If you've configured your Lambda log group to use a different path than `/aws/lambda`, you can specify it with this variable. **Optional**. - - - - - - `NR_VPC_LOG_GROUP_PREFIX` - - - - If you've configured your VPC log group to use a different path than `/aws/vpc/flow-log`, you can specify it with this variable. **Optional**. - - @@ -157,7 +116,7 @@ On the ingestion function, ensure that you set up a trigger, not a log subscript - +{/* **Save**. - + */} From 6b37ff4e05df24b2c1c9571a1d90f0e236c55aa9 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Mon, 12 Aug 2024 18:52:32 +0530 Subject: [PATCH 04/13] wip --- .../otel-adot-log-ingestion-serverless.mdx | 21 +++++++------------ 1 file changed, 8 insertions(+), 13 deletions(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx index 9629526e07b..5c5326808f3 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx @@ -1,20 +1,21 @@ --- -title: OTEL log ingestion solution for ADOT lambda layer collector +title: Logs for AWS Distro for OpenTelemetry Lambda functions metaDescription: How to instrument your serverless applications on AWS Lambda with ADOT solution in New Relic. freshnessValidatedDate: never --- -You can now monitor AWS serverless application that sends OTEL log events data from CloudWatch Logs to the New Relic UI. -You can configure the ADOT lambda layer collector to successfully forward OTEL application logs with all necessary service and application context. +You can monitor AWS serverless application that sends OpenTelemetry log events data from AWS CloudWatch to the New Relic UI. +You can configure the ADOT Lambda layer collector to successfully forward your OpenTelemetry application logs with all of your service and application context. This includes ensuring that logs contain metadata such as service name, version, environment, and any other relevant attributes that can aid in observability and troubleshooting. -## Pre-requisites +## Prerequisites [#Prerequisite] * Make sure you have a . +* An AWS account -## Procedure +## Procedure [#procedure] The following setup shows one approach for configuring environment variables to your AWS Lambda application. You can also configure them from the [Functions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html) page. @@ -27,14 +28,8 @@ Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amaz -1. Under **Applications**, type `newrelic` in the search bar, and click the **Show apps that create custom IAM roles or resource policies** check-box to find `newrelic-aws-otel-log-ingestion`. - - - - +1. Under **Applications**, type `newrelic` in the search bar, and click the **Show apps that create custom IAM roles or resource policies** check-box to find `newrelic-aws-otel-log-ingestion`. 2. Open the `newrelic-aws-otel-log-ingestion` details and click **Deploy**. - - 3. In the function's **Configure** menu, go to **Environment Variables** and configure log forwarding using the following environment variables: @@ -101,7 +96,7 @@ Acknowledge that the app creates custom IAM roles, and then click **Deploy* Once the process in the step above completes, create a Lambda trigger to link your Lambda function to CloudWatch logs. -To get your logs streaming to New Relic UI, attach a trigger to the Lambda: +To get your logs streaming to New Relic UI, attach a trigger to the Lambda in the AWS UI: 1. From the left side menu, select **Functions**. 2. Find and select the previously created `newrelic-log-ingestion` function. From 863b65aec47cc20ae6a64576cb09749c671270e8 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Mon, 12 Aug 2024 18:59:10 +0530 Subject: [PATCH 05/13] wip --- .../opentelemetry/otel-adot-log-ingestion-serverless.mdx | 5 ++--- src/nav/serverless-function-monitoring.yml | 2 +- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx index 5c5326808f3..22354ef8e97 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx @@ -17,8 +17,7 @@ This includes ensuring that logs contain metadata such as service name, version, ## Procedure [#procedure] -The following setup shows one approach for configuring environment variables to your AWS Lambda application. You can also configure them from the [Functions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html) page. - +The following setup shows one approach for configuring environment variables to your AWS Lambda application. You can also configure them on the AWS functions page. For more information, [see the Amazon Lambda environment variables doc](https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html). @@ -66,7 +65,7 @@ Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amaz - A boolean to determine if you want to output debug messages in the CloudWatch console. **Optional**. + A Boolean to determine if you want to output debug messages in the CloudWatch console. **Optional**. To turn on debug logs, set this to `true`. Default is `false`. diff --git a/src/nav/serverless-function-monitoring.yml b/src/nav/serverless-function-monitoring.yml index cf7ed59ebe2..f2a622f7261 100644 --- a/src/nav/serverless-function-monitoring.yml +++ b/src/nav/serverless-function-monitoring.yml @@ -25,7 +25,7 @@ pages: path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-java - title: Trace your .NET Lambda functions with New Relic and OpenTelemetry path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet - - title: OTEL log ingestion solution for ADOT lambda layer collector + - title: Logs for AWS Distro for OpenTelemetry Lambda functions path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless - title: UI and data pages: From f8a8a251b4ed346b0e9300e66a0c08deb0384991 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Mon, 12 Aug 2024 21:12:36 +0530 Subject: [PATCH 06/13] Update otel-adot-log-ingestion-serverless.mdx fixed an editorial error --- .../opentelemetry/otel-adot-log-ingestion-serverless.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx index 22354ef8e97..d3325b414f2 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx @@ -98,7 +98,7 @@ Once the process in the step above completes, create a Lambda trigger to link yo To get your logs streaming to New Relic UI, attach a trigger to the Lambda in the AWS UI: 1. From the left side menu, select **Functions**. -2. Find and select the previously created `newrelic-log-ingestion` function. +2. Find and select the previously created `newrelic-aws-otel-log-ingestion` function. 3. Under **Triggers**, click **Add Triggers**, and select **CloudWatch Logs** from the dropdown. 4. Select the the appropriate **Log group** for your application. 5. Enter a name for your filter. From b45a72e48c71db6d41262ecf4211ab40e67de527 Mon Sep 17 00:00:00 2001 From: cbehera-newrelic Date: Tue, 13 Aug 2024 16:42:57 +0530 Subject: [PATCH 07/13] Review comments are fixed --- .../otel-adot-log-ingestion-serverless.mdx | 45 ++++++++++++------- src/nav/serverless-function-monitoring.yml | 2 +- 2 files changed, 30 insertions(+), 17 deletions(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx index d3325b414f2..0e0114cce99 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx @@ -1,11 +1,11 @@ --- -title: Logs for AWS Distro for OpenTelemetry Lambda functions +title: Forward your Lambda function logs with Newrelic and OpenTelelemtry metaDescription: How to instrument your serverless applications on AWS Lambda with ADOT solution in New Relic. freshnessValidatedDate: never --- You can monitor AWS serverless application that sends OpenTelemetry log events data from AWS CloudWatch to the New Relic UI. You can configure the ADOT Lambda layer collector to successfully forward your OpenTelemetry application logs with all of your service and application context. -This includes ensuring that logs contain metadata such as service name, version, environment, and any other relevant attributes that can aid in observability and troubleshooting. +This includes ensuring that logs contain metadata such as service name, log group name, function ARN and any other relevant attributes that can aid in observability and troubleshooting. ## Prerequisites [#Prerequisite] @@ -38,7 +38,12 @@ Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amaz Key - + + Default value + + + Options + Description @@ -51,23 +56,31 @@ Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amaz `NR_OTEL_LOGGING_ENABLED` - - A boolean to determine if you want to output debug messages in the CloudWatch console. **Optional**. - - To turn on debug logs, set this to `true`. Default is `false`. + true + + + `true`,`false`. + + + Determines if logs are forwarded to the New Relic UI + `DEBUG_LOGGING_ENABLED` - - A Boolean to determine if you want to output debug messages in the CloudWatch console. **Optional**. - - To turn on debug logs, set this to `true`. Default is `false`. + false + + + `true`,`false`. + + + + A Boolean to determine if you want to output debug messages in the CloudWatch console. @@ -110,7 +123,7 @@ On the ingestion function, ensure that you set up a trigger, not a log subscript -{/* + **Configuration** tab. 3. On the left menu inside the **Configuration** tab, click on **Environment Variables**. 4. Here you can see a list of the already existing environment variables, just click **Edit** on the top right of the **Environment Variables** table. -5. Update the `NR_LOGGING_ENDPOINT` with the appropiate endpoint: - - For US: `https://log-api.newrelic.com/log/v1` - - For EU: `https://log-api.eu.newrelic.com/log/v1` +5. Update the `NR_OTEL_LOGGING_ENDPOINT` with the appropiate endpoint: + - US_OTEL_LOGGING_ENDPOINT: `https://otlp.nr-data.net:4318/v1/logs` + - EU_OTEL_LOGGING_ENDPOINT : `https://otlp.eu01.nr-data.net:4318/v1/logs` - For FedRAMP: `https://gov-log-api.newrelic.com/log/v1` 6. Click **Save**. - */} + diff --git a/src/nav/serverless-function-monitoring.yml b/src/nav/serverless-function-monitoring.yml index f2a622f7261..e3d06971459 100644 --- a/src/nav/serverless-function-monitoring.yml +++ b/src/nav/serverless-function-monitoring.yml @@ -25,7 +25,7 @@ pages: path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-java - title: Trace your .NET Lambda functions with New Relic and OpenTelemetry path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet - - title: Logs for AWS Distro for OpenTelemetry Lambda functions + - title: Forward your Lambda function logs with Newrelic and OpenTelelemtry path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless - title: UI and data pages: From 094f7d32d898ce97a8688109ee6931d396ce13a0 Mon Sep 17 00:00:00 2001 From: Adar Maor Date: Thu, 15 Aug 2024 15:17:30 +0300 Subject: [PATCH 08/13] docs(events-api): added caution and reworded aggregation explanation --- .../ingest-apis/event-api/incident-event-rest-api.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx b/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx index 4ccb0afef67..bfe4ac8be46 100644 --- a/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx +++ b/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx @@ -135,6 +135,9 @@ Here's an example of a NerdGraph query and its result. The incident event API uses the Event API's value types. For descriptions of these value types and guidelines on using them, see [our event API JSON guidelines](/docs/data-apis/ingest-apis/introduction-event-api/#json-guidelines). + + If you create two trigger events with the exact same aggregationTag, they will be aggregated to the same incident. + @@ -163,7 +166,7 @@ The incident event API uses the Event API's value types. For descriptions of the Any attribute prefixed with `aggregationTag` will be used to aggregate trigger events together. - In other words, two trigger events with the same aggregation tags are aggregated to the same incident. (This assumes there's no resolve event between them). + In other words, two trigger events with the same aggregation tags are aggregated to the same incident. (Under the assumption that none of the trigger events are resolve events). When resolving incidents, it’s important that the resolve event include the same aggregation tags. From e9b5a3677a935144854a2cdfe462c36771d60e4b Mon Sep 17 00:00:00 2001 From: Adar Maor Date: Thu, 15 Aug 2024 17:05:06 +0300 Subject: [PATCH 09/13] docs(events-api): reworded --- .../data-apis/ingest-apis/event-api/incident-event-rest-api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx b/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx index bfe4ac8be46..f567a77afaf 100644 --- a/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx +++ b/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx @@ -136,7 +136,7 @@ Here's an example of a NerdGraph query and its result. The incident event API uses the Event API's value types. For descriptions of these value types and guidelines on using them, see [our event API JSON guidelines](/docs/data-apis/ingest-apis/introduction-event-api/#json-guidelines). - If you create two trigger events with the exact same aggregationTag, they will be aggregated to the same incident. + If you create two trigger events with the exact same aggregationTag, they will be aggregated to the same incident. Meaning, only one incident will be created from multiple triggers.
From 1f152f1ea5dcaefb7d746988e67eb1cd6dff9f5a Mon Sep 17 00:00:00 2001 From: Adar Maor Date: Thu, 15 Aug 2024 18:29:55 +0300 Subject: [PATCH 10/13] docs(events-api): Added another clarifying statement --- .../ingest-apis/event-api/incident-event-rest-api.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx b/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx index f567a77afaf..a5390ae5370 100644 --- a/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx +++ b/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx @@ -12,7 +12,8 @@ redirects: freshnessValidatedDate: never --- -You can use the [Event API](/docs/data-apis/ingest-apis/introduction-event-api) to report custom alert incident events to New Relic. +You can use the [Event API](/docs/data-apis/ingest-apis/introduction-event-api) to report custom alert incident trigger events to New Relic. +This event will trigger the creation of an incident. It does not directly create an incident. The API is an asynchronous endpoint. This means you can send a large volume of POSTS, reliably, with low-response latency. From 9c5df864579348e921709b83f593f5ba47255175 Mon Sep 17 00:00:00 2001 From: nbaenam Date: Fri, 16 Aug 2024 11:42:51 +0200 Subject: [PATCH 11/13] style(APIS): Added TW edits --- .../ingest-apis/event-api/incident-event-rest-api.mdx | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx b/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx index a5390ae5370..686ee2d3f22 100644 --- a/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx +++ b/src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx @@ -13,7 +13,7 @@ freshnessValidatedDate: never --- You can use the [Event API](/docs/data-apis/ingest-apis/introduction-event-api) to report custom alert incident trigger events to New Relic. -This event will trigger the creation of an incident. It does not directly create an incident. +This event does not directly create an incident, but it does trigger the creation of the incident. The API is an asynchronous endpoint. This means you can send a large volume of POSTS, reliably, with low-response latency. @@ -137,8 +137,9 @@ Here's an example of a NerdGraph query and its result. The incident event API uses the Event API's value types. For descriptions of these value types and guidelines on using them, see [our event API JSON guidelines](/docs/data-apis/ingest-apis/introduction-event-api/#json-guidelines). - If you create two trigger events with the exact same aggregationTag, they will be aggregated to the same incident. Meaning, only one incident will be created from multiple triggers. + If you create two trigger events with the exact same `aggregationTag`, they will be aggregated to the same incident. Meaning, only one incident is created from multiple triggers. +
@@ -167,9 +168,9 @@ The incident event API uses the Event API's value types. For descriptions of the Any attribute prefixed with `aggregationTag` will be used to aggregate trigger events together. - In other words, two trigger events with the same aggregation tags are aggregated to the same incident. (Under the assumption that none of the trigger events are resolve events). + In other words, two trigger events with the same aggregation tags are aggregated to the same incident. (Assuming none of the trigger events are resolve events). - When resolving incidents, it’s important that the resolve event include the same aggregation tags. + When resolving incidents, it's important that the resolve event include the same aggregation tags. Aggregations tags with reserved keywords are filtered out. For example, in a JSON payload with `aggregationTag.priority: 2` this key-value pair will be omitted in the incident event with these reserved keywords: From 03eff505e54d410011e544b7e4471b10176c444b Mon Sep 17 00:00:00 2001 From: svc-docs-eng-opensource-bot Date: Mon, 19 Aug 2024 16:12:32 +0000 Subject: [PATCH 12/13] chore(whats-new-ids): updated ids --- src/data/whats-new-ids.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/data/whats-new-ids.json b/src/data/whats-new-ids.json index ddb622a235a..85b32b33785 100644 --- a/src/data/whats-new-ids.json +++ b/src/data/whats-new-ids.json @@ -339,5 +339,6 @@ "/whats-new/2024/08/whats-new-08-12-synthetics-browsers": "42995", "/whats-new/2024/05/whats-new-05-08-sessiontraces": "42996", "/whats-new/2024/07/whats-new-07-02-apmk8s": "42997", - "/whats-new/2024/08/whats-new-8-15-one-step-AWS": "42998" + "/whats-new/2024/08/whats-new-8-15-one-step-AWS": "42998", + "/whats-new/2024/08/Configure_incident_titles": "42999" } \ No newline at end of file From 0bd2b4a8dd0c9b46bc0e8e099fd2f89c1281cec3 Mon Sep 17 00:00:00 2001 From: Shawn Kilburn Date: Mon, 19 Aug 2024 09:40:10 -0700 Subject: [PATCH 13/13] style(Lambda): Fixed some minor style issues --- .../opentelemetry/otel-adot-log-ingestion-serverless.mdx | 6 +++--- src/nav/serverless-function-monitoring.yml | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx index 0e0114cce99..6acbde4b421 100644 --- a/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx +++ b/src/content/docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless.mdx @@ -1,5 +1,5 @@ --- -title: Forward your Lambda function logs with Newrelic and OpenTelelemtry +title: Forward your Lambda function logs with New Relic and OpenTelelemtry metaDescription: How to instrument your serverless applications on AWS Lambda with ADOT solution in New Relic. freshnessValidatedDate: never --- @@ -60,7 +60,7 @@ Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amaz true
- `true`,`false`. + `true`,`false` Determines if logs are forwarded to the New Relic UI @@ -76,7 +76,7 @@ Open the [AWS Serverless Application Repository](https://serverlessrepo.aws.amaz false - `true`,`false`. + `true`,`false` diff --git a/src/nav/serverless-function-monitoring.yml b/src/nav/serverless-function-monitoring.yml index e3d06971459..7ec73b9e8a7 100644 --- a/src/nav/serverless-function-monitoring.yml +++ b/src/nav/serverless-function-monitoring.yml @@ -25,7 +25,7 @@ pages: path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-java - title: Trace your .NET Lambda functions with New Relic and OpenTelemetry path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/lambda-opentelemetry-dotnet - - title: Forward your Lambda function logs with Newrelic and OpenTelelemtry + - title: Forward your Lambda function logs with OpenTelemetry path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless - title: UI and data pages: