[DOCS-13133] Expand AWS integration troubleshooting with high-frequency support topics#35349
[DOCS-13133] Expand AWS integration troubleshooting with high-frequency support topics#35349
Conversation
…cy support topics Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: be944f11c3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Some AWS CloudWatch metrics are emitted once per dimension combination, which can produce values that appear inflated when aggregated in Datadog. For example, the `aws.elb.healthy_host_count` metric is reported separately for each Availability Zone and target group. Summing this metric across all dimensions results in a total that is higher than the actual number of healthy hosts, because hosts in multiple zones are counted multiple times. | ||
|
|
||
| To avoid this, use the `_deduped` metric variants when available (for example, `aws.elb.healthy_host_count_deduped`), or scope your query to a specific Availability Zone or target group. |
There was a problem hiding this comment.
This new troubleshooting example mixes ELB concepts: aws.elb.healthy_host_count is the Classic ELB metric discussed later in this same page, and that section explains the overcount in terms of Availability Zones (not target groups). Telling users to scope by target group can send them looking for a dimension that does not exist for this metric, which makes the discrepancy workflow fail for the exact case this section is trying to fix.
Useful? React with 👍 / 👎.
Preview links (active after the
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Applied — fixed per-dimension section to correctly describe |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e5e38c2314
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 4. **Check whether the service requires additional enablement.** Some AWS services do not emit metrics to CloudWatch by default. For example: | ||
| - Amazon RDS requires [Enhanced Monitoring][18] to be enabled in the RDS console for OS-level metrics. | ||
| - Amazon S3 Storage Lens metrics require Storage Lens to be configured in the S3 console. | ||
| - AWS billing metrics require [Cost Explorer][19] to be enabled in the AWS Billing console. |
There was a problem hiding this comment.
This troubleshooting step gives the wrong prerequisite for missing aws.billing.* metrics: enabling Cost Explorer is not what turns on CloudWatch billing metrics, and our own billing guide instead requires enabling billing metrics in AWS plus enabling Billing collection in the integration (content/en/integrations/guide/monitor-your-aws-billing-details.md, steps 1–2). Users following this checklist can remain blocked because Cost Explorer alone does not make aws.billing.estimated_charges appear.
Useful? React with 👍 / 👎.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Re: billing metrics prerequisite — Applied, replaced Cost Explorer reference with the actual billing prerequisites (enable |
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 participant
What does this PR do? What is the motivation?
Expands the AWS integration troubleshooting page with new sections addressing the most common support ticket themes identified from analysis of 100+ escalated AWS integration tickets. Additions:
_dedupedvariantsMerge instructions
Merge readiness: