From 4a496b511d8f437788e810392e8b2099f5431146 Mon Sep 17 00:00:00 2001 From: JimHagan Date: Fri, 18 Mar 2022 09:35:16 -0400 Subject: [PATCH] Fixed syntax error in image tags --- .../observability-maturity/operational-efficiency/dg-coe.mdx | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-coe.mdx b/src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-coe.mdx index 3dc1c4165d4..db6c9889c36 100644 --- a/src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-coe.mdx +++ b/src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-coe.mdx @@ -72,14 +72,13 @@ Meet to maintain an organization wide telemetry ingest target. This can be brok * Team C (Monthly): 100TB This rough set of targets leaves 100TB as a buffer for uncertainty. You may also choose some specific limits based on certain highly variable telemetry. For example you may set organization or team based limits on Log or Metrics ingest. - ### Monthly ingest check-ins -Monthly Ingest Checkin!} alt="Observability Manger" style={{ height: '66px', width: '75px', verticalAlign: 'middle'}} /> +Monthly Ingest Checkin During these sessions you'll track ingest against your plan and produce action items needed to stay on target. ### Ad hoc anomaly resolution -Adhoc Anomaly Resolution} alt="Observability Manger" style={{ height: '66px', width: '75px', verticalAlign: 'middle'}} /> +Ad Hoc Anomaly Resolution Occasionally a system refactor or organizational change could lead to an unexpected increase in data ingest. In this scenario it may be necessary to call a meeting to address the specific topic. Some scenarios to watch for: - A new software deployment increases log volume by 3x.