Merge pull request newrelic#13845 from brnhensley/patch-10

chore: add language identifiers/fix typos

Author: ally-sassman

src/content/docs/data-apis/ingest-apis/event-api/incident-event-rest-api.mdx

@@ -56,12 +56,12 @@ The `eventType` field must use `NrAiIncidentExternal`.
 
 Here's an example of how to use curl to send your JSON payload.
 
-```
+```bash
 gzip -c example_incidents.json | curl --data-binary @- -X POST -H "Content-Type: application/json" -H "Api-Key: YOUR_LICENSE_KEY" -H "Content-Encoding: gzip"
 https://insights-collector.newrelic.com/v1/accounts/YOUR_ACCOUNT/events
 ```
 
-```
+```json
 Response
 {"success":true, "uuid":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}%
 ```
@@ -74,7 +74,7 @@ You can query your data with [Nerdgraph API](/docs/apis/nerdgraph/get-started/in
 
 Here's an example of a NerdGraph query and its result.
 
-```json
+```graphql
 {
   actor {
     account(id: YOUR_ACCOUNT_ID) {
@@ -175,7 +175,7 @@ The incident event API uses the Event API's value types. For descriptions of the
       <td>
         `state`
 
-        _enum: (trigger, resolve)_
+        _enum: (`trigger`, `resolve`)_
       </td>
 
       <td>
@@ -189,11 +189,11 @@ The incident event API uses the Event API's value types. For descriptions of the
       <td>
         `priority`
 
-        _enum: (low, medium, high, critical)_
+        _enum: (`low`, `medium`, `high`, `critical`)_
       </td>
 
       <td>
-        The incident's priority. Default: _high_.
+        The incident's priority. Default: `high`.
 
         Highest priority will be used when different priorities are sent.
       </td>
@@ -207,7 +207,7 @@ The incident event API uses the Event API's value types. For descriptions of the
       </td>
 
       <td>
-        **REQUIRED, when `state` is _trigger_**
+        **REQUIRED, when `state` is `trigger`**
 
         The triggering event's title.
       </td>
@@ -221,7 +221,7 @@ The incident event API uses the Event API's value types. For descriptions of the
       </td>
 
       <td>
-        **REQUIRED, when `state` is _trigger_**
+        **REQUIRED, when `state` is `trigger`**
 
         The origin of the incident, or the monitoring system that triggered it (not the entity that faulted).
       </td>

src/content/docs/data-apis/ingest-apis/event-api/introduction-event-api.mdx

@@ -232,19 +232,19 @@ The Event API accepts specific formats for attributes included in the payload. O
   >
     Here is an example of a typical JSON data set for sending with the API. This call sends two **Purchase** type events as a JSON array. You can add multiple events in a single HTTP call using a JSON array.
 
-    ```
+    ```json
     [
-      {
-        "eventType":"Purchase",
-        "account":3,
-        "amount":259.54
-      },
-      {
-        "eventType":"Purchase",
-        "account":5,
-        "amount":12309,
-        "product":"Item"
-      }
+        {
+            "eventType": "Purchase",
+            "account": 3,
+            "amount": 259.54
+        },
+        {
+            "eventType": "Purchase",
+            "account": 5,
+            "amount": 12309,
+            "product": "Item"
+        }
     ]
     ```
 
@@ -283,7 +283,7 @@ Data submitted to the Event API uses a compressed JSON format in a simple HTTPS
     id="numberone"
     title="Linux/bash example"
   >
-    ```
+    ```bash
     gzip -c example_events.json | curl -X POST -H "Content-Type: application/json"
     -H "Api-Key: YOUR_LICENSE_KEY" -H "Content-Encoding: gzip"
     https://insights-collector.newrelic.com/v1/accounts/YOUR_ACCOUNT_ID/events --data-binary @-
@@ -294,7 +294,7 @@ Data submitted to the Event API uses a compressed JSON format in a simple HTTPS
     id="numbertwo"
     title="Windows/PowerShell example"
   >
-    ```
+    ```powershell
     $accountId = "YOUR_ACCOUNT_ID"
     $insertkey = "YOUR_LICENSE_KEY"
     # Replace with your custom event for the body
@@ -373,7 +373,7 @@ Other potential issues:
           </td>
 
           <td>
-            ```
+            ```json
             {"success":true,"uuid":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}
             ```
           </td>
@@ -592,7 +592,7 @@ Other potential issues:
 
 The [`NrIntegrationError` event](/docs/telemetry-data-platform/manage-data/nrintegrationerror) allows you to query and set alerts on custom data being sent to your New Relic account. **Recommendation:** To get alerts for parsing errors, [create a NRQL alert condition](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) for `NrIntegrationError`. Use this example NRQL query:
 
-```
+```sql
 SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND category = 'EventApiException'
 ```
 
@@ -654,7 +654,7 @@ SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND c
 
     <tr>
       <td>
-        `Category`
+        `category`
       </td>
 
       <td>
@@ -664,7 +664,7 @@ SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND c
 
     <tr>
       <td>
-        `Message`
+        `message`
       </td>
 
       <td>
@@ -674,7 +674,7 @@ SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND c
 
     <tr>
       <td>
-        `Name`
+        `name`
       </td>
 
       <td>
@@ -698,7 +698,7 @@ SELECT message FROM NrIntegrationError WHERE newRelicFeature = 'Event API' AND c
 
 To find data sent via the Event API (and from integrations that use this API), you can query it. For example, to query a custom event using [NRQL](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql), you would run:
 
-```
+```sql
 SELECT * FROM YOUR_CUSTOM_EVENT
 ```
 

src/content/docs/data-apis/ingest-apis/gateway-api-import-data-other-observability-platforms.mdx

@@ -28,7 +28,7 @@ Here's an overview of the steps for enabling the Gateway API for DataDog:
 1. For DataDog: Our account representatives will work with you to map your Datadog API keys to New Relic keys.
 2. For each agent configuration file, point the data to `https://gateway.service.newrelic.com`. An example for DataDog: in the agent’s `datadog.yaml` file, you’d change these settings:
 
-   ```
+   ```yml
    dd_url: https://gateway.service.newrelic.com
    logs_config:
        logs_dd_url:  https://gateway.service.newrelic.com
@@ -48,4 +48,4 @@ Telemetry data brought in from third-party platforms doesn't map perfectly to ou
 
 <Callout variant="tip">
 Interested in unifying your data observability into a single platform? See our [guide on migrating from Datadog](/docs/journey-migration/migrating-from-dd/) to try it out for free.
-</Callout>
+</Callout>

src/content/docs/logs/log-api/use-tcp-endpoint-forward-logs-new-relic.mdx

@@ -42,7 +42,7 @@ To forward logs to New Relic with `rsyslog` for Amazon Linux, Redhat, and Centos
 3. In the `/etc/rsyslog.d/` directory, create a text file named `newrelic.conf`.
 4. Check whether the `$IncludeConfig` options under `/etc/rsyslog.conf` already have a matching wildcard that will include the newly created `newrelic.conf` file under the `/etc/rsyslog.d` directory. Otherwise you'll need to explicitly include `/etc/rsyslog.d/newrelic.conf` in `/etc/rsyslog.conf` using `$IncludeConfig /etc/rsyslog.d/newrelic.conf`
 
-5. Add the following to `newrelic.conf`. Replace the highlighted values. For YOUR_LICENSE_KEY, use your New Relic <InlinePopover type="licenseKey" />:
+5. Add the following to `newrelic.conf`. Replace the highlighted values. For `YOUR_LICENSE_KEY`, use your New Relic <InlinePopover type="licenseKey" />:
 
    ```properties
    ## Specify each of the files to be tailed in case step 1 is done
@@ -120,7 +120,7 @@ To configure `rsyslog` versions 8 and above for Amazon Linux, Redhat, and Centos
    Note the configured port number is `6516` instead of `6514`.
 </Callout>
 
-2. Add the following to `newrelic.conf`. Replace all highlighted values. For YOUR_LICENSE_KEY, use your New Relic <InlinePopover type="licenseKey" />:
+2. Add the following to `newrelic.conf`. Replace all highlighted values. For `YOUR_LICENSE_KEY`, use your New Relic <InlinePopover type="licenseKey" />:
 
    ```properties
    ## Specify each of the files to be tailed in case step 1 is done
@@ -155,8 +155,7 @@ To configure `rsyslog` versions 8 and above for Amazon Linux, Redhat, and Centos
    ```
 3. Restart the `rsyslog` service by running:
 
-   ```
-   bash
+   ```bash
    sudo systemctl restart rsyslog
    ```
 4. [Check your New Relic account](/docs/logs/log-management/ui-data/explore-your-data-log-analytics) for logs.
@@ -167,8 +166,7 @@ If you're using rsyslog version 7 or below, the configuration files need to be a
 
 1. Install packages required to allow `rsyslog` to send logs using TLS encryption:
 
-   ```
-   bash
+   ```bash
    sudo yum install rsyslog-gnutls ca-certificates
    ```
 2. Optional: Configure `rsyslog` to tail log files and forward their contents to New Relic. Add the following to the `/etc/rsyslog.conf` file in order to enable its text file input module:
@@ -181,7 +179,7 @@ If you're using rsyslog version 7 or below, the configuration files need to be a
    ```
 3. In the `/etc/rsyslog.d/` directory, create a text file named `newrelic.conf`.
 4. Check whether the `$IncludeConfig` options under `/etc/rsyslog.conf` already have a matching wildcard that will include the newly created `newrelic.conf` file under the `/etc/rsyslog.d` directory. Otherwise you'll need to explicitly include `/etc/rsyslog.d/newrelic.conf` in `/etc/rsyslog.conf` using `$IncludeConfig /etc/rsyslog.d/newrelic.conf`.
-5. Add the following to `newrelic.conf`. Replace the highlighted values. For YOUR_LICENSE_KEY, use your New Relic <InlinePopover type="licenseKey" />:
+5. Add the following to `newrelic.conf`. Replace the highlighted values. For `YOUR_LICENSE_KEY`, use your New Relic <InlinePopover type="licenseKey" />:
 
    ```properties
    ## Template expected by the New Relic Syslog endpoint
@@ -218,8 +216,7 @@ To forward logs to New Relic with `syslog-ng`:
 
 1. Install `ca-certificates` required to allow `syslog-ng` to send logs using TLS encryption:
 
-   ```
-   bash
+   ```bash
    sudo yum install ca-certificates
    ```
 2. Open the `syslog-ng` configuration file (`/etc/syslog-ng/syslog-ng.conf`) in a text editor.
@@ -237,7 +234,7 @@ To forward logs to New Relic with `syslog-ng`:
            file("PATH_TO_FILE");
    };
    ```
-5. Define the New Relic `syslog` format. For YOUR_LICENSE_KEY, use your New Relic <InlinePopover type="licenseKey" />.
+5. Define the New Relic `syslog` format. For `YOUR_LICENSE_KEY`, use your New Relic <InlinePopover type="licenseKey" />.
 
    ```properties
    template NRFormat { template("YOUR_LICENSE_KEY <${PRI}>1 ${ISODATE} ${HOST:--} ${PROGRAM:--} ${PID:--} ${MSGID:--} ${SDATA:--} $MSG\n");
@@ -273,4 +270,4 @@ To forward logs to New Relic with `syslog-ng`:
 
 <Callout variant="tip">
   If you're running syslog-ng from a Docker container and experience issues, check [balait/syslog image documentation](https://hub.docker.com/r/balabit/syslog-ng/).
-</Callout>
+</Callout>

src/content/docs/logs/troubleshooting/log-message-truncated.mdx

@@ -66,14 +66,15 @@ If you have values exceeding the character limit, here are some options to try:
 
         To query for logs that have likely exceeded this storage limit in New Relic, run the following query:
 
-        ```
+        ```sql
         SELECT * FROM Log WHERE length(message) >= 4094
         ```
 
         To expand the blob data, run the following query, using `message` or any other attribute. Be sure to enclose the blob's attribute with backticks. For example:
 
-        ```
-        SELECT message, another-attribute, blob(`newrelic.ext.message`), blob(`newrelic.ext.another-attribute`) FROM Log
+        ```sql
+        SELECT message, another-attribute, blob(`newrelic.ext.message`), blob(`newrelic.ext.another-attribute`)
+        FROM Log
         ```
 
         For more information, see our documentation about [long messages stored as blobs](https://docs.newrelic.com/docs/logs/log-management/ui-data/long-logs-blobs/).

src/content/docs/logs/troubleshooting/no-log-data-appears-ui.mdx

@@ -137,7 +137,7 @@ For the infrastructure agent: see [logging config options](/docs/infrastructure/
       <td>
         Try querying the `Log` data type:
 
-        ```
+        ```sql
         SELECT * FROM Log
         ```
 

src/content/docs/vulnerability-management/integrations/aws.mdx

@@ -54,15 +54,19 @@ Once you've created an API destination for ingest, create an Eventbridge rule to
 2. Option: choose any Security Hub sample event from the dropdown to test your rule against. 
 3. For the event pattern, enter the select the custom patterns pane and input a pattern. For example the pattern below matches events from Security Hub, Guard Duty, and Inspector:
 
-```
+```json
 {
-  "detail-type": [{
-    "prefix": "Security Hub"
-  }, {
-    "prefix": "GuardDuty Finding"
-  }, {
-    "prefix": "Inspector2"
-  }]
+  "detail-type": [
+    {
+      "prefix": "Security Hub"
+    },
+    {
+      "prefix": "GuardDuty Finding"
+    },
+    {
+      "prefix": "Inspector2"
+    }
+  ]
 }
 ```
 
@@ -79,7 +83,7 @@ Configure your tags as needed.
 
 ### E.  Review and Create
 
-Review all your selections and make any changes as necessary. 
+Review all your selections and make any changes as necessary.
 
 ### F.  Review in NRDB
 
@@ -89,4 +93,4 @@ To review logs ingested via AWS Event Bridge, you can use the following NRQL que
 FROM Vulnerability SELECT * WHERE source LIKE 'AWS%' SINCE 3 MONTHS AGO
 ```
 
-Note that GuardDuty and Inspector results will only show this way, while SecurityHub vulnerabilities will be visible in New Relic's Vulnerability Management (if available)
+Note that GuardDuty and Inspector results will only show this way, while SecurityHub vulnerabilities will be visible in New Relic's Vulnerability Management (if available).

src/content/docs/vulnerability-management/integrations/trivy.mdx

@@ -16,12 +16,12 @@ To ingest your Trivy scan result files in SARIF into New Relic, utilize the secu
 
 Here's an example curl POST:
 
-```
+```bash
 curl --location --request POST 'https://security-api.newrelic.com/security/v1?repository=<https://github.com/MY_GITHUB_USER/MY_TRIVY_REPO>' \
---header 'Api-Key: <NewRelicLicenseKey>' \
---header 'Content-Type: application/json' \
---header 'X-Scanner: Trivy' \
--d @nameOfSarifFile.json
+  --header 'Api-Key: YOUR_LICENSE_KEY' \
+  --header 'Content-Type: application/json' \
+  --header 'X-Scanner: Trivy' \
+  -d @nameOfSarifFile.json
  ```
 
  <Callout variant='tip'>
@@ -31,17 +31,17 @@ curl --location --request POST 'https://security-api.newrelic.com/security/v1?re
 ## Confirm scan import activity
 The HTTP response from the POST will include a request uuid and information about the request. For example:
 
-```
+```json
 {
-  "success":false,
-  "errorMessage":null,
-  "uuid":"4740e3c8-dbc4-46e6-a4b2-a7fb6f918d20"
+  "success": false,
+  "errorMessage": null,
+  "uuid": "4740e3c8-dbc4-46e6-a4b2-a7fb6f918d20"
 }
 ```
 
 The request guid is included in all vulnerability events which can be [queried with NRQL](/docs/query-your-data/nrql-new-relic-query-language/get-started/introduction-nrql-new-relics-query-language/). These events are written in real time as the import job runs. To view the status and output of an import as it runs, use this NRQL query (replacing `YOUR_REQUEST_ID` with the uuid returned from your HTTP POST):
 
-```
+```sql
 FROM Log SELECT * WHERE source = 'Trivy' AND requestId = 'YOUR_REQUEST_ID'
 ```
 To see scan results visit [Vulnerability Management](https://docs.newrelic.com/docs/vulnerability-management/overview/).