Skip to content

Commit

Permalink
rename console step, add svgs, update console step, update some copy
Browse files Browse the repository at this point in the history
  • Loading branch information
akristen committed Oct 21, 2024
1 parent 14d1fbb commit 343e030
Show file tree
Hide file tree
Showing 9 changed files with 99 additions and 64 deletions.
18 changes: 18 additions & 0 deletions src/install/assets/install-logos/cloudformation.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
18 changes: 18 additions & 0 deletions src/install/assets/install-logos/cloudwatch.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
18 changes: 18 additions & 0 deletions src/install/assets/install-logos/console.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
58 changes: 0 additions & 58 deletions src/install/aws-cloudwatch/cloudwatch-path/console-api-calls.mdx

This file was deleted.

32 changes: 32 additions & 0 deletions src/install/aws-cloudwatch/cloudwatch-path/console.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
---
componentType: default
optiontype: task
headingText: Integrate CloudWatch Metric Streams with AWS Console
---

This step gives you the necessary inputs to direct your metrics to New Relic. From AWS Console, you'll create a Firehose delivery stream and a metric stream. Once both are created, you'll finish set up by adding your AWS account in the New Relic platform

1. Create a Kinesis Data Firehose Delivery Stream and configure the following destination parameters:
* Source: Direct PUT or other sources
* Data transformation: Disabled
* Record format conversion: Disabled
* Destination: New Relic
* Ensure the following settings are defined:
* New Relic configuration (Destination Settings)
* HTTP endpoint URL - US Datacenter: `https://aws-api.newrelic.com/cloudwatch-metrics/v1`
* HTTP endpoint URL - EU Datacenter: `https://aws-api.eu01.nr-data.net/cloudwatch-metrics/v1`
* API key: Enter your <InlinePopover type="licenseKey"/>
* Content encoding: `GZIP`
* Retry duration: `60`
* S3 backup mode: Failed data only
* S3 bucket: select a bucket or create a new one to store metrics that failed to be sent.
* New Relic buffer conditions
* Buffer size: `1 MB`
* Buffer interval: `60 (seconds)`
* Permissions IAM role:
* Create or update IAM role
1. From AWS Console, go to <DNT>**CloudWatch service**</DNT> and select the <DNT>**Streams**</DNT> option under the <DNT>**Metrics**</DNT> menu. Click <DNT>**Create metric stream**</DNT>.
1. Determine the right configuration based on your use cases. For example, use inclusion and exclusion filters to select the services that should push metrics to New Relic.
1. Select the Firehose you created in the first step, then define a meaningful name for the stream. For example, you could name it `newrelic-metric-stream`.
1. Change default output format to `Open Telemetry 0.7`. Keep in mind that JSON isn't supported.
1. Go to <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS**</DNT>. Click <DNT>**Add an AWS account**</DNT>, then <DNT>**Use metric streams**</DNT>. Finish set up by following the steps.
2 changes: 1 addition & 1 deletion src/install/aws-cloudwatch/cloudwatch-path/migrate.mdx
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
componentType: default
optiontype: task
headingText: UPDATE
headingText: Migrate to the CloudWatch Metric Streams integration
---

We recommend that existing customers migrate from API polling to Metric Streams using a CloudFormation template by following the instructions below.
Expand Down
2 changes: 1 addition & 1 deletion src/install/aws-cloudwatch/default.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,4 @@ Once your permissions are set, you can set up the CloudWatch Metric Streams inte

* You can follow our in-app guided install, which directs you to the New Relic platform where you'll create Cloudformation template for CloudWatch Metric Streams. You may want to return to this doc to review the CloudFormation template parameters.
* You can follow some procedures that use AWS Console to create resources yourself.
* If you're currently integrating with API polling, you can migrate to CloudWatch Metric Streams.
* If you're currently using API polling, you can follow some procedures to migrate to CloudWatch Metric Streams.
4 changes: 4 additions & 0 deletions src/install/aws-cloudwatch/validate-data.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,3 +12,7 @@ To confirm you're receiving data from the Metric Streams, follow these steps:
* Explore your data. Use metrics and events to find a specific set of metrics, access all dimensions available for a given metric, and more.

It may take few minutes until new resources are detected and synthesized as entities. See [cloud integrationssystem limits](/docs/data-apis/manage-data/view-system-limits) for more information.

<Callout variant="tip">
AWS CloudWatch metrics for global services, such AWS Billing, are only availble in the <DNT>**us-east-1**</DNT> region. Make sure there's an active CloudWatch metric stream configured in that region.
</Callout>
Loading

0 comments on commit 343e030

Please sign in to comment.