I like the concept of meta.cloud.* and would like to add something like ec2 tags to that, nested under meta.cloud.tags.* for everything on that instance.
Alternatively, it'd be nice to be able to whitelist environment details, perhaps meta.env.ENV_VAR_NAME=$value.
Does support like this exist in metricbeat (or beats lib?).
Currently I'm sending metricbeat events to logstash, and adding the context there, but it'd be nice to only manage the single metricbeat instance.
So I finally got around to trying this, and I was able to successfully set a field like meta.tags.*
However I'd like to nest it with the cloud block, at meta.cloud.tags.*. It seems like the add cloud processor overwrites any fields that might already be there. Is that the case? If so, is there any way to achieve that?
Awesome, thanks @ruflin for the link. I opened a ticket to get a conversation started around standardizing cloud tags/labels in future releases (ref https://github.com/elastic/ecs/issues/384).
For now, I'll keep them where they are since neither is officially a convention yet.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.