-
Notifications
You must be signed in to change notification settings - Fork 474
[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
Conversation
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
🌐 Coverage report
|
@@ -20,43 +20,56 @@ | |||
type: group | |||
fields: | |||
- name: Invocations.avg |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
/test |
Package aws - 1.36.0 containing this change is available at https://epr.elastic.co/search?package=aws |
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
changelog.yml
file.How to test this PR locally
Refer to #5970
Related issues