From dcf648238e4981526c5f6988cf8e838e16b3a427 Mon Sep 17 00:00:00 2001
From: JimHagan <jhagan@newrelic.com>
Date: Thu, 24 Mar 2022 13:59:34 -0400
Subject: [PATCH] Added about this dashboard page to the entity breakdown
 dashboard

---
 .../data-ingest-entity-breakdown.json         | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/quickstarts/oma-data-gov/dashboards/data-ingest-entity-breakdown.json b/quickstarts/oma-data-gov/dashboards/data-ingest-entity-breakdown.json
index affce18c75..743c199f90 100644
--- a/quickstarts/oma-data-gov/dashboards/data-ingest-entity-breakdown.json
+++ b/quickstarts/oma-data-gov/dashboards/data-ingest-entity-breakdown.json
@@ -255,6 +255,28 @@
             "linkedEntityGuids": null
           }
         ]
+      },
+      {
+        "name": "About this dashboard",
+        "description": null,
+        "widgets": [
+          {
+            "visualization": {
+              "id": "viz.markdown"
+            },
+            "layout": {
+              "column": 1,
+              "row": 1,
+              "height": 5,
+              "width": 6
+            },
+            "title": "",
+            "rawConfiguration": {
+              "text": "# How these charts work\nThese charts use the `bytecountestimate()` operator which can estimate the data ingest overhead for nearly any event or metric in NRDB.  \n\nHere is an example of a query that estimates data ingest overhead for Browser data faceted by appName:\n\n```\nFROM PageAction, PageView, PageViewTiming, AjaxRequest, JavaScriptError\nSELECT rate(bytecountestimate()/10e8, 30 day) AS 'GB Ingest'\nFACET appName SINCE 1 DAY AGO\n```\n\n### Benefits\n- The data is far more granular than those in the main [Data Governance Baseline](https://docs.newrelic.com/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-baselining#install-dashboard) dashboard which rely only on NrConsumption metrics\n- We are able to facet by nearly any attribute\n\n### Drawbacks\n- The queries are slower as the data can be quite high volume and the bytecountestimate() operator has some overhead.\n- The can only be queried up to the data retentino period for that telemetry.  For some telemetry types this may not be more than a week.\n\n## View the [data governance guide](https://docs.newrelic.com/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-intro) for more information\n"
+            },
+            "linkedEntityGuids": null
+          }
+        ]
       }
     ]
   }
\ No newline at end of file