-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Add support for new mapping parameters for metrics defined in packages #115621
Labels
QA:Validated
Issue has been validated by QA
Team:Fleet
Team label for Observability Data Collection Fleet team
v8.2.0
Comments
jsoriano
added
the
Team:Fleet
Team label for Observability Data Collection Fleet team
label
Oct 19, 2021
Pinging @elastic/fleet (Team:Fleet) |
1 task
2 tasks
Copying manual test case here from 8.2 test plan:
|
Hi @juliaElastic Steps followed:
Build details: Hence marking this as QA:Validated. Thanks |
amolnater-qasource
added
QA:Validated
Issue has been validated by QA
and removed
QA:Needs Validation
Issue needs to be validated by QA
labels
Jun 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
QA:Validated
Issue has been validated by QA
Team:Fleet
Team label for Observability Data Collection Fleet team
v8.2.0
Describe the feature:
There were previous efforts to add metrics information for time series in meta (see #82273). Since then, new mapping parameters for metrics have been added (elastic/elasticsearch#74014), making metrics and dimensions first-class citizens.
Add the new mapping parameters to the templates installed for packages.
Following the example in #82273, this field definition:
Should be translated to:
unit
can continue in meta, this value would be used by convention only for formatting and there is no setting defined at the mapping level.Describe a specific use case for the feature:
Use the mapping settings available in elasticsearch for time series data, what will allow to leverage features implemented for this data.
The text was updated successfully, but these errors were encountered: