-
Notifications
You must be signed in to change notification settings - Fork 70
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
To make labels exploitable in Kibana #137
Comments
IMO it's a good idea 😄 |
We did almost the same in the metricbeat docker module: elastic/beats#3024 |
Good idea! Can it be incorporated into a new Docker image with a tag indicating it is a breaking change? |
If you want to test it I pushed a docker image of my version here : https://hub.docker.com/r/fmeriot/dockbeat-labels/ I use it as a base image like this :
Don't forget the "v1" version |
I would be very interested in this too ! |
The docker module is now also available in the metricbeat 5.1 release with the label refactoring. |
Any update on this? It would be very useful for our Grafana dashboards. Apparently related: #133 |
@alangibson The docker module in metricbeat has this change. The docker module is dockbeat as a module in metricbeat and was contributed from this code base. |
Hi,
I'am using Rancher to orchestrate my containers deployed on many hosts. I choosed Dockbeat as a very lightweight solution to log system metrics in elasticsearch. Thank you for your nice job!
Some of information very usefull to me in the logged data is some rancher labels like "stack name" or "container id". But the way they are stored in ElasticSearch makes very difficult to exploit them correctly in Kibana. Array of objects, even indexed with a nested type index, is'nt exploitable.
So, I modified a little bit the buildLabelArray function in /event/generator.go file like this :
Now, I have a flat map of labels like this :
Thanks to this I can have aggregated visualizations per Stack in my Dashboards.
Will you consider to "flatten" the labels array in future versions ?
Thank you for your work. That helps us a lot.
The text was updated successfully, but these errors were encountered: