Merge pull request #13905 from newrelic/daily-release/Jul-18-2023-3_31

daily-release/Jul-18-2023-3_31

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/eligibility-guidelines-new-relic-nonprofit-program.mdx

@@ -17,7 +17,7 @@ This document provides New Relic's Observability for Good program eligibility gu
 
 ## Exceptions
 
-Many global nonprofit, charity and NGO organizations are eligible for Observability for Good if the organization has a recognized legal status in their respective country equal to 501(c)(3) status under the United States Internal Revenue Code, with certain exceptions. In addition, all organizations must be verified by [TechSoup](https://www.techsoup.global/techsoup-local-ngo-definitions) or the local TechSoup partner.
+Many global nonprofit, charity and NGO organizations are eligible for Observability for Good if the organization has a recognized legal status in their respective country equal to 501(c)(3) status under the United States Internal Revenue Code, with certain exceptions. In addition, all organizations must be verified by our global validation partners, [Percent](https://poweredbypercent.com/), [TechSoup](https://www.techsoup.global/techsoup-local-ngo-definitions), or the local TechSoup partner.
 
 Examples of ineligible organizations include, but are not limited to:
 
@@ -145,11 +145,14 @@ Examples of ineligible organizations include, but are not limited to:
 In order to participate, approved organizations must also:
 
 * Submit an application through [newrelic.org/signup](https://www.newrelic.org/signup).
-* Complete the eligibility validation process through TechSoup.
+* Complete the eligibility validation process through one of our validation partners Percent or TechSoup.
 
   <Callout variant="tip">
-    Learn about TechSoups local NGO [definitions](https://www.techsoup.global/techsoup-local-ngo-definitions).
+    Learn about our validation partners' local NGO definitions: 
+    * [Percent's Local NGO definitions](https://poweredbypercent.com/nonprofit-definitions/)
+    * [TechSoup's Local NGO definitions](https://www.techsoup.global/techsoup-local-ngo-definitions)
   </Callout>
+
 * Accept New Relic's standard [terms of service](https://newrelic.com/terms).
 * Be a direct customer of New Relic and have a direct billing relationship with New Relic.
 
@@ -185,7 +188,7 @@ To learn more or to sign up as a new or existing New Relic customer, go to [newr
 * Participating nonprofits can choose between the Standard or Pro edition. 
 * Standard is available via online validation and fulfillment and is a great place to start for most nonprofits.
 * Pro includes many additional features such as single sign-on (SSO) and the ability to customize the retention schedule for your Data.
-  * To request O4G Pro edition or find out more, please contact us at NPDealDesk@newrelic.com.
+  * To request O4G Pro edition or find out more, please contact us at o4ginfo@newrelic.com.
 
   <Callout variant="tip">
     A payment method on file is required for accounts using Observability for Good Pro.

src/content/docs/alerts-applied-intelligence/notifications/notification-integrations.mdx

@@ -723,15 +723,17 @@ If successful, there'll be a link to view the incident in JIRA.
   >
     ### Webhook template for Splunk On-call
 
-     Send notifications from Workflows to Splunk On-call using a [webhook template](https://help.victorops.com/knowledge-base/new-relic-integration-guide/#about-splunk-on-call-and-new-relic)
+     Send notifications from workflows to Splunk On-call using a [webhook template](https://help.victorops.com/knowledge-base/new-relic-integration-guide/#about-splunk-on-call-and-new-relic)
   </Collapser>
 
   <Collapser
     className="freq-link"
     id="webhook"
     title="Webhook"
   >
-  Use the webhook notifier to send the notification messages to any endpoint you like.
+You should use a webhook notifier in Workflows to send notification messages to a specified HTTPS endpoint. By default, the notifier assumes that the content type of the request is JSON and makes an HTTP POST request to the given endpoint. When you start configuring it, the webhook notifier provides a default JSON payload structure that you can use out of the box. However, if you require more customization, you can modify the payload using Handlebars template syntax. This allows you to populate variables within the payload dynamically, tailoring it to your specific needs.
+
+In addition to the payload, you also have the ability to include additional HTTP headers in the webhook request. This can be useful for passing extra information or authentication tokens to the receiving endpoint. Here is a video tutorial for setting up webhooks.
 
     <Video
       type="wistia"
@@ -747,8 +749,8 @@ If successful, there'll be a link to view the incident in JIRA.
   2. Enter the following information: 
 
      * **Webhook name:** Reference name for your webhook.
-     * **Endpoint URL:** The endpoint of the target application, authentication and custom headers if needed.
-     * **Use authorization:** (Optional) You can choose between `basic authentication` or `bearer token`.
+     * **Endpoint URL:** The endpoint of the target application where an HTTP POST request will be sent. 
+     * **Use authorization:** (Optional) You can choose between `Basic Authentication` or `Bearer Token`.
 
   <img
       width="80%;"
@@ -757,22 +759,26 @@ If successful, there'll be a link to view the incident in JIRA.
       src={accountsWebhookDestination}
     />
 
+If you're new to working with webhooks and want to test the configuration and examine webhook payloads without writing a service, you can use HTTP catch-all services. [Beeceptor](https://beeceptor.com) and [Webhook.site](https://webhook.site) are examples of services that give you a designated URL where you can receive HTTP payloads and then inspect the JSON payload of the event. This feature is valuable for gathering relevant information before starting your development process.
+
+If you're building a new service to consume this payload you must test it locally. Using local tunnels is a good idea for testing and debugging webhooks in a local environment before deploying to a production server. These tunnels allow you to receive incoming webhook requests from New Relic on your local machine, eliminating the need for a publicly accessible server during development. Tools like Beeceptor or ngrok enable you to create a temporary public URL that forwards requests to your local server by specifying the desired application port or address. This expedites iteration and debugging, as you can directly observe and analyze webhook payloads in your local development environment.
 
 ### Two-way sync [#two-way-webhook]
 
 For notifications sent from workflows, you can acknowledge or close issues using [Nerdgraph](/docs/apis/nerdgraph/examples/nerdgraph-issues-api-via-github/#resolve-ack-issues).
 
+If you are testing two-way sync with webhooks, you can use Beeceptor's customized response status and payload templates. This allows you to draft a desired response when acknowledging the received events.
 
 ### Configure the webhook event template [#configure-webhook-event-template]
 
 Pick a webhook destination from the list, and configure the `HTTP-POST` request.
 
 The request configuration requires you to:
 
-      1. Set a name for the template.
-      2. Select a pre-configured destination from the destinations list or create a new one.
-      3. Add custom headers (optional).
-      4. Configure the request's payload.
+1. Set a name for the template.
+2. Select a pre-configured destination from the destinations list or create a new one.
+3. Add custom headers (optional).
+4. Configure the request's payload.
 
 
 ### Customize the webhook payload in Workflows [#customize-webhook-payload]

src/content/docs/apm/agents/manage-apm-agents/agent-data/triage-run-diagnostics.mdx

@@ -1,10 +1,10 @@
 ---
-title: Troubleshoot with the summary page
+title: Troubleshoot with the APM summary page
 tags:
   - APM
   - Triage
   - Diagnostics
-metaDescription: Run diagnostics with application monitoring tools to quickly resolve incidents.
+metaDescription: With the New Relic APM summary page, run diagnostics with application monitoring tools to quickly resolve incidents.
 redirects:
   - /docs/apm/apm-ui-pages/monitoring/apm-summary-page-view-transaction-apdex-usage-data/
   - /docs/applications-dashboards/applications-overview
@@ -106,8 +106,7 @@ For more about how to understand your score, see [Apdex: measure user satisfacti
     src={apmWebTransactionsinAPM}
 />
 
-
-Based on customer reports you know that the `Pay Now` button is failing in your app but you're unsure of what's causing the actual error. You've checked Apdex and it's showing poor user satisfaction. 
+Based on customer reports you know that the `Pay now` button is failing in your app but you're unsure of what's causing the actual error. You've checked Apdex and it's showing poor user satisfaction. 
 
 The next step is to figure out which part of the checkout process is breaking by investigating your app's **Web-transactions**.  
 
@@ -142,7 +141,7 @@ A deployment marker shows up as a gray pin on the each chart. You can hover over
     src={apmThroughputinApm}
 />
 
-While looking at the response times for`Checkout-service` you can also investigate throughput. **Throughput** is a way to measure the amount of work your application is handling. Throughput helps you understand if work is evenly distributed between your hosts and containers. Performance issues can often be a symptom of lack of resources.
+While looking at the response times for `Checkout-service` you can also investigate throughput. **Throughput** is a way to measure the amount of work your application is handling. Throughput helps you understand if work is evenly distributed between your hosts and containers. Performance issues can often be a symptom of lack of resources.
 
 For the purposes of this example, you see that throughput is a little higher than usual. If your throughput is very high during a time of service degradation, it could indicate that your application is processing more work than it can handle.  
 
@@ -160,7 +159,6 @@ On the other hand, low throughput could indicate that your app isn't handling ve
     src={apmErrorsinAPM}
 />
 
-
 Now that you've identified slow transactions and analyzed your throughput, it's time to take a look at errors. The **Errors** chart shows you the percentage of transactions that resulted in an error. 
 
 In the context of APM, errors represent the `TransactionError` and `ErrorTrace` events.

src/content/docs/apm/agents/manage-apm-agents/app-naming/name-your-application.mdx

@@ -97,6 +97,8 @@ Each unique app name creates a new application record in your New Relic UI, whic
 
 To change the app name, set the app name value in the agent's configuration file. If you have deployed an app via one APM agent, and then deploy another app with the same name via a different APM agent, New Relic will automatically append the agent language name to the end of the second app's name. For example, if you deploy a Node.js app named `New-App`, and then deploy a .NET app named `New-App`, New Relic will automatically append the second app name as `New-App (DOTNET)`.
 
+To ensure compliance with naming conventions, please note that the symbols `<` and `>` are not permitted in the application name. If these symbols are included, they will be automatically removed. Please ensure that your application name adheres to this requirement.
+
 <table>
   <thead>
     <tr>

src/content/docs/data-apis/custom-data/aws-privatelink.mdx

@@ -3,7 +3,7 @@ title: Send New Relic data via AWS PrivateLink
 metaDescription: Send telemetry from your VPC to New Relic via AWS PrivateLink
 ---
 
-import awsCreateVpcEndpointUi from 'images/accounts_screenshot-full_aws-create-vpc-endpoint-ui.png'
+import awsCreateVpcEndpointUi from 'images/accounts_screenshot-full_aws-create-vpc-endpoint-ui.webp'
 
 You can send telemetry data from your AWS Virtual Private Cloud (VPC) to New Relic via [AWS PrivateLink](https://aws.amazon.com/privatelink).
 

src/content/docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-13-0.mdx

@@ -0,0 +1,47 @@
+---
+subject: .NET agent
+releaseDate: '2023-07-18'
+version: 10.13.0
+downloadLink: 'https://download.newrelic.com/dot_net_agent/latest_release'
+features: ['Add support for filtering log events based on a list of log levels so that they are not forwarded to New Relic. Also adds new logging metrics to count the total number of filtered log events (Logging/denied).', 'Instrument OpenAsync() for SQL libraries.']
+bugs: ['Refactor StackExchange.Redis v2+ instrumentation to eliminate potential memory leaks.', 'Remove invalid trailing comma added to W3C tracestate header.', 'Update the MSI UI to clean up formatting and readability issues.']
+security: ['Update Grpc.Net.Client library to address Dependabot alerts.']
+---
+
+### Security
+
+* Update Grpc.Net.Client library to address Dependabot alerts. ([#1768](https://github.com/newrelic/newrelic-dotnet-agent/issues/1768)) ([#1769](https://github.com/newrelic/newrelic-dotnet-agent/issues/1769)) ([eee7564](https://github.com/newrelic/newrelic-dotnet-agent/commit/eee7564cbe79b653ad7909af36f09c9a64cdb731))
+
+### New Features
+
+* Add support for filtering log events based on a list of log levels so that they are not forwarded to New Relic. Also adds new logging metrics to count the total number of filtered log events (Logging/denied). Refer to our [application logging configuration](https://docs.newrelic.com/docs/apm/agents/net-agent/configuration/net-agent-configuration/#application_logging) documentation for more details. ([#1760](https://github.com/newrelic/newrelic-dotnet-agent/issues/1760)) ([#1761](https://github.com/newrelic/newrelic-dotnet-agent/issues/1761)) ([#1762](https://github.com/newrelic/newrelic-dotnet-agent/issues/1762)) ([#1766](https://github.com/newrelic/newrelic-dotnet-agent/issues/1766)) ([aadce3a](https://github.com/newrelic/newrelic-dotnet-agent/commit/aadce3a09f9fe3c77a93f557686f1ddc26fc6169))
+* Instrument OpenAsync() for SQL libraries. ([#1725](https://github.com/newrelic/newrelic-dotnet-agent/issues/1725)) ([a695ce6](https://github.com/newrelic/newrelic-dotnet-agent/commit/a695ce6de7e56bc3f803c9b9f6c8c09b30c106fd))
+
+### Fixes
+
+* Refactor StackExchange.Redis v2+ instrumentation to eliminate potential memory leaks. ([902b025](https://github.com/newrelic/newrelic-dotnet-agent/commit/902b025c8c420b8bc288b15d914b47aabc1bd426))
+* Remove invalid trailing comma added to W3C tracestate header. ([#1779](https://github.com/newrelic/newrelic-dotnet-agent/issues/1779)) ([790a3b7](https://github.com/newrelic/newrelic-dotnet-agent/commit/790a3b75dd7609d76638ea3625a9289f58b24378))
+* Update the MSI UI to clean up formatting and readability issues. ([#1748](https://github.com/newrelic/newrelic-dotnet-agent/issues/1748)) ([3fbc543](https://github.com/newrelic/newrelic-dotnet-agent/commit/3fbc54310ed3989f915e6f39b27ef8867ed573db))
+
+Once published, you can find the release artifacts for this release [here](https://download.newrelic.com/dot_net_agent/latest_release/) or on [NuGet.org](https://www.nuget.org/).
+
+### Checksums
+| File | SHA - 256  Hash |
+| ---| ---|
+| newrelic-dotnet-agent-10.13.0-1.x86_64.rpm | E589D2BD0DA972CB8ECE27A2BCC55E5EC5724F049AEF1993606F1AFBCE7E34B9 |
+| newrelic-dotnet-agent_10.13.0_amd64.deb | BB8A5F34E85CAA468BEFED90803339A49E6139618CAB208493772F76F95E1321 |
+| newrelic-dotnet-agent_10.13.0_amd64.tar.gz | 730089417451F14E749BBAF5B66482FDBA920CE0D313999A1AB51F6F6388C613 |
+| newrelic-dotnet-agent_10.13.0_arm64.deb | 9079245A6BCA2589B8A6A71AD62B8BE1944BA3B3F6A56446FE488385E6E70AE1 |
+| newrelic-dotnet-agent_10.13.0_arm64.tar.gz | DFAC11B4E07118F2C1F1E28F78785CE61EE96D1EEFAD1F3116F83994AD60B59E |
+| NewRelicDotNetAgent_10.13.0_x64.msi | 5B37B9736B32B0D32466115066BC43EB5D1D59C08749E5BB5A04A1431B31907A |
+| NewRelicDotNetAgent_10.13.0_x64.zip | EDE778E4393772439BAE0EFB5266604A18028CBBB955B9A40C543ECAEF6B51F9 |
+| NewRelicDotNetAgent_10.13.0_x86.msi | A66A75309281CBC902E393EC391F0FBB849A7BA9F115E4F72C82A830EC2E5312 |
+| NewRelicDotNetAgent_10.13.0_x86.zip | 9B9A94D705B66C326FCE83794B08D6C45EEEC4BF796B4F9E1B994DFBFB587407 |
+
+### Updating
+
+* Follow standard procedures to [update the .NET agent](/docs/agents/net-agent/installation-configuration/update-net-agent).
+* If you're using a particularly old agent, review the list of major changes and procedures for [updating legacy .NET agents](/docs/agents/net-agent/troubleshooting/upgrade-legacy-net-agents).
+
+We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about [keeping your agent up to date](/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent).
+See the New Relic .NET agent [EOL policy doc](/docs/apm/agents/net-agent/getting-started/net-agent-eol-policy) for information about agent releases and support dates.

src/data/whats-new-ids.json

@@ -265,5 +265,6 @@
   "/whats-new/2023/06/whats-new-06-23-synthetics-horde-ip-changes": "42915",
   "/whats-new/2023/06/Interactive scorecards": "42916",
   "/whats-new/2023/06/whats-new-06-26-apm360": "42917",
-  "/whats-new/2023/06/Query_enhancements": "42918"
+  "/whats-new/2023/06/Query_enhancements": "42918",
+  "/whats-new/2023/07/summer_series_WN": "42919"
 }

src/i18n/content/jp/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/change-applied-intelligence-correlation-logic-decisions.mdx

@@ -319,7 +319,7 @@ import alertsTopology3 from 'images/alerts_diagram_topology-3.webp'
 
 ## カスタム決定を作成する [#customize]
 
-独自のカスタム決定を作成することで、ノイズを減らし、相関を改善できます。決定の作成を開始するには、 **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI** > **Decisions**に移動し、 **Create new decision**をクリックします。
+独自のカスタム決定を構築することで、ノイズを削減し、相関関係を改善できます。意思決定の作成を開始するには、 **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Decisions**に移動し、 **Create new decision** \[新しい意思決定の作成] をクリックします。
 
 意思決定ビルダーには 2 つのバージョンがあります。
 
@@ -483,7 +483,7 @@ import alertsTopology3 from 'images/alerts_diagram_topology-3.webp'
 
 高度な意思決定ビルダーを使用するには:
 
-1. **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI** > **Decisions**に移動します。
+1. **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI > Decisions**に移動します。
 2. **Create new decision**をクリックし、 **Use advanced builder**をクリックします。
 
 利用可能なオプションの詳細については、読み続けてください。