[leandrodamascena]

Issue number: closes #8692

Summary

Changes

One short "CloudWatch Omni" subsection in each of the three core pages:

• Logger: Omni works on the telemetry already in CloudWatch, so nothing to configure. A table of the standard keys that matter for filtering and correlation (service, correlation_id, xray_trace_id, function keys), advice on flat key names for append_keys, and a tip to keep service consistent across Logger, Metrics and Tracer.
• Metrics: EMF becomes CloudWatch metrics and that is what Omni dashboards and alerts use; keep the service dimension and meaningful namespace/dimension names.
• Tracer: X-Ray traces reach Omni through Transaction Search; Omni's own path is OpenTelemetry, which Tracer does not emit, with a pointer to Feature request: OpenTelemetry Support #7003.

Why draft

I created a real Omni domain and space and ran telemetry queries against the default dataset, but the CloudWatch Logs from a test function never showed up in it during the hour I had, so I could not take screenshots or verify a query example end to end. The text sticks to what AWS documents (Omni operates on the same telemetry stored in CloudWatch) and to what Powertools emits. I'll add a query example and screenshots once I understand how log groups are onboarded into the dataset.

User experience

Docs only.

Checklist

• Meet tenets criteria
• Documentation updated

[powertools-for-aws-oss-automation]

No acknowledgement section found. Please make sure you used the template to open a PR and didn't remove the acknowledgment section. Check the template at .github/PULL_REQUEST_TEMPLATE.md#acknowledgment

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud