Skip to content
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

Add APM cloud identification metadata to telemetry #70465

Closed
smith opened this issue Jul 1, 2020 · 1 comment · Fixed by #71008
Closed

Add APM cloud identification metadata to telemetry #70465

smith opened this issue Jul 1, 2020 · 1 comment · Fixed by #71008
Assignees
Labels
Team:APM All issues that need APM UI Team support v7.9.0

Comments

@smith
Copy link
Contributor

smith commented Jul 1, 2020

These keyword fields should be added to the mapping and collected in the telemetry tasks:

  • cloud.availability_zone
  • cloud.provider
  • cloud.region
@smith smith added Team:APM All issues that need APM UI Team support v7.9.0 [zube]: (7.9) Planned for release labels Jul 1, 2020
@smith smith self-assigned this Jul 1, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui (Team:apm)

smith added a commit to smith/kibana that referenced this issue Jul 7, 2020
Add cloud provider, region, and availability zone to the data telemetry mappings and queries.

Fixes elastic#70465
smith added a commit that referenced this issue Jul 7, 2020
Add cloud provider, region, and availability zone to the data telemetry mappings and queries.

Fixes #70465
smith added a commit to smith/kibana that referenced this issue Jul 7, 2020
Add cloud provider, region, and availability zone to the data telemetry mappings and queries.

Fixes elastic#70465
smith added a commit that referenced this issue Jul 8, 2020
Add cloud provider, region, and availability zone to the data telemetry mappings and queries.

Fixes #70465
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:APM All issues that need APM UI Team support v7.9.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants