fix(EOL Q4): AWS F thru M

newrelic · Jan 31, 2022 · 08341a2 · 08341a2
1 parent 4c5dd42
commit 08341a2
Show file tree

Hide file tree

Showing 7 changed files with 32 additions and 20 deletions.
diff --git a/...amazon-integrations/aws-integrations-list/aws-health-monitoring-integration.mdx b/...amazon-integrations/aws-integrations-list/aws-health-monitoring-integration.mdx
@@ -45,8 +45,7 @@ To use this integration's data:
 
 1. Go to [**one.newrelic.com**](https://one.newrelic.com) **> Infrastructure > AWS**.
 2. Select any of the available AWS Health integration links.
-3. To view a complete list of open issues, select the [**Inventory** page](/docs/infrastructure/new-relic-infrastructure/infrastructure-ui-pages/infrastructure-inventory-page-search-your-entire-infrastructure).
-4. To view a timeline when an AWS Health inventory event is created, modified, or deleted, use the [**Events** page](/docs/infrastructure/new-relic-infrastructure/infrastructure-ui-pages/infrastructure-events-page-live-feed-every-config-change).
+3. To view a timeline when an AWS Health event is created, modified, or deleted, use the [**Events** page](/docs/infrastructure/new-relic-infrastructure/infrastructure-ui-pages/infrastructure-events-page-live-feed-every-config-change).
 
 ## Events monitoring and alerts [#event-monitoring]
 
@@ -179,7 +178,11 @@ SELECT uniqueCount(affectedEntityArn) FROM AwsHealthNotification where statusCod
 
 ## Inventory data [#metrics]
 
-[Inventory data](/docs/infrastructure/integrations-getting-started/getting-started/understand-integration-data-data-types#inventory-data) provides information about active AWS Health events. New Relic's AWS Health integration generates three types of entities, each of which have the same inventory data:
+<Callout variant="important" title="EOL NOTICE">
+After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our [Explorers Hub post](https://discuss.newrelic.com).
+</Callout>
+
+Inventory data provides information about active AWS Health events. New Relic's AWS Health integration generates three types of entities, each of which have the same inventory data:
 
 * `aws/health/issue/`
 * `aws/health/scheduled-change/`

diff --git a/...re/amazon-integrations/aws-integrations-list/aws-iam-monitoring-integration.mdx b/...re/amazon-integrations/aws-integrations-list/aws-iam-monitoring-integration.mdx
@@ -50,6 +50,10 @@ The IAM integration doesn't capture any performance metrics in the traditional s
 
 ## Inventory data [#inventory]
 
+<Callout variant="important" title="EOL NOTICE">
+After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our [Explorers Hub post](https://discuss.newrelic.com).
+</Callout>
+
 The IAM integration reports this [inventory data](/docs/infrastructure/integrations-getting-started/getting-started/understand-integration-data-data-types#inventory-data):
 
 <table>

diff --git a/...re/amazon-integrations/aws-integrations-list/aws-iot-monitoring-integration.mdx b/...re/amazon-integrations/aws-integrations-list/aws-iot-monitoring-integration.mdx
@@ -11,7 +11,7 @@ redirects:
   - /docs/aws-iot-monitoring-integration
 ---
 
-New Relic offers an [integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) for reporting your AWS IoT [metric data](/docs/telemetry-data-platform/understand-data/new-relic-data-types/#metrics-new-relic) and [inventory data](/docs/telemetry-data-platform/understand-data/new-relic-data-types/).
+New Relic offers an [integration](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) for reporting your AWS IoT [metric data](/docs/telemetry-data-platform/understand-data/new-relic-data-types/#metrics-new-relic).
 
 [AWS IoT](https://docs.aws.amazon.com/iot/latest/developerguide/what-is-aws-iot.html) is a service that provides communication between Internet-connected devices and the AWS Cloud. It also collects and stores telemetry data. With the AWS IoT Infrastructure integration, you can access these features:
 
@@ -64,16 +64,6 @@ After [connecting the AWS IoT integration to New Relic](/docs/integrations/amazo
         Go to the [query builder](/docs/query-your-data/explore-query-data/query-builder/query-builder-basic-mode) and create queries for `IOTBrokerSample`, `IOTRuleActionSample`, and `IOTRuleSample` events.
       </td>
     </tr>
-
-    <tr>
-      <td>
-        [Inventory data](#inventory) for AWS IoT entities
-      </td>
-
-      <td>
-        Go to [**one.newrelic.com**](http://one.newrelic.com) **> Infrastructure** **> Inventory** and search for or select `aws/iot/broker/`, `aws/iot/rule-action/`, or `aws/iot/rule`.
-      </td>
-    </tr>
   </tbody>
 </table>
 
@@ -454,6 +444,10 @@ To view metric data for your AWS IoT integration, [create NRQL queries](/docs/in
 
 ## Inventory data [#inventory]
 
+<Callout variant="important" title="EOL NOTICE">
+After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our [Explorers Hub post](https://discuss.newrelic.com).
+</Callout>
+
 To [view inventory data](/docs/integrations/new-relic-integrations/getting-started/understand-use-data-infrastructure-integrations#overview) for AWS IoT, go to [**one.newrelic.com**](https://one.newrelic.com) **> Infrastructure > Inventory** and search for or select the following:
 
 <CollapserGroup>

diff --git a/...ions/aws-integrations-list/aws-kinesis-data-firehose-monitoring-integration.mdx b/...ions/aws-integrations-list/aws-kinesis-data-firehose-monitoring-integration.mdx
@@ -21,7 +21,7 @@ redirects:
 
 [Amazon Kinesis Data Firehose](https://aws.amazon.com/kinesis/firehose/) provides a simple way to capture and load streaming data. It can capture, transform, and load streaming data into Amazon Kinesis Data Analytics, Amazon S3, Amazon Redshift, and Amazon Elasticsearch Service, enabling near real-time analytics.
 
-New Relic's Kinesis Data Firehose integration reports data such as indexed records and bytes, counts of data copied to AWS services, the age and freshness of records, and other [metric data](#metrics) and [service metadata](#inventory).
+New Relic's Kinesis Data Firehose integration reports data such as indexed records and bytes, counts of data copied to AWS services, the age and freshness of records, and other [metric data].
 
 ## Activate integration [#activate]
 
@@ -216,6 +216,10 @@ This integration collects the following metrics:
 
 ## Inventory data [#inventory]
 
+<Callout variant="important" title="EOL NOTICE">
+After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our [Explorers Hub post](https://discuss.newrelic.com).
+</Callout>
+
 New Relic collects the following Kinesis Firehose inventory data. For more about inventory data, see [Understand and use data](/docs/infrastructure/integrations-getting-started/getting-started/understand-integration-data-data-types#inventory-data).
 
 <table>

diff --git a/...tions/aws-integrations-list/aws-kinesis-data-streams-monitoring-integration.mdx b/...tions/aws-integrations-list/aws-kinesis-data-streams-monitoring-integration.mdx
@@ -234,6 +234,10 @@ This integration collects the following metrics:
 
 ## Inventory data [#inventory]
 
+<Callout variant="important" title="EOL NOTICE">
+After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our [Explorers Hub post](https://discuss.newrelic.com).
+</Callout>
+
 <Callout variant="tip">
   Tags (indicated with an **\***) are only fetched when [tags collection](/docs/integrations/new-relic-integrations/getting-started/configure-polling-frequency-data-collection-cloud-integrations#collect_tags) is on.
 </Callout>

diff --git a/...amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration.mdx b/...amazon-integrations/aws-integrations-list/aws-lambda-monitoring-integration.mdx
@@ -24,7 +24,7 @@ redirects:
 
 Lambda functions are pieces of custom code that run when a certain event happens. In order to identify the events that invoke a particular Lambda function, AWS Lambda users define event source mappings. Optionally, aliases can be used to point to a specific version of a Lambda function.
 
-New Relic's AWS Lambda integration reports data such as invocation counts, error counts, function timers, and other [metrics](#metrics) and [inventory data](#inventory). You can view your Lambda data in pre-built dashboards and also create custom queries and charts in [New Relic One](/docs/infrastructure/integrations-getting-started/getting-started/use-integration-data-new-relic-insights).
+New Relic's AWS Lambda integration reports data such as invocation counts, error counts, function timers, and other [metrics](#metrics). You can view your Lambda data in pre-built dashboards and also create custom queries and charts in [New Relic One](/docs/infrastructure/integrations-getting-started/getting-started/use-integration-data-new-relic-insights).
 
 ## Activate integration [#activate]
 
@@ -212,6 +212,10 @@ Lambda region data is attached to the `ServerlessSample` [event type](/docs/insi
 
 ## Inventory data [#inventory]
 
+<Callout variant="important" title="EOL NOTICE">
+After March 2022, we're discontinuing support for several capabilities, including inventory data for cloud integrations. For more details, including how you can easily prepare for this transition, see our [Explorers Hub post](https://discuss.newrelic.com).
+</Callout>
+
 This integration supports the following inventory data. For more about inventory data, see [Understand integration data](/docs/infrastructure/integrations-getting-started/getting-started/understand-integration-data-data-types#inventory-data).
 
 ### aws/lambda/function/

diff --git a/.../infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream.mdx b/.../infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream.mdx
@@ -296,7 +296,7 @@ On a typical deployment, migrating from API polling to metric stream involves th
 4. Disable all unnecessary polling integrations in the previous AWS provider account. The following integrations still need to be enabled since they aren't fully replaced by metric streams:
   - AWS Billing, AWS CloudTrail, AWS Health, AWS Trusted Advisor.
 
-### Query, dashboard, alert and inventory considerations [#considerations]
+### Query, dashboard, and alert considerations [#considerations]
 
 AWS Metric Streams integration uses the Metric API to push metrics in the dimensional metric format.
 
@@ -308,7 +308,6 @@ Please consider the following when migrating from poll-based integrations:
 * **Dashboards**: Custom dashboards that use poll-based AWS integration events will still work as expected. 
 * **Alerts**: Alert conditions that use poll-based AWS events will still work. We recommend adapting those to the dimensional metric format (using NRQL as source). 
 * **Entities**: New Relic Explorer might show duplicated entities for up to 24 hours.
-* **Inventory**: the [Inventory page](/docs/infrastructure/infrastructure-ui-pages/infra-ui-pages/infrastructure-inventory-page-search-your-entire-infrastructure/) is not supported with AWS CloudWatch metric streams (inventory telemetry is not included in the stream). 
 
 ### Integrations not fully replaced by metric streams [#integrations-not-replaced-streams]
 
@@ -319,8 +318,8 @@ The AWS CloudWatch Metric Streams integration only collects CloudWatch metrics,
 - AWS Trusted Advisor
 - AWS VPC
 
-## Infrastructure Agent metrics and EC2 metadata decoration [#infra-data-decoration]
+## Infrastructure agent metrics and EC2 metadata decoration [#infra-data-decoration]
 
 As with the EC2 API polling integration, when the infrastructure agent is installed on a host and the EC2 namespace is active via AWS CloudWatch metric stream integration, then all the infrastructure agent events and metrics are decorated with additional metadata. 
 
-The following attributes will decorate infrastructure samples (some might not be applicable on all environments): `awsAvailabilityZone`, `ec2InstanceId`, `ec2PublicDnsName`, `ec2State`, `ec2EbsOptimized`, `ec2PublicIpAddress`, `ec2PrivateIpAddress`, `ec2VpcId`, `ec2AmiId`, `ec2PrivateDnsName`, `ec2KeyName`, `ec2SubnetId`, `ec2InstanceType`, `ec2Hypervisor`, `ec2Architecture`, `ec2RootDeviceType`, `ec2RootDeviceName`, `ec2VirtualizationType`, `ec2PlacementGroupName`, `ec2PlacementGroupTenancy`.
+The following attributes will decorate infrastructure samples. Some of these may not be applicable on all environments: `awsAvailabilityZone`, `ec2InstanceId`, `ec2PublicDnsName`, `ec2State`, `ec2EbsOptimized`, `ec2PublicIpAddress`, `ec2PrivateIpAddress`, `ec2VpcId`, `ec2AmiId`, `ec2PrivateDnsName`, `ec2KeyName`, `ec2SubnetId`, `ec2InstanceType`, `ec2Hypervisor`, `ec2Architecture`, `ec2RootDeviceType`, `ec2RootDeviceName`, `ec2VirtualizationType`, `ec2PlacementGroupName`, `ec2PlacementGroupTenancy`.