Merge branch 'develop' of https://github.com/newrelic/docs-website in…

…to release-es-pt

.github/workflows/build-notification.yml

@@ -14,7 +14,7 @@ on:
         type: choice
         options:
           - building
-          - succeeded
+          - ready
           - failed
       deployUrl:
         description: URL of live branch deploy
@@ -47,7 +47,7 @@ jobs:
           END
               )
               ;;
-            "succeeded")
+            "ready")
               comment_body=$(cat <<-END
           ### <span aria-hidden="true">✅</span> Deploy Preview ready!
 
@@ -105,8 +105,8 @@ jobs:
             -f context='netlify/build' \
             /repos/${{ env.repo }}/statuses/${{ inputs.sha }}
 
-      - name: update PR check - succeeded
-        if: ${{ inputs.buildStatus == 'succeeded' }}
+      - name: update PR check - ready
+        if: ${{ inputs.buildStatus == 'ready' }}
         env: 
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |

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

@@ -295,7 +295,7 @@ Click a test notification with default field values to see the Jira issue. If su
 
 
   From the Workflow main page, you can enable, edit, delete, or copy workflow id to clipboard the created workflow.
-
+    
   </Collapser>
 
   <Collapser

src/content/docs/apis/nerdgraph/examples/nerdgraph-streaming-export.mdx

@@ -418,6 +418,8 @@ If you do encounter this issue and you're exporting to S3 or another file storag
 
 Once you have the compressed data, you can re-upload it to S3 (or whatever other service you're using) and delete the old file.
 
+Please be aware that in S3 or another file storage system, objects may consist of multiple GZIP-encoded payloads that are appended consecutively. Therefore, your decompression library should have the capability to handle such concatenated GZIP payloads.
+
 ### Automatic Decompression in AWS
 
 Once your data has arrived in AWS, you may want options to automatically decompress it. If you're streaming that data to an S3 bucket, there are two ways to enable automatic decompression:
@@ -437,6 +439,7 @@ Once your data has arrived in AWS, you may want options to automatically decompr
 
   <Collapser id="collapser-2" title="Metadata-setting Lambda function">
     AWS will automatically decompress objects downloaded from S3, if those objects have the correct metadata set. We have written a function that automatically applies this metadata to every new object downloaded to a set S3 object. Here's how to set it up:
+
     1. Navigate [here](https://github.com/newrelic/metadata-setting-lambda-function), clone the repository locally, and follow the provided steps in the README file to generate a ZIP file containing the lambda function.
     2. Create an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) for the function.
     * When [creating the role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html#roles-creatingrole-service-console), be sure to set the trusted entity type as "AWS Service", with "Lambda" as your use case.
@@ -449,11 +452,12 @@ Once your data has arrived in AWS, you may want options to automatically decompr
     8. Once the function has been created, click <DoNotTranslate>**Upload from**</DoNotTranslate> and select <DoNotTranslate>**.zip or .jar file**</DoNotTranslate> from the dropdown.
     9. Click <DoNotTranslate>**Upload**</DoNotTranslate> from the box that pops up, and select the ZIP file created in step 1.
     10. Once the upload has finished, click <DoNotTranslate>**Save**</DoNotTranslate> to exit the pop-up box.
-    11. All that's left to do now is enable this Lambda function to trigger on S3 object creation. Click <DoNotTranslate>**Add trigger**</DoNotTranslate> to start setting that up.
-    12. From the dropdown, select <DoNotTranslate>**S3**</DoNotTranslate> as your source.
-    13. Enter the name of the S3 bucket you'd like to apply the metadata to in the <DoNotTranslate>**Bucket**</DoNotTranslate> field.
-    14. Remove the default <DoNotTranslate>**All object create events**</DoNotTranslate> from the event types. From the Event types dropdown, select <DoNotTranslate>**PUT**</DoNotTranslate>.
-    15. Check the <DoNotTranslate>**Recursive invocation**</DoNotTranslate> box, then click <DoNotTranslate>**Add**</DoNotTranslate> in the bottom right.
+    11. Edit <DoNotTranslate>**Runtime settings**</DoNotTranslate> by adding the handler. In our provided function the handler is <DoNotTranslate>`metadatasetter.App::handleRequest`</DoNotTranslate>. 
+    12. All that's left to do now is enable this Lambda function to trigger on S3 object creation. Click <DoNotTranslate>**Add trigger**</DoNotTranslate> to start setting that up.
+    13. From the dropdown, select <DoNotTranslate>**S3**</DoNotTranslate> as your source.
+    14. Enter the name of the S3 bucket you'd like to apply the metadata to in the <DoNotTranslate>**Bucket**</DoNotTranslate> field.
+    15. Remove the default <DoNotTranslate>**All object create events**</DoNotTranslate> from the event types. From the Event types dropdown, select <DoNotTranslate>**PUT**</DoNotTranslate>.
+    16. Check the <DoNotTranslate>**Recursive invocation**</DoNotTranslate> box, then click <DoNotTranslate>**Add**</DoNotTranslate> in the bottom right.
 
     The Lambda function will now start automatically adding the compression metadata to all newly added S3 objects.
   </Collapser>

src/content/docs/apis/synthetics-rest-api/monitor-examples/manage-synthetics-monitors-rest-api.mdx

@@ -218,7 +218,7 @@ https://synthetics.eu.newrelic.com/synthetics/api
     "frequency": integer (minutes) [required, must be one of 1, 5, 10, 15, 30, 60, 360, 720, or 1440],
     "uri": string [required for SIMPLE and BROWSER type],
     "locations": array of strings [at least one required],
-    "status": string (ENABLED, MUTED, DISABLED) [required],
+    "status": string (ENABLED, DISABLED) [required],
     "slaThreshold": double,
     "options": {
       "validationString": string [only valid for SIMPLE and BROWSER types],
@@ -440,7 +440,7 @@ In addition to the general API, there are several API methods for the scripted b
 
     Calculation steps:
 
-    1. Calculate the HMAC value from the script. One way is to use:  
+    1. Calculate the HMAC value from the script. One way is to use:
        `cat script | openssl dgst -sha256 -hmac "password" > hmac`
     2. Remove the newline character if one was added by openssl.
     3. Encode the HMAC in BASE64 without line breaks.
@@ -463,20 +463,20 @@ Here is an example of using New Relic's REST API and the bash script to create a
 
       ```
       var assert = require("assert");
-      $browser.get("http://example.com").then(function(){ 
-        // Check the H1 title matches "Example Domain" 
-        return $browser.findElement($driver.By.css("h1")).then(function(element){ 
-          return element.getText().then(function(text){ 
-            assert.equal("Example Domain", text, "Page H1 title did not match"); 
-          }); 
-        }); 
-      }).then(function(){ 
-        // Check that the external link matches "http://www.iana.org/domains/example" 
-        return $browser.findElement($driver.By.css("div > p > a")).then(function(element){ 
-          return element.getAttribute("href").then(function(link){ 
-            assert.equal("http://www.iana.org/domains/example", link, "More information link did not match"); 
-          }); 
-        }); 
+      $browser.get("http://example.com").then(function(){
+        // Check the H1 title matches "Example Domain"
+        return $browser.findElement($driver.By.css("h1")).then(function(element){
+          return element.getText().then(function(text){
+            assert.equal("Example Domain", text, "Page H1 title did not match");
+          });
+        });
+      }).then(function(){
+        // Check that the external link matches "http://www.iana.org/domains/example"
+        return $browser.findElement($driver.By.css("div > p > a")).then(function(element){
+          return element.getAttribute("href").then(function(link){
+            assert.equal("http://www.iana.org/domains/example", link, "More information link did not match");
+          });
+        });
       });
       ```
   </Collapser>

src/content/docs/apis/synthetics-rest-api/monitor-examples/payload-attributes-synthetics-rest-api.mdx

@@ -138,7 +138,7 @@ Here are the attributes that can be used when creating and managing monitors wit
       </td>
 
       <td>
-        String: Valid values include `ENABLED`, `MUTED`, and `DISABLED`.
+        String: Valid values include `ENABLED` and `DISABLED`.
       </td>
     </tr>
 

src/content/docs/apm/agents/go-agent/configuration/go-agent-code-level-metrics-config.mdx

@@ -89,7 +89,7 @@ There are additional configuration options you may wish to use to further refine
 
 <CollapserGroup>
   <Collapser
-    id="errors-inbox configuration"
+    id="errors-inbox-configuration"
     title="Errors inbox configuration"
   >
 

src/content/docs/apm/agents/java-agent/api-guides/java-agent-api-custom-instrumentation-annotation-example-app.mdx

@@ -232,7 +232,7 @@ Here is the same example app divided into sections that describe how the API is
     id="record-user-id"
     title="Record the user ID"
   >
-    This part of the API call inserts additional metadata into the [page load timing](/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process) request so that browser traces can be tied with the `userId`. It also records the `userId` as a custom parameter on the transaction so that it appears in the [parameter details of a transaction trace](/docs/apm/transactions/transaction-traces/transaction-trace-details). (Page load timing sometimes is referred to as real user monitoring or RUM.)
+    This part of the API call inserts additional metadata into the [page load timing](/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process) request so that browser traces can be tied with the `userId`. It also records the `userId` as a custom parameter on the transaction so that it appears in the [parameter details of a transaction trace](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page). (Page load timing sometimes is referred to as real user monitoring or RUM.)
 
     ```java
     String userId = req.getParameter("userId");

src/content/docs/apm/agents/java-agent/configuration/configuring-your-ssl-certificates.mdx

@@ -26,7 +26,7 @@ For SSL connection issues, please visit [SSL or connection errors (Java)](/docs/
 <Callout variant="important">
   Java agent versions higher than 6.4.2 no longer ship with SSL certificates bundled into the agent. You must provide your own SSL truststore to the agent by explicitly using the [ca_bundle_path](/docs/agents/java-agent/configuration/java-agent-configuration-config-file#ca_config_bundle) configuration option, or by using the default truststore provided by the JDK/JRE (the agent will look to use the latter by default). Additionally the `use_private_ssl` configuration option has been removed from Java agent versions higher than 6.4.2.
 
-  Users wishing to add the global certificate to their local trust store can download the [DigiCert Global Root CA](https://www.digicert.com/kb/digicert-root-certificates.htm) from DigiCert.
+  Users wishing to add the global certificate to their local trust store can download the [DigiCert Global Root CA](https://www.digicert.com/kb/digicert-root-certificates.htm) from DigiCert under the "Other root certificates" section.
 </Callout>
 
 ## Java agent versions 6.2.0 - 6.4.2

src/content/docs/apm/agents/java-agent/instrumentation/use-rabbitmq-or-jms-message-queues.mdx

@@ -112,6 +112,6 @@ Queue operations appear in APM's [<DoNotTranslate>**Transactions**</DoNotTransla
 
 Other places RabbitMQ information may appear: 
 
-* The [<DoNotTranslate>**Transaction trace summary**</DoNotTranslate> page](/docs/apm/transactions/transaction-traces/transaction-trace-summary) may show `Put` and `Take` operations in the <DoNotTranslate>**Slowest components**</DoNotTranslate> section. 
-* The <DoNotTranslate>**Transaction trace**</DoNotTranslate> page may include a dedicated <DoNotTranslate>**Messages**</DoNotTranslate> tab.
+* The [**Transaction trace summary** page](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page) may show `Put` and `Take` operations in the **Slowest components** section. 
+* The **Transaction trace** page may include a dedicated **Messages** tab.
 

src/content/docs/apm/agents/java-agent/troubleshooting/ssl-or-connection-errors-java.mdx

@@ -39,7 +39,7 @@ If you see either of these errors, your JDK instance probably is using a customi
 
 <DoNotTranslate>**Recommendation:**</DoNotTranslate> Add the DigiCert Global Root Certificate Authority (CA), from which New Relic's certificate is derived, to your trust store.
 
-You can download the [DigiCert Global Root CA](https://www.digicert.com/kb/digicert-root-certificates.htm) from DigiCert (choose the "Download PEM" option).
+You can download the [DigiCert Global Root CA](https://www.digicert.com/kb/digicert-root-certificates.htm) from DigiCert under the "Other root certificates" section (choose the "Download PEM" option).
 
 To import the cert to your trust store, use this command, or see [Oracle's Java SE documentation for keytool](https://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html):
 

src/content/docs/apm/agents/manage-apm-agents/agent-data/agent-attributes.mdx

@@ -128,7 +128,7 @@ Collected attributes appear in these locations:
 
     <tr>
       <td>
-        [Transaction segments](/docs/apm/transactions/transaction-traces/transaction-trace-details)
+        [Transaction segments](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page)
       </td>
 
       <td>

src/content/docs/apm/agents/nodejs-agent/extend-your-instrumentation/message-queues.mdx

@@ -91,7 +91,7 @@ Queue operations appear on APM's [<DoNotTranslate>**Transactions**</DoNotTransla
   <DoNotTranslate>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > APM & services > Applications > (select an app) > Transactions > (select a transaction):**</DoNotTranslate> The transaction's <DoNotTranslate>**Breakdown table**</DoNotTranslate> categorizes queue operations as `MessageBroker` metrics and labels them as `Put` (publish a message) or `Take` (receive a message).
 </figcaption>
 
-The [<DoNotTranslate>**Transaction trace summary**</DoNotTranslate> page](/docs/apm/transactions/transaction-traces/transaction-trace-summary) may show `Put` and `Take` operations in the <DoNotTranslate>**Slowest components**</DoNotTranslate> section. For example:
+The [**Transaction trace summary** page](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page) may show `Put` and `Take` operations in the **Slowest components** section. For example:
 
 <img
   title="slow-message-component"

src/content/docs/apm/agents/python-agent/supported-features/python-message-queues.mdx

@@ -213,7 +213,7 @@ The `Put` (publish a message) and `Take` (receive a message) metrics appear in t
   You can [select transaction traces](/docs/apm/transactions/transaction-traces/viewing-transaction-traces) from the app's <DoNotTranslate>**Summary**</DoNotTranslate> or <DoNotTranslate>**Transactions**</DoNotTranslate> pages in APM.
 </Callout>
 
-The [<DoNotTranslate>**Transaction trace summary**</DoNotTranslate> page](/docs/apm/transactions/transaction-traces/transaction-trace-summary) may show `Put` and `Take` operations for RabbitMQ in the <DoNotTranslate>**Slowest components**</DoNotTranslate> section. For example:
+The [**Transaction trace summary** page](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page) may show `Put` and `Take` operations for RabbitMQ in the **Slowest components** section. For example:
 
 <img
   title="screen-rabbitmq-trace-slowest.png"

src/content/docs/apm/agents/ruby-agent/features/message-queues.mdx

@@ -106,7 +106,7 @@ Message queue operations are visible in several places in the APM UI:
     id="view-in-txn-trace-summary"
     title="Transaction trace summary page"
   >
-    The [<DoNotTranslate>**Transaction trace summary**</DoNotTranslate> page](/docs/apm/transactions/transaction-traces/transaction-trace-summary) may show `Put` and `Take` operations in the <DoNotTranslate>**Slowest components**</DoNotTranslate> section. For example:
+    The [**Transaction trace summary** page](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page) may show `Put` and `Take` operations in the **Slowest components** section. For example:
 
     <img
       title="trace_summary.png"

src/content/docs/apm/apm-ui-pages/features/analyze-database-instance-level-performance-issues.mdx

@@ -65,10 +65,10 @@ Use these examples as starting points to monitor and troubleshoot the performanc
     id="tx-trace-example"
     title="Transaction trace details example"
   >
-    Your app has a performance issue, and you have used the APM [Transactions](/docs/apm/applications-menu/monitoring/transactions-page) page to identify a suspect transaction. When you select a [transaction trace](/docs/apm/transactions/transaction-traces/transaction-trace-summary) for the slow transaction, you notice that the database time is the key contributor to the transaction performance.
+    Your app has a performance issue, and you have used the APM [Transactions](/docs/apm/applications-menu/monitoring/transactions-page) page to identify a suspect transaction. When you select a [transaction trace](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page) for the slow transaction, you notice that the database time is the key contributor to the transaction performance.
 
-    From the selected [transaction trace <DoNotTranslate>**Details**</DoNotTranslate>](/docs/apm/transactions/transaction-traces/transaction-trace-details), you select the <DoNotTranslate>**Database**</DoNotTranslate> <Icon name="fe-database"/>
-    icon to review the <DoNotTranslate>**Database query**</DoNotTranslate> information. This shows both the query details and the specific instance where the query was executed. From here you can use your database vendor tools to further diagnose the issue.
+    From the selected [transaction trace **Details**](/docs/apm/transactions/transaction-traces/transaction-traces-trace-details-page), you select the **Database** <Icon name="fe-database"/>
+    icon to review the **Database query** information. This shows both the query details and the specific instance where the query was executed. From here you can use your database vendor tools to further diagnose the issue.
 
     <img
       title="APM transaction trace: Database and instances information"