Merge pull request #13877 from newrelic/daily-release/Jul-17-2023-10_57

Daily release/jul 17 2023 10 57

src/@newrelic/gatsby-theme-newrelic/icons/newrelic/nav-collapse.js

@@ -29,7 +29,7 @@ const NavCollapseIcon = (props) => {
   const [rectSpring] = useSpring(
     () => ({
       delay: 280,
-      from: { x: '0' },
+      from: { x: '0px' },
       to: { x: '14px' },
       reverse: sidebar,
       config: RECT_SPRING,

src/components/MainLayoutContext.js

@@ -1,4 +1,13 @@
 import { createContext, useContext } from 'react';
 
 export const MainLayoutContext = createContext();
+/**
+ * exposes whether the site's left nav sidebar is currently open
+ *
+ * @example
+ *
+ * ```js
+ * const [sidebar] = useMainLayoutContext(); // true | false
+ * ```
+ */
 export const useMainLayoutContext = () => useContext(MainLayoutContext);

src/content/docs/data-apis/manage-data/drop-data-using-nerdgraph.mdx

@@ -20,27 +20,28 @@ One way to [manage your data ingest](/docs/data-apis/manage-data/manage-data-com
 
 ## Overview [#overview]
 
-With data dropping rules, you can specify which types of data you don't want saved to your New Relic organization. This data is not counted towards your [data ingest](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing) or ingest billing. 
+With data dropping rules, you can specify which types of data you don't want saved to your New Relic organization. 
 
-Learn more in this NerdBytes video (7:09 minutes):
+Dropped data does not count towards your data ingest and so is not billable. To learn more about what data counts as billable or not, see [Data ingest](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#usage-calculation). 
+
+Drop rules only apply to data that arrives from the moment you create the rule. They don't delete data that's [already been ingested](/docs/telemetry-data-platform/ingest-manage-data/manage-data/manage-data-retention#data-deletion).
+
+Learn more about dropping data in this video (7:09 minutes):
 
 <Video
   id="ww0mim4c5jk"
   type="youtube"
 />
 
-Besides using NerdGraph, other ways to drop data include:
+Besides creating drop-data rules, other ways to minimize unwanted data include:
 
-* If you're using Prometheus remote write, see [Drop Prometheus remote write data](/docs/integrations/prometheus-integrations/install-configure/remote-write-drop-data/).
-* If you're reporting logs, you can [drop log data via the UI](/docs/logs/ui-data/drop-data-drop-filter-rules).
 * If you want to drop APM metric timeslice data, you can use [metric normalization rules](/docs/new-relic-one/use-new-relic-one/ui-data/metric-normalization-rules).
+* If you're reporting logs, you can [drop log data via the UI](/docs/logs/ui-data/drop-data-drop-filter-rules).
+* If you're using Prometheus remote write, see [Drop Prometheus remote write data](/docs/integrations/prometheus-integrations/install-configure/remote-write-drop-data/).
 
 ## Requirements [#requirements]
 
-The ability to create and edit drop filter rules depends on which user model you're on:
-
-* Newer user model: you must be assigned a role with "NRQL drop rules" [capabilities](/docs/accounts/accounts-billing/new-relic-one-user-management/user-capabilities).
-* Original user model: you must have an [Admin role](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles).
+The ability to create and edit drop filter rules is linked to the [`NRQL drop rules` capability](/docs/accounts/accounts-billing/new-relic-one-user-management/user-capabilities#insights).
 
 The following data types can be targeted for data dropping:
 
@@ -51,19 +52,17 @@ The following data types can be targeted for data dropping:
 * Custom events (like those generated by the [APM agent APIs](/docs/insights/insights-data-sources/custom-data/insert-custom-events-new-relic-apm-agents) or the [Event API](/docs/insights/insights-data-sources/custom-data/introduction-event-api))
 * Log data (you can also [use the UI to drop data](/docs/logs/ui-data/drop-data-drop-filter-rules))
 * Distributed tracing spans
-* [Default infrastructure monitoring events](/docs/infrastructure/manage-your-data/data-instrumentation/default-infrastructure-monitoring-data) and [infrastructure integrations](/docs/integrations/infrastructure-integrations/get-started/introduction-infrastructure-integrations) events, with these caveats:
-  * Aggregated, non-raw `SystemSample`, `ProcessSample`, `NetworkSample` and `StorageSample` can't be dropped (for more on this, see [Data retention](/docs/data-apis/manage-data/manage-data-retention/#infrastructure-data)). This data doesn't count towards your data ingest.
-  * Raw infrastructure data is used for alerting, so if you are dropping these events, you will not be able to alert on them even if you see data in charts with time windows longer than 59 minutes (such as alert condition preview charts).
-* [Dimensional metrics](/docs/telemetry-data-platform/ingest-manage-data/understand-data/new-relic-data-types#dimensional-metrics), with these caveats:
-  * Billing impacts: for [our usage-based pricing](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), dropped data is not billable. For [our original pricing model](/docs/accounts/original-accounts-billing/product-pricing/product-based-pricing), dropped data is billable.
+* [Default infrastructure monitoring events](/docs/infrastructure/manage-your-data/data-instrumentation/default-infrastructure-monitoring-data) and [infrastructure integrations](/docs/integrations/infrastructure-integrations/get-started/introduction-infrastructure-integrations) events. Some caveats:
+  * When you drop this data, the raw data is dropped, but the aggregated `SystemSample`, `ProcessSample`, `NetworkSample` and `StorageSample` events are still available (for more on this, see [Data retention](/docs/data-apis/manage-data/manage-data-retention/#infrastructure-data)). Though still available, this data doesn't count towards ingest and is not billable.
+  * Raw infrastructure data is used for alerting, so if you drop that data, you can't alert on it. Because the aggregated data is still available, you may still see that data in charts with time ranges above 59 minutes. 
+* [Dimensional metrics](/docs/telemetry-data-platform/ingest-manage-data/understand-data/new-relic-data-types#dimensional-metrics) (the `Metric` data type). Some caveats:
+  * For organizations on our [original pricing model](/docs/accounts/original-accounts-billing/product-pricing/product-based-pricing): billing is based on product subscription, meaning dropped dimensional metrics remain billable.
   * For metrics generated by the [events-to-metrics service](/docs/data-ingest-apis/get-data-new-relic/metric-api/events-metrics-service-create-metrics): drop rules won't work but these metrics can be stopped or attributes pruned by disabling or re-configuring the events-to-metric rule.
 
-You can't use a drop rule to delete data that's already been ingested and stored. That data [can't be edited or deleted](/docs/telemetry-data-platform/ingest-manage-data/manage-data/manage-data-retention#data-deletion). 
-
 ## Create a drop data rule [#how-to]
 
 <Callout variant="caution">
-  Use caution when deciding to drop data. The data you drop is not recoverable. Before using this feature, please review [caution information below.](#caution)
+  Use caution when deciding to drop data. The data you drop can't be recovered. For more details on potential issues, see [Caution notes](#caution).
 </Callout>
 
 To drop data, create a [NerdGraph](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph)-format drop rule that includes:

src/content/docs/data-apis/manage-data/manage-data-retention.mdx

@@ -104,7 +104,7 @@ This table shows the default [namespace](/docs/glossary/glossary) retention sett
       </td>
 
       <td>
-        APM errors (metadata)
+        APM errors 
       </td>
 
       <td>
@@ -121,7 +121,7 @@ This table shows the default [namespace](/docs/glossary/glossary) retention sett
       </td>
 
       <td>
-        APM errors (stack traces)
+        APM error stack traces
       </td>
 
       <td>

src/content/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard.mdx

@@ -190,9 +190,9 @@ Click a dashboard to open its charts. A dashboard page includes these features:
 
   There're two ways to turn on TV mode:
 
-      * When viewing a dashboard, select the <Icon name="fe-tv"/> icon at the top right.
+      * When viewing a dashboard, select the <Icon name="fe-monitor"/> icon at the top right.
 
-      * Add this parameter to a dashboard page URL: `&platform[tvMode]=true`
+      * Add this parameter to a dashboard page URL: `&tvMode=true`
 
 
   To configure TV mode, from a dashboard, click the <Icon name="fe-more-horizontal"/> icon on the right corner and select **Settings**. Under the TV mode section, there're these options: