Merge pull request #4231 from newrelic/log-mgmt-plinko

fix(Logs): Get started docs

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

@@ -15,7 +15,7 @@ redirects:
   - /docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/kubernetes-plugin-log-forwarding
 ---
 
-If your log data is already being monitored by [Fluent Bit](https://fluentbit.io/), you can use our Fluent Bit [output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) to forward and enrich your log data in New Relic.This plugin is also provided in a standalone Docker image that can be installed in a [Kubernetes](https://kubernetes.io/) cluster in the form of a [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/). We refer to this as our **Kubernetes plugin**.
+If your log data is already being monitored by [Fluent Bit](https://fluentbit.io/), you can use our [Fluent Bit output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) to forward and enrich your log data in New Relic. This plugin is also provided in a standalone Docker image that can be installed in a [Kubernetes](https://kubernetes.io/) cluster in the form of a [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/). We refer to this as our Kubernetes plugin.
 
 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.
 

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

@@ -38,26 +38,28 @@ Log management features include:
 
 ## Bring in your logging data [#integrate-logs]
 
-You can bring your log data into New Relic using a [compatible log forwarding plugin](/docs/enable-new-relic-logs#compatibility-requirements), or with [OpenTelemetry](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-logs).
+To bring your log data into New Relic, you can:
 
-* Forward your logs [using our Infrastructure agent](/docs/logs/enable-new-relic-logs/1-enable-logs/forward-your-logs-using-new-relic-infrastructure-agent) or our [Kubernetes plugin](/docs/logs/enable-logs/enable-logs/kubernetes-plugin-logs).
-* Use our plugins for well-known log forwarders, like [Fluentd](/docs/logs/enable-logs/enable-logs/fluentd-plugin-logs), [Fluent Bit](/docs/logs/enable-logs/enable-logs/fluent-bit-plugin-logs), and [Logstash](/docs/logs/enable-logs/enable-logs/logstash-plugin-logs).
-* Stream or ship your logs from Amazon using [AWS Lambda](/docs/logs/enable-new-relic-logs/1-enable-logs/aws-lambda-sending-logs-s3) or [Kinesis](/docs/logs/enable-new-relic-logs/1-enable-logs/stream-logs-new-relic-using-kinesis-data-firehose).
-* Send your logs data using the [Logs API](/docs/introduction-new-relic-logs-api).
+* Use our [infrastructure monitoring agent](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/) as a lightweight data collector, without having to install additional software.
+* Select from a wide range of [log forwarding plugins](/docs/logs/forward-logs/enable-log-management-new-relic/), including Amazon, Microsoft, Fluentd, Fluent Bit, Kubernetes, Logstash, and more.
+* Use our [OpenTelemetry](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-concepts/#logs) solutions.
+* Send your log data by using the [Log API](/docs/logs/log-management/log-api/) or [TCP endpoint](/docs/logs/log-management/log-api/use-tcp-endpoint-forward-logs-new-relic/).
 
-Once log management is enabled, you can also connect your logs with your APM agent, Kubernetes clusters, or distributed tracing to get additional contextual logging data with our [logs in context extensions](/docs/enable-logs-context-logs).
+Once log management is enabled, you can also connect your logs with your APM agent, Kubernetes clusters, or distributed tracing to get additional contextual logging data with our [logs in context extensions](/docs/logs/logs-context/configure-logs-context-apm-agents/).
 
 ## View your logging data in New Relic [#find-data]
 
 You can explore your logging data in the UI or by API:
 
 * Logs UI at [one.newrelic.com](https://one.newrelic.com)
-* Logs UI for EU region data center [if applicable](/docs/using-new-relic/welcome-new-relic/get-started/our-eu-us-region-data-centers/): [one.eu.newrelic.com](https://one.eu.newrelic.com)
+* Logs UI for [EU region data center](/docs/using-new-relic/welcome-new-relic/get-started/our-eu-us-region-data-centers/) if applicable: [one.eu.newrelic.com](https://one.eu.newrelic.com)
 
 You can also query the `Log` data type. For example, use [NRQL](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql) to run:
 
 ```
 SELECT * FROM Log
 ```
 
-For more information about query options in New Relic, see [Query your data](/docs/using-new-relic/data/understand-data/query-new-relic-data).
+You can also use [NerdGraph](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph/), our GraphQL-format API, to request the exact data you need.
+
+For more information, see our documentation about [query options](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) in New Relic.

src/content/docs/logs/log-management/get-started/new-relics-log-management-security-privacy.mdx

@@ -4,7 +4,7 @@ tags:
   - Logs
   - Log management
   - Get started
-metaDescription: How to ensure that the data you send to New Relic Log monitoring is secure.
+metaDescription: What New Relic does to ensure that the log data you send is secure, and what you can do as additional data privacy measures.
 redirects:
   - /docs/new-relic-logs-security
   - /docs/logs/new-relic-logs/get-started/new-relic-logs-security
@@ -13,7 +13,7 @@ redirects:
   - /docs/logs/log-management/get-started/new-relic-log-management-security-privacy
 ---
 
-With [log management](/docs/introduction-new-relic-logs) you have direct control over what data is reported to New Relic. To ensure data privacy and to limit the types of information New Relic receives, no customer data is captured except what you supply in API calls or log forwarder configuration. All data for the logs service is then reported to New Relic over HTTPS.
+With our [log management](/docs/logs/log-management/get-started/get-started-log-management/) solution, you have direct control over what data is reported to New Relic. To ensure data privacy, and to limit the types of information New Relic receives, no customer data is captured except what you supply in API calls or log forwarder configuration. All data for the logs service is then reported to New Relic over HTTPS.
 
 This document describes additional security considerations for your logging data. For more information about New Relic's security measures:
 
@@ -33,8 +33,8 @@ Numbers that appear to be a credit card (thirteen to sixteen digits) are obfusca
 
 Nine-digit numbers with hyphens that appear to be Social Security numbers, such as `123-45-6789`, are obfuscated as `XXXXXXXXX`. Nine-digit numbers with spaces, such as `123 45 6789`, or hyphens in a different pattern, such as `12-345-67-89`, are not automatically obfuscated.
 
-If you need to opt out of automatic obfuscation, get support at [support.newrelic.com](https//:support.newrelic.com).
+If you need to opt out of automatic obfuscation, get support at [support.newrelic.com](https://support.newrelic.com).
 
 ## Customize your security settings [#customize-security]
 
-The data you send to New Relic, including any additional filtering, is controlled by the configuration of the [log forwarder you use](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/enable-log-management-new-relic), such as FluentD. Because you control what customer data is logged, be sure to follow your organization's security guidelines to mask, obfuscate, or prevent sending any sensitive data.
+The data you send to New Relic, including any additional filtering, is controlled by the configuration of the [log forwarder](/docs/logs/forward-logs/enable-log-management-new-relic/) you use. You control what customer data is logged, so be sure to follow your organization's security guidelines to mask, obfuscate, or prevent sending any sensitive data.

src/content/docs/logs/log-management/log-api/introduction-log-api.mdx

@@ -4,7 +4,7 @@ tags:
   - Logs
   - Log management
   - Log API
-metaDescription: Use New Relic's Log API so you can send your monitored log data directly to New Relic via HTTP input.
+metaDescription: Use our Log API so you can send your monitored log data directly to New Relic via HTTP input.
 redirects:
   - /docs/enable-new-relic-logs-http-input
   - /docs/introduction-new-relic-logs-api
@@ -17,26 +17,19 @@ redirects:
   - /docs/telemetry-data-platform/get-data/apis/introduction-log-api
 ---
 
-If our [logging solutions](/docs/logs/enable-logs/enable-logs/enable-new-relic-logs) don't meet your needs, you can use our Log API to send [log data](/docs/using-new-relic/data/understand-data/new-relic-data-types#log-data) directly to [New Relic's Log management](/docs/logs/new-relic-logs/get-started/introduction-new-relic-logs) via an HTTP endpoint.
+If our [log forwarding solutions](/docs/logs/forward-logs/enable-log-management-new-relic/) don't meet your needs, you can use our Log API to send log data directly to New Relic via an HTTP endpoint.
 
 Want to try out our Log API? [Create a New Relic account](https://newrelic.com/signup) for free! No credit card required.
 
-## Compatibility and requirements [#compatibility-requirements]
-
-Requirements include:
-
-* A [New Relic license key](/docs/apis/intro-apis/new-relic-api-keys/#ingest-license-key)
-* For payload details, see [limits and restricted characters](#limits).
-
 ## HTTP setup [#setup]
 
 To send log data to your New Relic account:
 
-1. Get your [New Relic license key](/docs/apis/intro-apis/new-relic-api-keys/#ingest-license-key). 
-2. Generate the JSON message using the required [headers](#json-headers) and [body](#json-body) fields.
-3. Ensure you're providing an Api-Key or License-Key via [headers](#json-headers) or [query parameters](#query-parameters)
-4. Submit the JSON message to the [HTTP endpoint](#endpoint) in a **POST** request.
-5. Generate some traffic and wait a few minutes, then [check your account](#find-data) for data.
+1. Get your [New Relic license key](/docs/apis/intro-apis/new-relic-api-keys/#ingest-license-key).
+2. Review the information about [limits and restricted characters](#limits) for payloads. 
+3. Generate the JSON message using the required [headers](#json-headers) and [body](#json-content) fields. Provide your `Api-Key` or `License-Key` via [headers](#json-headers) or [query parameters](#query-parameters).
+5. Submit the JSON message to the [HTTP endpoint](#endpoint) in a `POST` request.
+6. Generate some traffic and wait a few minutes, then [check your account](#what-next) for data.
 
 ## HTTP headers [#json-headers]
 
@@ -919,16 +912,13 @@ POST /log/v1 HTTP/1.1
    }
 ```
 
-## Find log data [#find-data]
-
-For where to find data sent via the Log API (including from integrations that use that API), see [Find log data](/docs/logs/new-relic-logs/get-started/introduction-new-relic-logs#find-data).
-
 ## What's next? [#what-next]
 
-Now that you've enabled Log management, here are some potential next steps:
+Make the most of your data in New Relic with our log management capabilities:
 
-* Explore your data using the [Logs UI](/docs/explore-your-data-new-relic-logs-ui).
-* [Configure your agent](/docs/logs/new-relic-logs/enable-logs-context/enable-logs-context-apm-agents) to see contextual log data, such as [distributed tracing](/docs/understand-dependencies/distributed-tracing/get-started/introduction-distributed-tracing), stack traces, application logs, and more.
-* [Query your data](/docs/logs/new-relic-logs/ui-data/query-syntax-logs) and [create custom dashboards](/docs/insights/use-insights-ui/manage-dashboards/create-edit-copy-insights-dashboards), [charts](/docs/insights/use-insights-ui/manage-dashboards/add-customize-nrql-charts), or [alerts](/docs/alerts/new-relic-alerts/configuring-alert-policies/create-edit-or-find-alert-policy).
+* Explore the logging data across your platform with our [Logs UI](/docs/logs/log-management/ui-data/use-logs-ui/).
+* Get deeper visibility into both your application and your platform performance data by forwarding your logs with our [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents/) capabilities.
+* Set up [alerts](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/).
+* [Query](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) your data and [create dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/). For example, to query your data with NerdGraph, our GraphQL-format API, see our [NerdGraph NRQL tutorial](/docs/apis/nerdgraph/examples/nerdgraph-nrql-tutorial/).
 
-If no data appears after you enable Log management, follow the [troubleshooting procedures](/docs/logs/new-relic-logs/troubleshooting/no-data-appears-logs).
+If no data appears after you enable log management, follow the [troubleshooting procedures](/docs/logs/log-management/troubleshooting/no-log-data-appears-ui/).