Merge pull request #15898 from newrelic/nb-logs-sweep

feat(Sonic): Added logs monitoring key popover

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing.mdx

@@ -201,7 +201,7 @@ Here's a table with comparisons of the two options. Prices and limits are monthl
         [Automatically](/docs/logs/get-started/new-relics-log-management-security-privacy/#log-obfuscation) mask known credit card and Social Security number patterns in logs.
       </td>
       <td>
-        Create and track rules directly in the log management UI, and [mask or hash](/docs/logs/ui-data/obfuscation-ui/) sensitive log data.
+        Create and track rules directly in the <InlinePopover type="logs" /> UI, and [mask or hash](/docs/logs/ui-data/obfuscation-ui/) sensitive log data.
       </td>
       <td>
 

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx

@@ -742,7 +742,7 @@ Details about access to the options available on [our Instant Observability page
     id="logs-capabilities"
     title="Log management access"
   >
-Details on log management feature access by user type:
+Details on <InlinePopover type="logs" /> feature access by user type:
 
 <table>
   <thead>

src/content/docs/data-apis/understand-data/new-relic-data-types.mdx

@@ -746,7 +746,7 @@ A log is a message about a system used to understand the activity of the system
 
 ### Logs at New Relic [#logs-new-relic]
 
-Our [log management](/docs/logs/get-started/get-started-log-management) capabilities give you a centralized platform that connects your log data with other New Relic-monitored data. For example, you can [see logs alongside your APM data](/docs/logs/logs-context/logs-in-context).
+Our [<InlinePopover type="logs" />](/docs/logs/get-started/get-started-log-management) capabilities give you a centralized platform that connects your log data with other New Relic-monitored data. For example, you can [see logs alongside your APM data](/docs/logs/logs-context/logs-in-context).
 
 In New Relic, log data is reported with multiple [attributes](/docs/using-new-relic/welcome-new-relic/get-started/glossary#attribute) (key-value data) attached. To query your log data, you could use a NRQL query like:
 

src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx

@@ -334,7 +334,7 @@ For each pod, depending on the [integrations and features you've enabled](/docs/
 * Active alerts (both warning and critical)
 * [Kubernetes events that happened in that pod](/docs/integrations/kubernetes-integration/kubernetes-events/install-kubernetes-events-integration)
 * APM data and traces (if you've [linked your APM data](/docs/integrations/kubernetes-integration/link-your-applications/link-your-applications-kubernetes))
-* A link to the pods' and containers' logs, collected using the [Kubernetes plugin for log management in New Relic](/docs/logs/enable-logs/enable-logs/kubernetes-plugin-logs)
+* A link to the pods' and containers' logs, collected using the [Kubernetes plugin for <InlinePopover type="logs" /> in New Relic](/docs/logs/enable-logs/enable-logs/kubernetes-plugin-logs)
 
 Cluster and [control plane](/docs/integrations/kubernetes-integration/installation/configure-control-plane-monitoring) statistics are always visible on the left side.
 

src/content/docs/licenses/license-information/referenced-policies/security-guide.mdx

@@ -35,7 +35,7 @@ New Relic provides its customers controls of their data as follows:
 * New Relic's customers can use any number of methods to send data to New Relic's APIs, such as (1) using New Relic's software, (2) using vendor-neutral software that is managed and maintained by a third-party (e.g., [OpenTelemetry instrumentation](https://docs.newrelic.com/docs/integrations/open-source-telemetry-integrations/opentelemetry/introduction-opentelemetry-new-relic/#benefits) provided by [opentelemetry.io](opentelemetry.io), or (3) from third-party systems that customers manage and/or control.
 * New Relic's customers can use New Relic's Services such as NerdGraph to filter out and drop data. See [Drop data using nerdgraph](https://docs.newrelic.com/docs/telemetry-data-platform/manage-data/drop-data-using-nerdgraph/).
 * New Relic's customers can adjust their data retention periods as appropriate for their needs. See [Adjust retention](https://docs.newrelic.com/docs/telemetry-data-platform/manage-data/manage-data-retention/#adjust-retention).
-* New Relic's log management capabilities obfuscate numbers that match known patterns, such as bank card and social security numbers as described in our [log management security documentation](https://docs.newrelic.com/docs/logs/log-management/get-started/new-relics-log-management-security-privacy/). Customers that meet certain requirements can obfuscate their data as described [here](https://docs.newrelic.com/docs/logs/ui-data/obfuscation-ui/).
+* New Relic's <InlinePopover type="logs" /> capabilities obfuscate numbers that match known patterns, such as bank card and social security numbers as described in our [log management security documentation](https://docs.newrelic.com/docs/logs/log-management/get-started/new-relics-log-management-security-privacy/). Customers that meet certain requirements can obfuscate their data as described [here](https://docs.newrelic.com/docs/logs/ui-data/obfuscation-ui/).
 * New Relic honors requests to delete personal data in accordance with applicable privacy laws. Please see [https://docs.newrelic.com/docs/security/security-privacy/data-privacy/data-privacy-new-relic/](https://docs.newrelic.com/docs/security/security-privacy/data-privacy/data-privacy-new-relic/).
 * Customers may use New Relic's APIs to query data, such as NerdGraph described [here](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-nrql-tutorial/), and New Relic Services to export the data to other cloud providers. Customers that meet certain requirements can export their data as described [here](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-streaming-export/) and [here](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-historical-data-export/).
 * Customers can configure their log forwarder; see [this](https://docs.newrelic.com/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent/) before sending infrastructure logs to New Relic.

src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-licenses.mdx

@@ -9,7 +9,7 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-We love open-source software, and use the following with our [log management capabilities in New Relic](/docs/logs/get-started/get-started-log-management/). Thank you, open-source community, for making these fine tools! Some of these are listed under multiple software licenses, and in that case we have listed the license we've chosen to use.
+We love open-source software, and use the following with our [<InlinePopover type="logs" /> capabilities in New Relic](/docs/logs/get-started/get-started-log-management/). Thank you, open-source community, for making these fine tools! Some of these are listed under multiple software licenses, and in that case we have listed the license we've chosen to use.
 
 For a list of the licenses used for the log forwarders used with New Relic, see [Logs plugin licenses](/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses/).
 

src/content/docs/licenses/product-or-service-licenses/new-relic-logs/logs-plugin-licenses.mdx

@@ -9,7 +9,7 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-We love open-source software, and use the following in the log forwarder plugins that can be used with our [log management capabilities in New Relic](/docs/logs/get-started/get-started-log-management/). Thank you, open-source community, for making these fine tools! Some of these are listed under multiple software licenses, and in that case we have listed the license we've chosen to use.
+We love open-source software, and use the following in the log forwarder plugins that can be used with our [<InlinePopover type="logs" /> capabilities in New Relic](/docs/logs/get-started/get-started-log-management/). Thank you, open-source community, for making these fine tools! Some of these are listed under multiple software licenses, and in that case we have listed the license we've chosen to use.
 
 For a list of the licenses used for log management in New Relic, see [Logs licenses](/docs/licenses/product-or-service-licenses/new-relic-logs/logs-licenses/).
 

src/content/docs/logs/forward-logs/aws-firelens-plugin-log-forwarding.mdx

@@ -17,7 +17,7 @@ freshnessValidatedDate: never
 
 If your log data is already being monitored by [AWS FireLens](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_firelens.html), you can use our FireLens integration to forward and enrich your log data in New Relic. This integration is built on our Fluent Bit output plugin.
 
-Forwarding your FireLens logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding your FireLens logs to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Basic process [#compatibility-requirements]
 

src/content/docs/logs/forward-logs/aws-lambda-sending-cloudwatch-logs.mdx

@@ -18,7 +18,7 @@ freshnessValidatedDate: never
 
 You can send your [Amazon CloudWatch logs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html) to New Relic using our AWS Lambda function, `newrelic-log-ingestion`. This can be easily deployed from the AWS Serverless application repository.
 
-Forwarding your CloudWatch logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding your CloudWatch logs to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Install and configure the CloudWatch logs Lambda function [#install-function]
 

src/content/docs/logs/forward-logs/aws-lambda-sending-logs-s3.mdx

@@ -18,7 +18,7 @@ import serverlessAWSLambdaSelectRegion from 'images/serverless_screenshot-crop_A
 
 You can send your [Amazon S3 buckets](https://aws.amazon.com/s3/) to New Relic using our AWS Lambda function, `NewRelic-log-ingestion-s3`. This can be easily deployed from the AWS Serverless application repository.
 
-Forwarding logs from your S3 bucket to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding logs from your S3 bucket to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Install the Lambda function [#install-function]
 

src/content/docs/logs/forward-logs/aws-lambda-sending-security-logs-s3.mdx

@@ -14,7 +14,7 @@ import serverlessAWSLambdaSelectRegion from 'images/serverless_screenshot-crop_A
 You can send your [Amazon Security Lake logs](https://docs.aws.amazon.com/security-lake/latest/userguide/internal-sources.html) to New Relic using Serverless app 
 `newrelic-securitylake-s3-processor-LogForwarder`, which can be easily deployed from [AWS Serverless application repository](https://serverlessrepo.aws.amazon.com/applications).
 
-Forwarding logs from your Security Lake to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding logs from your Security Lake to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Install the Serverless application [#install-app]
 

src/content/docs/logs/forward-logs/azure-log-forwarding.mdx

@@ -31,7 +31,7 @@ import enforceHttpsFunctionApp from 'images/enforce-https-function-app.webp'
 
 If your logs are already being collected in Azure, you can use our [Microsoft Azure Resource Manager (ARM)](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview) templates to forward and enrich them in New Relic.
 
-Forwarding your Azure logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding your Azure logs to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 We currently offer two ARM templates to achieve this: the EventHub-based (recommended) and the Blob Storage-based templates.
 

src/content/docs/logs/forward-logs/enable-log-management-new-relic.mdx

@@ -28,7 +28,7 @@ import logsNRLogsinContext from 'images/logs_diagram_NR-logs-in-context.webp'
 
 import logsLogForwardOptions from 'images/logs_diagram_log-forward-options.webp'
 
-Our log management capabilities help you to collect, process, explore, query, and alert on your log data. To get your logs into New Relic, you can use any of these options:
+Our <InlinePopover type="logs" /> capabilities help you to collect, process, explore, query, and alert on your log data. To get your logs into New Relic, you can use any of these options:
 
 <img
   title="Log forwarding options into New Relic"

src/content/docs/logs/forward-logs/fluent-bit-plugin-log-forwarding.mdx

@@ -18,7 +18,7 @@ freshnessValidatedDate: never
 
 If your log data is already being monitored by [Fluent Bit](https://fluentbit.io/), you can use our Fluent Bit output plugin to forward and enrich your log data in New Relic.
 
-Forwarding your Fluent Bit logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding your Fluent Bit logs to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Basic process [#compatibility-requirements]
 

src/content/docs/logs/forward-logs/fluentd-plugin-log-forwarding.mdx

@@ -18,7 +18,7 @@ freshnessValidatedDate: never
 
 If your log data is already being monitored by [Fluentd](https://www.fluentd.org), you can use our Fluentd integration to forward and enrich your log data in New Relic.
 
-Forwarding your Fluentd logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding your Fluentd logs to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Basic process [#enable-process]
 

src/content/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent.mdx

@@ -464,7 +464,7 @@ Although these configuration parameters aren't required, we still recommend you
       The `attributes` configuration parameter does not add custom attributes to logs forwarded via external Fluent Bit configuration (for example, using the `fluentbit` configuration parameter). In this scenario, you should refer to the `record_modifier` option in the [Fluent Bit documentation](https://docs.fluentbit.io/manual/).
     </Callout>
 
-    One common use of the `attributes` configuration parameter is to specify the `logtype` attribute. This attribute allows leveraging one of the [built-in parsing rules](/docs/logs/log-management/ui-data/parsing/#built-in-rules) supported by New Relic's log management capabilities.
+    One common use of the `attributes` configuration parameter is to specify the `logtype` attribute. This attribute allows leveraging one of the [built-in parsing rules](/docs/logs/log-management/ui-data/parsing/#built-in-rules) supported by New Relic's <InlinePopover type="logs" /> capabilities.
 
     **Example:**
 

src/content/docs/logs/forward-logs/heroku-log-forwarding.mdx

@@ -13,7 +13,7 @@ freshnessValidatedDate: never
 
 If your log data is already being monitored by Heroku's built-in [Logplex](https://devcenter.heroku.com/articles/logplex) router, you can use our integration to forward and enrich your log data in New Relic.
 
-Forwarding your Heroku logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding your Heroku logs to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 We currently support [Heroku HTTPS drains](https://devcenter.heroku.com/articles/log-drains#https-drains) and [Heroku Syslog drains](https://devcenter.heroku.com/articles/log-drains#syslog-drains).
 

src/content/docs/logs/forward-logs/kubernetes-plugin-log-forwarding.mdx

@@ -16,7 +16,7 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-New Relic's Kubernetes plugin for log forwarding simplifies sending logs from your cluster to New Relic logs. It uses a standalone Docker image and runs as a DaemonSet, seamlessly collecting logs for centralized analysis and troubleshooting. Forwarding your Kubernetes logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+New Relic's Kubernetes plugin for log forwarding simplifies sending logs from your cluster to New Relic logs. It uses a standalone Docker image and runs as a DaemonSet, seamlessly collecting logs for centralized analysis and troubleshooting. Forwarding your Kubernetes logs to New Relic will give you enhanced l<InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Enable Kubernetes for log management [#enable-process]
 

src/content/docs/logs/forward-logs/logstash-plugin-log-forwarding.mdx

@@ -17,7 +17,7 @@ freshnessValidatedDate: never
 
 If your log data is already being monitored by [Logstash](https://www.elastic.co/products/logstash), you can use our Logstash plugin to forward and enrich your log data in New Relic.
 
-Forwarding your Logstash logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding your Logstash logs to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Enable Logstash for log management [#enable-process]
 

src/content/docs/logs/forward-logs/mux-video-streaming-firehose.mdx

@@ -27,11 +27,11 @@ If everything is configured correctly and your data is being collected, you shou
 * Our [logs UI](https://one.newrelic.com/launcher/logger.log-launcher)
 * Our [NRQL query tools](/docs/chart-builder/use-chart-builder/choose-data/use-advanced-nrql-mode-specify-data). For example, you can execute a query like this:
 
-    ```
+    ```sql
     SELECT * FROM Log
     ```
 
-If no data appears after you enable our log management capabilities, follow our [standard log troubleshooting procedures](/docs/logs/log-management/troubleshooting/no-log-data-appears-ui/).
+If no data appears after you enable our <InlinePopover type="logs" /> capabilities, follow our [standard log troubleshooting procedures](/docs/logs/log-management/troubleshooting/no-log-data-appears-ui/).
 
 ## What's next? [#what-next]
 

src/content/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose.mdx

@@ -21,7 +21,7 @@ import logsAWSKinesisFirehoseBufferHints from 'images/logs_screenshot-crop_AWS-K
 
 If your log data is already being monitored by [Amazon CloudWatch Logs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html), you can use our Kinesis Data Firehose integration to forward and enrich your log data in New Relic. Kinesis Data Firehose is a service that can stream data in real time to a variety of destinations, including our platform.
 
-Forwarding your CloudWatch Logs or other logs compatible with a Kinesis stream to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding your CloudWatch Logs or other logs compatible with a Kinesis stream to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Create the delivery stream for New Relic [#create-delivery-stream]
 

src/content/docs/logs/forward-logs/vector-output-sink-log-forwarding.mdx

@@ -14,7 +14,7 @@ freshnessValidatedDate: never
 
 If your log data is already being monitored by [Vector](https://vector.dev/), you can use our [Vector output sink](https://vector.dev/docs/reference/configuration/sinks/new_relic/) to forward and enrich your log data in New Relic.
 
-Forwarding your Vector logs to New Relic will give you enhanced log management capabilities to collect, process, explore, query, and alert on your log data.
+Forwarding your Vector logs to New Relic will give you enhanced <InlinePopover type="logs" /> capabilities to collect, process, explore, query, and alert on your log data.
 
 ## Configure the Vector logs sink for New Relic [#configure-sink]
 

src/content/docs/logs/get-started/get-started-log-management.mdx

@@ -29,7 +29,7 @@ import logsMainLogsUi from 'images/logs_screenshot-full_main-logs-ui.webp'
 
 As applications move towards the cloud, microservices architecture is becoming more dispersed, making the ability to monitor logs essential. New Relic offers a fast, scalable log management platform so you can connect your logs with the rest of your telemetry and infrastructure data in a single place.  
 
-Our log management solution provides deeper visibility into application and infrastructure performance data (events, errors, traces, and more) to reduce mean time to resolution (MTTR) and quickly troubleshoot production incidents.
+Our <InlinePopover type="logs" /> solution provides deeper visibility into application and infrastructure performance data (events, errors, traces, and more) to reduce mean time to resolution (MTTR) and quickly troubleshoot production incidents.
 
 ## Find problems faster, reduce context switching [#logs-definition]