-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating intro to AWS doc #18722
Updating intro to AWS doc #18722
Conversation
… api polling with metric streams integration
Hi @akristen 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…stall method table, copy edits
...ontent/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
Outdated
Show resolved
Hide resolved
To get started, you need to establish a connection between New Relic and your AWS services. Establishing the initial connection integrates New Relic into your AWS stack so you can access additional integrations for full visibility into your AWS environment. | ||
|
||
Here are options to get started: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akristen This table is a great call!
...ontent/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
Outdated
Show resolved
Hide resolved
|
||
## Amazon CloudWatch Metric streams and API polling [#api-polling] | ||
|
||
We strongly recommend that you use the CloudWatch Metric Streams integration as it directly connects with the metric streams repository that holds your AWS metric data. You may need our API Polling integrations to supplement AWS CloudWatch metric streams. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akristen strongly recommend this instead of....? Also, should we link to the CloudWatch integration doc here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little hazy on the details, but CloudWatch Metric Streams is an o11y mechanism for collecting metric data from AWS integrations. It replaces API polling in almost all cases, but there are some edge situations where API polling is necessary. I'll follow up with a SME about this too because the docs in general could use more clarity about this
...ontent/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
Outdated
Show resolved
Hide resolved
...ontent/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
Outdated
Show resolved
Hide resolved
|
||
Once you finish configuration, data from your AWS services reports directly to New Relic. AWS entities for many services are listed in our [entity explorer](/docs/new-relic-one/use-new-relic-one/ui-data/new-relic-one-entity-explorer). Metrics and events appear in [metrics and events](/docs/query-your-data/explore-query-data/browse-data/introduction-data-explorer/). AWS data is also visible in the infrastructure UI. | ||
* The [AWS CloudWatch Pricing page](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Metric-Streams.html)defines AWS CloudWatch metric streams pricing based on the number of metric updates. | ||
* We sometimes use AWS Kinesis Data Firehose as the delivery method from AWS to New Relic, so we recommend reviewing the [AWS Firehose pricing page](https://aws.amazon.com/kinesis/data-firehose/pricing/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akristen This is a little vague. As a reader, I think I'd like a little more context about when we (New Relic, I assume) use Firehose
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, this might be on an integration-by-integration basis. Once I find a SME, I'll ask them to clarify this statement
...ontent/docs/infrastructure/amazon-integrations/get-started/introduction-aws-integrations.mdx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akristen I flagged some minor things, but I think this is looking good. A definite improvement over the previous version!
reviewed and approved - Toni Chou |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
Made some updates to refresh the intro to AWS integration docs: