-
Notifications
You must be signed in to change notification settings - Fork 458
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
No meta info for groups #1091
Comments
Pinging @elastic/integrations (Team:Integrations) |
I think this can be handled with semantic validation rules. EDIT: I'm going with semantic rules. |
So, is the issue that we don't want |
Yes.
It's up to you. You can start fixing the system package if you know all these places. Otherwise please wait until the PR for semantic validation is merged, so it will detect all these places. |
@fearful-symmetry What I'm trying to understand on my end is: Do we need the units? I assume we put them there for a reason? |
Side note: the check I proposed in elastic/package-spec#183 forbids all unit/metric types for group fields.
I assume that was a typo, right? |
@ruflin most of those fields weren't added by me if I remember correctly, so I really can't say. It looks like @exekias added most of the ones to |
Are we in agreement we don't need this and we should get rid of it? |
Agreed. Unless there's a blocker, I'm going to wait for the validation PR before trying to clear things out. |
@fearful-symmetry I will try to update it in the elastic/integrations as well. EDIT: PR: #1114 |
In elastic/kibana#82273 the issue was raised that units are set on a group object: https://github.com/elastic/integrations/blob/master/packages/system/data_stream/fsstat/fields/fields.yml#L15-L16
First, I think this should not happen and we should fix the package. @fearful-symmetry I guess this falls on your plate?
Second, we should have a discussion if we should validate this also in the package spec? @mtojek @ycombinator
Last, to support also older packages, do we need a workaround in Kibana (@Zacqary )?
The text was updated successfully, but these errors were encountered: