Skip to content

[AWS][Lambda] Add metric type to lambda fields #6045

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 17, 2023

Conversation

constanca-m
Copy link
Contributor

What does this PR do?

Add field metric type to the Lambda data stream for TSDB support.

Details

All metrics used in this data stream are computed based on aggregations: average, max and sum. Even though max and sum might seem as counters, these are computed at a given moment in time and are not cumulative values over time. All metrics go up and down and for that, all of them are gauges.

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 #5970

Related issues

Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
@constanca-m constanca-m requested a review from a team as a code owner May 1, 2023 15:47
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
@elasticmachine
Copy link

elasticmachine commented May 1, 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-05-17T07:56:38.199+0000

  • Duration: 58 min 52 sec

Test stats 🧪

Test Results
Failed 0
Passed 188
Skipped 4
Total 192

🤖 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

elasticmachine commented May 1, 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 86.131% (236/274) 👎 -8.055
Lines 85.925% (7387/8597) 👎 -14.075
Conditionals 100.0% (0/0) 💚

@@ -20,43 +20,56 @@
type: group
fields:
- name: Invocations.avg
Copy link
Contributor

Choose a reason for hiding this comment

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

@elastic/obs-cloud-monitoring just wondering why all datastreams are missing unit configuration, somehow I thought it is important to add it

Copy link
Contributor

Choose a reason for hiding this comment

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

We should definitely add the unit field.

@constanca-m
Copy link
Contributor Author

constanca-m commented May 17, 2023

/test

@constanca-m constanca-m merged commit be711bd into elastic:main May 17, 2023
@constanca-m constanca-m deleted the lambda-add-metric-type branch May 17, 2023 08:59
@elasticmachine
Copy link

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

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