docs(NR-290692): add clarifying verbiage on how markers are included on NRQL charts

src/content/docs/change-tracking/change-tracking-view-analyze.mdx

@@ -33,6 +33,51 @@
   <Callout variant="tip">
     If you land on a dashboard or entity summary page and don't see the tracked change you're expecting, check your time picker selection. It might be outside the window you are looking at.
   </Callout>
+
+  * If you are still not seeing the markers that you're expecting, please verify whether you have added those change events to the entities relevant to the chart. Most charts are driven by a NRQL query that you can see by clicking on the three-dots at the tile's top-right corner. The entities relevant to the chart are derived from the NRQL query based on the following logic:
+    * Entities that are directly specified in the query for the chart using either an `IN` or `=` operator (e.g. queries with an `WHERE entity.guid IN ('MTE2NjAxMzJ8QVBNfEFQUExJQ0FUSU9OfDEyMDk1MjY5')` clause). While we use `entity.guid` as an example, other properties may also be used to explicitly designate entities for the query. They are:
+      * `entity.guid`
+      * `entityGuid`
+      * `entity.name`
+      * `entityName`
+      * `appName`
+      * `service.name`
+    * Entities that are [related](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/core-concepts/what-entity-new-relic/#related-entities) to entities specified via the method above. Only the following relationship-types are considered:
+      * `CALLS`
+      * `SERVES`
+      * `IS`
+      * `CONTAINS`
+      * `HOSTS`
+
+  Please be advised that __NRQL queries for charts are currently scoped to a single account__. This means that if you specify entity-GUIDs belonging to multiple accounts, only markers from a single account will be visualized.
+
+  For example, let's say that the query for your chart looks like the following:
+  ```
+  FROM Transaction SELECT count(*) WHERE entityGuid IN ('MTE2NjAxMzJ8QVBNfEFQUExJQ0FUSU9OfDg0MTY1OTI','MTEwNjI2OTl8QVBNfEFQUExJQ0FUSU9OfDg5ODEwMDk5') TIMESERIES MAX SINCE 2 weeks AGO
+  ```
+  Markers from both entities will show up on the chart. Additionally, markers from related-entities will also be included on the chart. To determine the list of related-entities, you can run a GraphQL query similar to the example below:
+  ```
+  {
+    actor {
+      entity(guid: "MTEwNjI2OTl8QVBNfEFQUExJQ0FUSU9OfDg5ODEwMDk5") {
+        relatedEntities(
+          filter: {relationshipTypes: {include: [CALLS, SERVES, IS, CONTAINS, HOSTS]}}
+        ) {
+          results {
+            type
+            source {
+              guid
+            }
+            target {
+              guid
+            }
+          }
+        }
+      }
+    }
+  }
+  ```
+
 * <DNT>**Entity sidebar:**</DNT> To see a table of changes, click on <DNT>**Change tracking**</DNT> for any entity that has recorded changes. It features a time range selector and table filtering and sorting options. Use these to narrow the field of changes or to find a specific change.
   <Callout variant="tip">Note that you may need to adjust the selected time range on this page to see tracked changes. Also, by default the table will only lazy load up to 2,000 changes. Keep this in mind as you're filtering, searching, and adjusting your time range.</Callout>
 * <DNT>**New Relic <InlinePopover type="alerts"/> & Detection:**</DNT> If your change is related to an issue, you'll see it listed in the <DNT>**Root Cause Analysis**</DNT> section of the <DNT>**Issues**</DNT> page.