-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Agent] Support labels dedot in k8s provider #27019
Comments
Pinging @elastic/integrations (Team:Integrations) |
Regarding the pros/cons of Speaking of this, @exekias @jsoriano do you think it is a good time now to consider using It is true that currently we don't use any labels in our dashboards/visualisations but maybe users want to create custom visualisation based on labels, so I think this is something quite important for us in order to adopt this type. |
Note that this is tightly coupled with the implementation of #24495. If we aim to use the same interfaces/libs (see the draft PR linked to #24495) with Beats in order to generate metadata then the dettoting comes along:
If we conclude to use
|
I don't think Agent is defining these anywhere, it relies on default |
At the moment some common agent fields, as the ones for cloud or containers, are defined on each integration in the
Yes, this would be the long-term solution. |
It seems that even if the
In this I would suggest to move it forward using the old dedot approach we had in Beats and try to move to @mukeshelastic @akshay-saraswat it would be nice if we could have an estimation about 1, and maybe check again with Kibana folks what is the status and if they plan to work on this soon. |
Closed by #27691 |
We need to support label's dedoting or use
flattened
type as proposed at #26801 (comment). We need to verify which option works best for us so the scope of this issue is to investigate the option offlattened
and evaluate if it could be used instead of dedoting the labels (and annotations) as it was the case in Beats.cc: @MichaelKatsoulis @akshay-saraswat @exekias
The text was updated successfully, but these errors were encountered: