Standardize additional cloud metadata

[graphaelli]

Adds:

• account.name
• project.id
• project.name

[webmat]

Makes a lot of sense to me, thanks @graphaelli! Do you know if this has impact on some of the infra UIs?

I'd also like to get the opinion from someone familiar with the collection of this cloud meta-data in Beats. @urso could you plz loop in the best person to chime in on this?

[graphaelli]

This does not impact Infra UIs - project.id is already supplied by the add_cloud_metadata processor in beats, account.id is supplied the metricbeat aws module, project.name is new.

[urso]

+1 on adding project/account information to the cloud namespace.

@kvch @kaiyan-sheng @narph You've been working with Cloud (AWS, Azure, GCP) to some extend. Any other meta-data in mind we would like to add?

[webmat]

Thanks @urso. What I'm looking for here is actually any concerns from getting this data from people that know about the implementation of the meta data collector in Beats.

Although if additional fields could be useful, additional PRs are always welcome :-)

[kvch]

@webmat It would be great to have appropriate field names for such services. For example, I use resource.* fields to identify and describe the states of the AWS/GCP resources from the event. But I understand, it is outside of the scope of this PR.

[webmat]

@urso @kvch Thanks for the feedback. So there's no issues in getting this information from the metadata collector?

[urso]

I don't think so.

[webmat]

LGTM

@graphaelli could you add a changelog entry, we'll merge after that.

[webmat]

Oh wait, getting carried away. Did you want to wait on @simitt's review before I merge, Gil?

[graphaelli]

@webmat Changelog pushed, @simitt is on board