Merge pull request #22344 from brnhensley/patch-47

fix: indentation

Author: WriteMayur

src/content/docs/distributed-tracing/infinite-tracing-on-premise/bring-your-own-cache.mdx

@@ -19,21 +19,21 @@ The processor supports any Redis-compatible cache implementation. It has been te
 For production deployments, we recommend using cluster mode (sharded) to ensure high availability and scalability. To enable distributed caching, add the `distributed_cache` configuration to your `tail_sampling` processor section:
 
   ```yaml
-    tail_sampling:
-      distributed_cache:
-        connection:
-          address: redis://localhost:6379/0
-          password: 'local'
-        trace_window_expiration: 30s      # Default: how long to wait after last span before evaluating
-        in_flight_timeout: 120s           # Optional: defaults to trace_window_expiration if not set
-        traces_ttl: 3600s                 # Optional: default 1 hour
-        cache_ttl: 7200s                  # Optional: default 2 hours
-        suffix: "itc"                     # Redis key prefix
-        max_traces_per_batch: 500         # Default: traces processed per evaluation cycle
-        evaluation_interval: 1s           # Default: evaluation frequency
-        evaluation_workers: 4             # Default: number of parallel workers (defaults to CPU count)
-        data_compression:
-          format: lz4                     # Optional: compression format (none, snappy, zstd, lz4); lz4 recommended
+  tail_sampling:
+    distributed_cache:
+      connection:
+        address: redis://localhost:6379/0
+        password: 'local'
+      trace_window_expiration: 30s      # Default: how long to wait after last span before evaluating
+      in_flight_timeout: 120s           # Optional: defaults to trace_window_expiration if not set
+      traces_ttl: 3600s                 # Optional: default 1 hour
+      cache_ttl: 7200s                  # Optional: default 2 hours
+      suffix: "itc"                     # Redis key prefix
+      max_traces_per_batch: 500         # Default: traces processed per evaluation cycle
+      evaluation_interval: 1s           # Default: evaluation frequency
+      evaluation_workers: 4             # Default: number of parallel workers (defaults to CPU count)
+      data_compression:
+        format: lz4                     # Optional: compression format (none, snappy, zstd, lz4); lz4 recommended
   ```
 
   <Callout variant="important">
@@ -43,16 +43,16 @@ For production deployments, we recommend using cluster mode (sharded) to ensure
 The `address` parameter must specify a valid Redis-compatible server address using the standard format:
 
   ```shell
-  redis[s]://[[username][:password]@][host][:port][/db-number]
+  [output] redis[s]://[[username][:password]@][host][:port][/db-number]
   ```
 
 Alternatively, you can embed credentials directly in the `address` parameter:
 
   ```yaml
-    tail_sampling:
-      distributed_cache:
-        connection:
-          address: redis://:yourpassword@localhost:6379/0
+  tail_sampling:
+    distributed_cache:
+      connection:
+        address: redis://:yourpassword@localhost:6379/0
   ```
 
 The processor is implemented in Go and uses the [go-redis](https://github.com/redis/go-redis/tree/v9) client library.
@@ -114,8 +114,8 @@ Proper Redis instance sizing is critical for optimal performance. Use the config
 
 ### Memory estimation formula
 
-  ```shell
-    Total Memory = (Trace Data) + (Decision Caches) + (Overhead)
+  ```
+  Total Memory = (Trace Data) + (Decision Caches) + (Overhead)
   ```
 
 #### 1. Trace data storage
@@ -133,13 +133,13 @@ Trace data is stored in Redis for the full `traces_ttl` period to support late-a
 
 **Example calculation**: At 10,000 spans/second with 1-hour `traces_ttl`:
 
-  ```shell
+  ```
   10,000 spans/sec × 3600 sec × 900 bytes = 32.4 GB
   ```
 
 **With lz4 compression** (we have observed 25% reduction):
 
-  ```shell
+  ```
   32.4 GB × 0.75 = 24.3 GB
   ```
 
@@ -164,7 +164,7 @@ When using `distributed_cache`, the decision caches are stored in Redis without
 
 **Example calculation**: 500 traces per batch (default) with 20 spans per trace on average:
 
-  ```shell
+  ```
   500 × 20 × 900 bytes = 9 MB per batch
   ```
 
@@ -247,4 +247,4 @@ The processor uses a cascading TTL structure, with each level providing protecti
 4. **`cache_ttl`** (default: 2 hours)
    - Redis key expiration for decision cache entries (sampled/non-sampled)
    - Prevents duplicate evaluation for late-arriving spans
-   - Defined via `distributed_cache.cache_ttl`
+   - Defined via `distributed_cache.cache_ttl`

src/content/docs/infrastructure-as-code/terraform/migrate-drop-rules-to-pipeline-cloud-rules.mdx

@@ -54,14 +54,14 @@ This section describes the standard Terraform workflow for migrating from `newre
     Navigate to your Terraform working directory and run one of the following commands:
 
     ```bash
-      # Apply to update state with pipeline_cloud_rule_entity_id
-      terraform apply
+    # Apply to update state with pipeline_cloud_rule_entity_id
+    terraform apply
 
-      # Safer: use refresh-only to see changes without modifying infrastructure
-      terraform apply -refresh-only
+    # Safer: use refresh-only to see changes without modifying infrastructure
+    terraform apply -refresh-only
 
-      # Targeted: limit operation to specific drop rule resources
-      terraform apply -refresh-only -target=newrelic_nrql_drop_rule.foo
+    # Targeted: limit operation to specific drop rule resources
+    terraform apply -refresh-only -target=newrelic_nrql_drop_rule.foo
     ```
 
     After running one of the above commands, the `pipeline_cloud_rule_entity_id` will be available in your state for each drop rule. Keep the IDs handy for the next step.
@@ -620,7 +620,8 @@ To simplify the native Terraform migration workflow described above, New Relic p
              action      = "drop"
              nrql        = "SELECT * FROM Log WHERE contains(message, 'SSN')"
            }
-            ``` */}
+          ```
+          */}
           </Step>
 
           <Step>

src/content/docs/infrastructure/host-integrations/db-entity-tags.mdx

@@ -19,7 +19,6 @@ Changes to these configuration files are automatically picked up and do not requ
 Example snippet for a database integration config file (for example, `mysql-config.yml`):
 
 ```yaml
-
 # /etc/newrelic-infra/integrations.d/mysql-config.yml
 integrations:
   - name: nri-mysql
@@ -42,8 +41,7 @@ Changes to `newrelic-infra.yml` require a restart of the infrastructure agent to
 
 Example `newrelic-infra.yml` snippet:
 
-``` yaml
-
+```yaml
 # /etc/newrelic-infra.yml
 # ... other configuration ...
 custom_attributes:

src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/java-extensions-k8s-auto-attach.mdx

@@ -86,7 +86,7 @@ Replace `your-registry/{Your-Image-Name}` with your actual container registry pa
 Push the image to your container registry:
 
 ```bash
-  docker push your-registry/{Your-Image-Name}
+docker push your-registry/{Your-Image-Name}
 ```
 
 </Step>
@@ -114,7 +114,6 @@ spec:
   agent:
     language: java
     image: your-registry/{Your-Image-Name}
-
 ```
 
 </Step>
@@ -126,7 +125,7 @@ spec:
 Apply the updated instrumentation to your cluster:
 
 ```bash
-  kubectl apply -f instrumentation-java.yaml
+kubectl apply -f instrumentation-java.yaml
 ```
 
 </Step>
@@ -140,17 +139,17 @@ Restart your Java applications to pick up the new init container with extensions
 
 * To restart a specific deployment:
 
-  ```bash
-    # Restart a specific deployment
-    kubectl rollout restart deployment/my-java-deployment
-  ```
+```bash
+# Restart a specific deployment
+kubectl rollout restart deployment/my-java-deployment
+```
 
 * To restart all deployments in a namespace:
 
-  ```bash
-    # Or restart all deployments in a namespace
-    kubectl rollout restart deployments -n my-namespace
-  ```
+```bash
+# Or restart all deployments in a namespace
+kubectl rollout restart deployments -n my-namespace
+```
 
 </Step>
 
@@ -165,7 +164,7 @@ If extensions aren't loading:
 1. Verify the extensions directory exists in your custom image:
 
     ```bash
-      docker run --rm your-registry/{Your-Image-Name} ls -la /extensions
+    docker run --rm your-registry/{Your-Image-Name} ls -la /extensions
     ```
 
 2. Check file permissions ensure extension JAR files are readable.
@@ -178,4 +177,4 @@ If extensions aren't loading:
 * [Java extension modules documentation](/docs/apm/agents/java-agent/instrumentation/extension-additional-instrumentation-modules/)
 * [Kubernetes APM auto-attach](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/)
 * [Java agent configuration](/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file/)
-* [Custom instrumentation for Java](/docs/apm/agents/java-agent/custom-instrumentation/java-custom-instrumentation/)
+* [Custom instrumentation for Java](/docs/apm/agents/java-agent/custom-instrumentation/java-custom-instrumentation/)

src/content/docs/query-your-data/explore-query-data/notebooks/notebooks-examples.mdx

@@ -35,8 +35,8 @@ Our main API experienced elevated error rates starting at 14:32 UTC...
 
 **Query block: Error rate timeline**
 ```sql
-SELECT count(*) as 'Total Requests',
-       filter(count(*), WHERE httpResponseCode >= 400) as 'Errors'
+SELECT count(*) AS 'Total Requests',
+       filter(count(*), WHERE httpResponseCode >= 400) AS 'Errors'
 FROM Transaction
 WHERE appName = 'api-production'
 TIMESERIES 1 minute
@@ -45,8 +45,8 @@ SINCE '2024-10-15 14:00:00' UNTIL '2024-10-15 16:00:00'
 
 **Query block: Error breakdown by endpoint**
 ```sql
-SELECT count(*) as 'Error Count',
-       average(duration) as 'Avg Duration (ms)'
+SELECT count(*) AS 'Error Count',
+       average(duration) AS 'Avg Duration (ms)'
 FROM Transaction
 WHERE appName = 'api-production'
   AND httpResponseCode >= 400
@@ -73,8 +73,8 @@ ORDER BY count(*) DESC
 
 **Query block: Database performance during incident**
 ```sql
-SELECT average(duration) as 'Query Duration (ms)',
-       count(*) as 'Query Count'
+SELECT average(duration) AS 'Query Duration (ms)',
+       count(*) AS 'Query Count'
 FROM DatabaseSample
 WHERE host = 'prod-db-01'
 TIMESERIES 5 minutes
@@ -104,9 +104,9 @@ Track and analyze application performance trends over time to identify optimizat
 
 **Query block: Response time trends**
 ```sql
-SELECT percentile(duration, 50) as 'P50',
-       percentile(duration, 95) as 'P95',
-       percentile(duration, 99) as 'P99'
+SELECT percentile(duration, 50) AS 'P50',
+       percentile(duration, 95) AS 'P95',
+       percentile(duration, 99) AS 'P99'
 FROM Transaction
 WHERE appName IN ('web-frontend', 'api-backend', 'auth-service')
 FACET appName
@@ -116,7 +116,7 @@ SINCE 7 days ago
 
 **Query block: Error rate comparison**
 ```sql
-SELECT percentage(count(*), WHERE error IS true) as 'Error Rate %'
+SELECT percentage(count(*), WHERE error IS true) AS 'Error Rate %'
 FROM Transaction
 WHERE appName IN ('web-frontend', 'api-backend', 'auth-service')
 FACET appName
@@ -167,7 +167,7 @@ New interactive dashboard builder with drag-and-drop widgets...
 
 **Query block: Daily active users creating dashboards**
 ```sql
-SELECT uniqueCount(userId) as 'Users Creating Dashboards'
+SELECT uniqueCount(userId) AS 'Users Creating Dashboards'
 FROM PageView
 WHERE pageUrl LIKE '%/dashboard/create%'
 TIMESERIES 1 day
@@ -177,9 +177,9 @@ SINCE 30 days ago
 **Query block: Dashboard creation funnel**
 ```sql
 SELECT funnel(userId,
-  WHERE pageUrl LIKE '%/dashboard/create%' as 'Started Creation',
-  WHERE pageUrl LIKE '%/dashboard/create%' AND eventType = 'widget_added' as 'Added Widget',
-  WHERE eventType = 'dashboard_saved' as 'Saved Dashboard'
+  WHERE pageUrl LIKE '%/dashboard/create%' AS 'Started Creation',
+  WHERE pageUrl LIKE '%/dashboard/create%' AND eventType = 'widget_added' AS 'Added Widget',
+  WHERE eventType = 'dashboard_saved' AS 'Saved Dashboard'
 )
 FROM PageView, UserAction
 SINCE 30 days ago
@@ -209,8 +209,8 @@ Create ongoing security analysis to track potential threats and system vulnerabi
 
 **Query block: Failed authentication patterns**
 ```sql
-SELECT count(*) as 'Failed Attempts',
-       latest(remoteAddr) as 'Source IP'
+SELECT count(*) AS 'Failed Attempts',
+       latest(remoteAddr) AS 'Source IP'
 FROM Log
 WHERE message LIKE '%authentication failed%'
 FACET remoteAddr
@@ -221,8 +221,8 @@ ORDER BY count(*) DESC
 
 **Query block: API access anomalies**
 ```sql
-SELECT count(*) as 'Request Count',
-       uniqueCount(userAgent) as 'Unique User Agents'
+SELECT count(*) AS 'Request Count',
+       uniqueCount(userAgent) AS 'Unique User Agents'
 FROM Transaction
 WHERE appName = 'api-gateway'
 FACET request.headers.x-forwarded-for
@@ -254,9 +254,9 @@ Track key business KPIs alongside technical metrics to understand the complete p
 
 **Query block: User engagement metrics**
 ```sql
-SELECT count(*) as 'Page Views',
-       uniqueCount(userId) as 'Active Users',
-       average(duration) as 'Avg Session Duration'
+SELECT count(*) AS 'Page Views',
+       uniqueCount(userId) AS 'Active Users',
+       average(duration) AS 'Avg Session Duration'
 FROM PageView
 TIMESERIES 1 day
 SINCE 30 days ago
@@ -265,10 +265,10 @@ SINCE 30 days ago
 **Query block: Conversion funnel**
 ```sql
 SELECT funnel(userId,
-  WHERE pageUrl = '/signup' as 'Signup Page',
-  WHERE pageUrl = '/signup/verify' as 'Email Verified',
-  WHERE pageUrl = '/onboarding/complete' as 'Onboarding Complete',
-  WHERE eventType = 'subscription_created' as 'Converted'
+  WHERE pageUrl = '/signup' AS 'Signup Page',
+  WHERE pageUrl = '/signup/verify' AS 'Email Verified',
+  WHERE pageUrl = '/onboarding/complete' AS 'Onboarding Complete',
+  WHERE eventType = 'subscription_created' AS 'Converted'
 )
 FROM PageView, UserAction
 SINCE 30 days ago
@@ -344,4 +344,4 @@ SINCE 1 hour ago
 
 * Learn how to [add queries to notebooks](/docs/query-your-data/explore-query-data/notebooks/add-queries-to-notebooks)
 * Discover [sharing options](/docs/query-your-data/explore-query-data/notebooks/share-notebooks) for your notebooks
-* Explore [NRQL examples](/docs/nrql/nrql-examples) for more query inspiration
+* Explore [NRQL examples](/docs/nrql/nrql-examples) for more query inspiration