From d7b8667ce5c1cd3417c24fd9436dcd470ebe0110 Mon Sep 17 00:00:00 2001 From: ally sassman <42753584+a-sassman@users.noreply.github.com> Date: Tue, 21 Feb 2023 18:56:14 -0800 Subject: [PATCH] Update data-governance-optimize-ingest-guide.mdx --- .../data-governance-optimize-ingest-guide.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/data-governance-optimize-ingest-guide.mdx b/src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/data-governance-optimize-ingest-guide.mdx index 9c81503b79c..e61be3d23c7 100644 --- a/src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/data-governance-optimize-ingest-guide.mdx +++ b/src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/data-governance-optimize-ingest-guide.mdx @@ -1507,4 +1507,3 @@ Answering the following questions will help you develop confidence in your abili ## Conclusion [#conclusion] The process section showed us how to associate our telemetry with specific observability value drivers or objectives. This can make the hard decision of optimizing our account ingest somewhat easier. We learned how to describe a high level [optimization plan](/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-optimizing#develop-plan) that optimizes ingest while protecting our objectives. Finally we were introduced a [rich set of recipes](/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-optimizing#use-reduction-techniques) for configuration and drop-rule-based ingest optimizations. -](https://github.com/JimHagan/docs-website.git)