chore(plugins): Remove all references to Plugins product

Exception: Regulatory audits page
newrelic · Oct 23, 2021 · 919555b · 919555b
1 parent 02b6276
commit 919555b
Show file tree

Hide file tree

Showing 27 changed files with 17 additions and 328 deletions.
diff --git a/...l-accounts-billing/product-based-pricing/overview-data-retention-components.mdx b/...l-accounts-billing/product-based-pricing/overview-data-retention-components.mdx
@@ -924,113 +924,6 @@ Select a New Relic product to see details about its data retention:
     </table>
   </Collapser>
 
-  <Collapser
-    id="plugins"
-    title="Plugins"
-  >
-    The retention period for historical data depends on the product and subscription level. The following data retention periods exist for New Relic Plugins.
-
-    <Callout variant="important">
-      Plugins is not supported with accounts that host data in the [EU region data center](/docs/using-new-relic/welcome-new-relic/getting-started/introduction-eu-region-data-center).
-    </Callout>
-
-    ## Plugins data retention
-
-    <table>
-      <thead>
-        <tr>
-          <th style={{ width: "150px" }}>
-            **Component**
-          </th>
-
-          <th style={{ width: "100px" }}>
-            **Lite**
-          </th>
-
-          <th style={{ width: "140px" }}>
-            **Essentials**
-          </th>
-
-          <th style={{ width: "140px" }}>
-            **Pro**
-          </th>
-
-          <th style={{ width: "140px" }}>
-            **Enterprise**
-          </th>
-        </tr>
-      </thead>
-
-      <tbody>
-        <tr>
-          <td>
-            Metric data
-          </td>
-
-          <td>
-            24 hours
-          </td>
-
-          <td>
-            3 days
-          </td>
-
-          <td>
-            90 days
-          </td>
-
-          <td>
-            90 days
-          </td>
-        </tr>
-      </tbody>
-    </table>
-
-    ## Legacy Plugins data retention
-
-    <table>
-      <thead>
-        <tr>
-          <th style={{ width: "250px" }}>
-            **Component**
-          </th>
-
-          <th style={{ width: "140px" }}>
-            **Standard**
-          </th>
-
-          <th style={{ width: "140px" }}>
-            **Startup**
-          </th>
-
-          <th style={{ width: "140px" }}>
-            **Small Business**
-          </th>
-        </tr>
-      </thead>
-
-      <tbody>
-        <tr>
-          <td>
-            Metric data
-          </td>
-
-          <td>
-            7 days
-          </td>
-
-          <td>
-            14 days
-          </td>
-
-          <td>
-            30 days
-          </td>
-        </tr>
-      </tbody>
-    </table>
-  </Collapser>
-
   <Collapser
     id="synthetics"
     title="Synthetics"

diff --git a/...s/advanced-alerts/advanced-techniques/define-custom-metrics-alert-condition.mdx b/...s/advanced-alerts/advanced-techniques/define-custom-metrics-alert-condition.mdx
@@ -39,15 +39,6 @@ To define the custom metric values for your condition:
 3. From the **Categorize** section, select the [product and type of condition](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions) for the custom metric.
 4. From the **Select entities** section, add one or more [targets (entities)](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/select-product-targets-alert-condition) that use your custom metric.
 5. From the **Define thresholds > When target application** section, select **Custom > Search metric name**, and begin typing the custom metric name, select from the list, or type the exact metric name.
-
-   <Callout variant="tip">
-     **Exception:** The custom metric search is not enabled for:
-
-     * Labels for APM apps
-     * New Relic Plugins
-
-     To find the metric name in these situations, use the [Data explorer](/docs/insights/use-insights-ui/explore-data/metric-explorer-search-chart-metrics-sent-new-relic-agents). Then type the exact metric name in the Alerts **Define thresholds** page.
-   </Callout>
 6. Provide the [required threshold values](#custom-metrics-requirements) for your custom metric.
 7. From the **Define thresholds > Condition name** section, provide a [meaningful name](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions#best-practices-conditions) for your custom metric condition, maximum 100 characters.
 8. Optional: Include the [URL with runbook instructions](/docs/alerts/new-relic-alerts-beta/reviewing-alert-incidents/provide-runbook-instructions-alerts) for handling the situation.
@@ -62,8 +53,4 @@ After you save the condition, you can view the selected policy's **Alert conditi
 The **Condition name** does not appear in the **Thresholds** section for a saved condition. If you want to [change the condition name](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions#rename-condition) for a custom metric, edit it from the selected policy's **Alert conditions** page:
 
 1. In the **[one.newrelic.com](https://one.newrelic.com/ "Link opens in a new window.")** top nav, click **Alerts & AI**, click **Alert policies**, then **(select a policy)**.
-2. Click a condition name to edit it, and then type a meaningful name for the condition.
-
-## Custom metric examples for alert notifications [#custom-metric-alert-examples]
-
-If you have created a [plugin](/docs/plugins/developing-plugins/structuring-your-plugin/creating-summary-metrics-plugins) or custom dashboard for your custom metric, you can view your custom metric name there. For other ideas about how to apply custom metrics (for example, to [alert on received and transmitted network stats](https://discuss.newrelic.com/t/alert-on-network-metrics/23902)), visit the [New Relic Explorers Hub](https://discuss.newrelic.com/tags/alerts).
+2. Click a condition name to edit it, and then type a meaningful name for the condition.
diff --git a/...ic-alerts/advanced-alerts/rest-api-alerts/alerts-conditions-api-field-names.mdx b/...ic-alerts/advanced-alerts/rest-api-alerts/alerts-conditions-api-field-names.mdx
@@ -74,7 +74,7 @@ Not every field listed in this glossary is required for every condition type. Th
     id="entities"
     title="entities"
   >
-    This is an array of [entity](/docs/alerts/new-relic-alerts/getting-started/alerts-glossary#alert-entity) IDs identifying the objects that will be monitored with your condition. These may be application IDs, browser IDs, plugin IDs, key transaction IDs, external service IDs, etc.
+    This is an array of [entity](/docs/alerts/new-relic-alerts/getting-started/alerts-glossary#alert-entity) IDs identifying the objects that will be monitored with your condition. These may be application IDs, browser IDs, key transaction IDs, external service IDs, etc.
 
     These are entered as a series of comma-separated integers if there is more than one.
 

diff --git a/.../advanced-alerts/rest-api-alerts/disable-enable-alerts-conditions-using-api.mdx b/.../advanced-alerts/rest-api-alerts/disable-enable-alerts-conditions-using-api.mdx
@@ -48,8 +48,6 @@ The process for disabling or enabling a condition is the same general process fo
          [API Explorer link Get>List](https://rpm.newrelic.com/api/explore/alerts_external_service_conditions/list)
        * [Synthetic monitoring](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#synthetics-conditions-list)  
          [API Explorer link Get>List](https://rpm.newrelic.com/api/explore/alerts_synthetics_conditions/list)
-       * [Plugins](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#plugins-conditions-list)  
-         [API Explorer link Get>List](https://rpm.newrelic.com/api/explore/alerts_plugins_conditions/list)
      </Collapser>
    </CollapserGroup>
 3. For the returned JSON, find the JSON object of the condition you want to change.
@@ -71,8 +69,6 @@ The process for disabling or enabling a condition is the same general process fo
          [API Explorer PUT>Update](https://rpm.newrelic.com/api/explore/alerts_external_service_conditions/update)
        * [Conditions for Synthetic monitoring](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#synthetics-conditions-update))  
          [API Explorer PUT>Update](https://rpm.newrelic.com/api/explore/alerts_synthetics_conditions/update)
-       * [Conditions for Plugins](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#plugins-conditions-update)  
-         [API Explorer PUT>Update](https://rpm.newrelic.com/api/explore/alerts_plugins_conditions/update)
 
        <Callout variant="tip">
          An Update API request can only change one condition at a time, it cannot update a vector of objects. For example, to change three conditions, you will have to make three separate requests.

diff --git a/...ic-alerts/advanced-alerts/rest-api-alerts/manage-entities-alerts-conditions.mdx b/...ic-alerts/advanced-alerts/rest-api-alerts/manage-entities-alerts-conditions.mdx
@@ -13,7 +13,7 @@ redirects:
   - /docs/alerts-applied-intelligence/new-relic-alerts/rest-api-alerts/manage-entities-alerts-conditions
 ---
 
-In alerts, an **entity** is defined as any target for monitoring, such as an application, a browser, or a plugin. The [alerts UI](/docs/alerts/new-relic-alerts/defining-conditions/select-product-targets-alert-condition) shows available entities that you can select. You can also use the REST API and API Explorer to [add](https://rpm.newrelic.com/api/explore/alerts_entity_conditions/add) or [remove](https://rpm.newrelic.com/api/explore/alerts_entity_conditions/remove) entities for a condition.
+In alerts, an **entity** is defined as any target for monitoring, such as an application, a browser, or a host. The [alerts UI](/docs/alerts/new-relic-alerts/defining-conditions/select-product-targets-alert-condition) shows available entities that you can select. You can also use the REST API and API Explorer to [add](https://rpm.newrelic.com/api/explore/alerts_entity_conditions/add) or [remove](https://rpm.newrelic.com/api/explore/alerts_entity_conditions/remove) entities for a condition.
 
 ## Requirements
 
@@ -33,7 +33,6 @@ To update the entity list for a condition:
    * [APM, browser, and mobile](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions)
    * [External services](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#ext-services-conditions)
    * [Synthetic monitoring](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#synthetics-conditions)
-   * [Plugins](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#plugins-conditions)
 4. Modify the condition using the [add](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#add-entity) or [remove](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#remove_entity) API requests.
 
 <Callout variant="important">