Skip to content

[AWS] Add metric type to Usage, DynamoDB and ELB data streams#6296

Merged
constanca-m merged 4 commits intoelastic:mainfrom
constanca-m:aws-add-metric-usage-elb-dynamodb
Jun 6, 2023
Merged

[AWS] Add metric type to Usage, DynamoDB and ELB data streams#6296
constanca-m merged 4 commits intoelastic:mainfrom
constanca-m:aws-add-metric-usage-elb-dynamodb

Conversation

@constanca-m
Copy link
Copy Markdown
Contributor

What does this PR do?

Add metric type to Usage, DynamoDB and ELB data streams.

All metric fields were set as of having type gauge. Even though some fields seem to be counters, they are only cumulative over a very specific window of time - for example, 1 minute or 5 minutes. This causes a value to be incrementing and decrementing over time, instead of staying equal or higher to the previous value, which would be necessary if we were facing a counter field.

As an example, we have ConsumedReadCapacityUnits.sum (by definition, "The number of read capacity units consumed over the specified time period"), that would look like this for each table:

Screenshot from 2023-05-23 16-06-06

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

Refer to #6227.

Related issues

Relates to #6227.

Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
@constanca-m constanca-m requested a review from a team as a code owner May 23, 2023 15:14
@constanca-m constanca-m self-assigned this May 23, 2023
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
@elasticmachine
Copy link
Copy Markdown

elasticmachine commented May 23, 2023

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-06-06T06:55:02.436+0000

  • Duration: 46 min 10 sec

Test stats 🧪

Test Results
Failed 0
Passed 190
Skipped 4
Total 194

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link
Copy Markdown

elasticmachine commented May 23, 2023

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (15/15) 💚
Files 93.75% (15/16) 👎 -6.25
Classes 93.75% (15/16) 👎 -6.25
Methods 85.921% (238/277) 👎 -11.138
Lines 85.925% (7387/8597) 👎 -9.305
Conditionals 100.0% (0/0) 💚

@@ -1,4 +1,9 @@
# newer versions go on top
- version: "1.36.9"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: in #6365 we bumped minor version, here only patch one
why the difference? :)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1.36.x are all related to TSDB, unlike what happened in #6365. That is why I changed the way I was bumping the version.

@constanca-m
Copy link
Copy Markdown
Contributor Author

/test

@constanca-m constanca-m merged commit e4b4ac9 into elastic:main Jun 6, 2023
@constanca-m constanca-m deleted the aws-add-metric-usage-elb-dynamodb branch June 6, 2023 07:59
@elasticmachine
Copy link
Copy Markdown

Package aws - 1.40.3 containing this change is available at https://epr.elastic.co/search?package=aws

sodhikirti07 pushed a commit that referenced this pull request Jun 15, 2023
* Add metric type.

Signed-off-by: constanca-m <constanca.manteigas@elastic.co>

* Update changelog.

Signed-off-by: constanca-m <constanca.manteigas@elastic.co>

---------

Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants