Description of the issue
There are multiple use cases where knowing the cloud provider would help our users and ourselves:
- App ops knowing where the applications are hosted
- Linking across apm, logs and metrics
- Elastic - monitoring where customers are deploying their applications to prioritize installation, integration and coverage work
Agents would need to report following optional fields (based on ECS):
- cloud.availability_zone
- cloud.account.id
- cloud.account.name
- cloud.instance.id
- cloud.instance.name
- cloud.machine.type
- cloud.project.id
- cloud.project.name
- cloud.provider
- cloud.region
APM server can currently report this data for co-located applications (it needs to be installed on the same host).
This is code which collects cloud metadata:
https://github.com/elastic/beats/tree/0ef472268ea41881f81accabe2af6cfb72eef682/libbeat/processors/add_cloud_metadata
Agent spec PR: #290
Agent Issues
Description of the issue
There are multiple use cases where knowing the cloud provider would help our users and ourselves:
Agents would need to report following optional fields (based on ECS):
APM server can currently report this data for co-located applications (it needs to be installed on the same host).
This is code which collects cloud metadata:
https://github.com/elastic/beats/tree/0ef472268ea41881f81accabe2af6cfb72eef682/libbeat/processors/add_cloud_metadata
Agent spec PR: #290
Agent Issues