Merge pull request #13428 from newrelic/large-log-links

feat(tutorials): add links towards log tutorial

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

@@ -37,6 +37,10 @@ Our log management capabilities help you to collect, process, explore, query, an
 
 For an overview of our various logging solutions, see [Introduction to logs](/docs/logs/get-started/get-started-log-management#integrate-logs).
 
+<Callout variant="tip">
+Got lots of logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 Here are some details on how to accomplish specific use cases: 
 
 <table>

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

@@ -62,6 +62,9 @@ How you forward your logs depends on how you installed the infrastructure agent,
   See [Rollback to Fluent Bit 1.9](#rollback-after-fluent-bit-2) for more information about how to rollback.
 </Callout>
 
+<Callout variant="tip">
+Got lots of logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
 
 ## System requirements [#system]
 

src/content/docs/logs/get-started/logging-best-practices.mdx

@@ -13,6 +13,10 @@ import logsParsingExample from 'images/logs_screenshot-full_parsing-example.webp
 
 Welcome to the New Relic logging best practices guide. Here you'll find in-depth recommendations for how to optimize our logs features and manage data consumption. 
 
+<Callout variant="tip">
+Got lots of logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## Forwarding logs [#forwarding-logs]
 
 Here are some tips on log forwarding to supplement our [log forwarding docs](/docs/logs/forward-logs/enable-log-management-new-relic): 

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

@@ -22,6 +22,10 @@ This document describes additional security considerations for your logging data
 * Visit the [New Relic security website](https://newrelic.com/security).
 * Read this [blog post](https://blog.newrelic.com/product-news/security-use-cases-for-logs/) that explains how you can use our log management tools to gain visibility into some of the most severe threats to modern digital businesses.
 
+<Callout variant="tip">
+Got lots of logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## Log obfuscation [#log-obfuscation]
 
 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/logs-context/configure-logs-context-go.mdx

@@ -17,6 +17,10 @@ redirects:
 
 With our Go language <InlinePopover type="apm" /> agent, you can get **logs in context**, which lets you see your app logs in the context of your other New Relic data. For general information on this feature, see [APM logs in context](/docs/apm/new-relic-apm/getting-started/get-started-logs-context).
 
+<Callout variant="tip">
+Got lots of Go logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## Configuring logs in context in the agent  [#automatic]
 
 Modifications to the Go agent's config options are needed in order to use the following logs in context features.

src/content/docs/logs/logs-context/configure-logs-context-nodejs.mdx

@@ -22,6 +22,10 @@ redirects:
 
 With our Node.js APM agent, you can get <InlinePopover type="apm" /> logs in context, which lets you see your app logs in the context of your other New Relic data. For general information on this feature, see [APM logs in context](/docs/apm/new-relic-apm/getting-started/get-started-logs-context).
 
+<Callout variant="tip">
+Got lots of Node.js logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## Automatic logs in context options [#automatic]
 
 With application logging, your APM agent automatically collects and contextualizes your logs.

src/content/docs/logs/logs-context/configure-logs-context-php.mdx

@@ -16,6 +16,10 @@ redirects:
 
 With our PHP <InlinePopover type="apm" /> agent, you can get **logs in context**, which lets you see your app logs in the context of your other New Relic data. For general information on this feature, see [APM logs in context](/docs/apm/new-relic-apm/getting-started/get-started-logs-context).
 
+<Callout variant="tip">
+Got lots of PHP logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## Automatic logs in context options [#automatic-logs-in-context]
 
 If you're using a supported framework, you can configure the APM agent to send your app's logs and linking metadata automatically to New Relic. Supported frameworks for automatic logs in context include:

src/content/docs/logs/logs-context/configure-logs-context-python.mdx

@@ -16,6 +16,10 @@ redirects:
 
 With our Python <InlinePopover type="apm" /> agent, you can get **logs in context**, which lets you see your app logs in the context of your other New Relic data. For general information on this feature, see [APM logs in context](/docs/apm/new-relic-apm/getting-started/get-started-logs-context).
 
+<Callout variant="tip">
+Got lots of Python logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## Automatic logs in context options [#automatic]
 
 You have three options to configure APM logs in context to send your app's logs and linking metadata automatically to New Relic.

src/content/docs/logs/logs-context/configure-logs-context-ruby.mdx

@@ -17,6 +17,10 @@ redirects:
 
 With our Ruby <InlinePopover type="apm" /> agent, you can get **logs in context**, which lets you see your app logs in the context of your other New Relic data. For general information on this feature, see [APM logs in context](/docs/apm/new-relic-apm/getting-started/get-started-logs-context).
 
+<Callout variant="tip">
+Got lots of Ruby logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## Automatic logs in context options [#automatic]
 
 You have three options to configure <InlinePopover type="apm" /> logs in context to send your app's logs and linking metadata automatically to New Relic.

src/content/docs/logs/logs-context/get-started-logs-context.mdx

@@ -20,6 +20,10 @@ import apmLogsCroppedUi from 'images/apm_screenshot-crop_logs-cropped-ui.webp'
 
 There are [several ways to report your logs to New Relic](/docs/logs/get-started/get-started-log-management). Using our APM agents is one popular way, especially for smaller teams and DevOps teams that value the benefit of not having to use any other log management tools. 
 
+<Callout variant="tip">
+Got lots of logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## APM logs in context [#apm-logs-defined]
 
 Our <InlinePopover type="apm" /> agents have a feature called **logs in context**. For more on the benefits of this feature, see [Logs in context](/docs/logs/logs-context/logs-in-context).

src/content/docs/logs/logs-context/java-configure-logs-context-all.mdx

@@ -55,6 +55,9 @@ redirects:
 
 With our Java <InlinePopover type="apm" /> agent, you can get **logs in context**, which lets you see your app logs in the context of your other New Relic data. For general information on this feature, see [APM logs in context](/docs/apm/new-relic-apm/getting-started/get-started-logs-context).
 
+<Callout variant="tip">
+Got lots of Java logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
 
 ## Automatic logs in context options [#automatic]
 

src/content/docs/logs/logs-context/logs-in-context.mdx

@@ -37,6 +37,11 @@ To see how logs in context can help you find the root cause of an issue in your
   type="youtube"
 />
 
+
+<Callout variant="tip">
+Got lots of logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## See the root cause of issues across your platform [#compatibility-requirements]
 
 By bringing all of your application and infrastructure data together in a single solution, you can get to the root cause of issues faster. Logs in context help you quickly see meaningful patterns and trends.

src/content/docs/logs/logs-context/net-configure-logs-context-all.mdx

@@ -28,6 +28,10 @@ import logsDotnetLogsinContextSerilog from 'images/logs_diagram_dotnet-logs-in-c
 
 With our .NET <InlinePopover type="apm" /> agent, you can get **logs in context**, which lets you see your app logs in the context of your other New Relic data. For general information on this feature, see [APM logs in context](/docs/apm/new-relic-apm/getting-started/get-started-logs-context).
 
+<Callout variant="tip">
+Got lots of .Net logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 ## Automatic logs in context options [#automatic]
 
 You have three options to configure <InlinePopover type="apm" /> logs in context to send your app's logs and linking metadata automatically to New Relic. Supported frameworks for automatic logs in context using in agent forwarding include:

src/content/docs/logs/logs-context/upgrade-to-automatic-logs-context.mdx

@@ -14,6 +14,10 @@ If you are currently sending application logs to New Relic, it is possible to se
 
 If you have extensive data processing or enrichment logic in your existing log forwarder configuration, sending logs directly from the APM agents will skip that step.
 
+<Callout variant="tip">
+Got lots of Go logs? Check out our [tutorial on how to optimize and manage them](/docs/tutorial-large-logs/get-started-managing-large-logs/). 
+</Callout>
+
 There are two primary upgrade paths we recommend to avoid sending duplicate logs:
 
 1. Update to the latest [APM agent](https://docs.newrelic.com/docs/new-relic-one/install-configure/update-new-relic-agent/), which automatically forwards logs, and then disable the log forwarder:

src/install/python/python-agent-whats-next.mdx

@@ -10,6 +10,7 @@ headingText: What's next?
     <WhatsNextTile title="What's next?">
 
     Now that you've installed the Python agent, [learn how to solve perfomance issues](/docs/journey-app-slow/root-causes/) with our tutorial series. 
+
     #### Consider looking at these docs:
 
     * [Troubleshooting with event loop diagnostics](/docs/apm/agents/python-agent/supported-features/python-event-loop-diagnostics/)