Fix rds metricset cpu.total.pct#28456
Conversation
|
This pull request does not have a backport label. Could you fix it @kaiyan-sheng? 🙏
NOTE: |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
Pinging @elastic/integrations (Team:Integrations) |
| } | ||
|
|
||
| for _, event := range events { | ||
| cpuValue, err := event.RootFields.GetValue("aws.rds.metrics.CPUUtilization.avg") |
There was a problem hiding this comment.
If I understood correctly, this key gets mapped to aws.rds.cpu.total.pct in the final event. Where does this happen?
There was a problem hiding this comment.
Thanks for the review! Im using the rename processor in aws module: https://github.com/elastic/beats/blob/master/x-pack/metricbeat/module/aws/rds/manifest.yml#L85
(cherry picked from commit a98cacd)
(cherry picked from commit a98cacd)
What does this PR do?
This PR is to fix RDS metricset
aws.rds.cpu.total.pctby dividing the original value by 100. In the screenshot below, it also shows the value for CPU usage, the ARN are also different collected from different instances.Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues
Screenshots