[aws_<service>_otel] Improvements#19683
Conversation
and add them to ecs/rds/sqs charts
TL;DRBuildkite failed before tests ran because the post-checkout hook cannot merge the PR branch with current Remediation
Investigation detailsRoot CauseThis is a configuration/mergeability failure during Buildkite checkout, not a source test failure. The failing job switched to current The conflict is explained by the package metadata state:
Evidence
Verification
Follow-upLater Buildkite statuses on the PR show the same pipeline upload step is still failing on newer commits, so resolving the merge conflicts is the gating action before CI can exercise tests. What is this? | From workflow: PR Buildkite Detective Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. |
…ations into aws-otel-improvements
Make the six AWS OpenTelemetry content package READMEs (ec2, ecs, rds, sqs, lambda, elb_metrics) consistent: - Reference the aws_cloudwatch_input_otel input package as the data collection source in the "content only" paragraph. - Pluralize the "Alerting Rule Templates" heading to match the Dashboards and SLO Templates headings. - Fix a duplicated phrase in the aws_elb_metrics_otel intro line. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
✅ All changelog entries have the correct PR link. |
💚 Build Succeeded
History
|
Proposed commit message
This PR improves aws otel dashboards design and ESQL queries.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots