-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[BUG] add_cloud_metadata does not populate host.type correctly #10968
Comments
What we can do is trim the leading parts of those values for the GCE provider. |
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Feb 28, 2019
This removes the project info from the `cloud.machine.type` and `cloud.availability_zone` fields that are added to the add_cloud_metadata processor for Google Compute Engine (GCE). Fixes elastic#10968
andrewkroh
added a commit
that referenced
this issue
Mar 1, 2019
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Mar 3, 2019
This removes the project info from the cloud.machine.type and cloud.availability_zone fields that are added to the add_cloud_metadata processor for Google Compute Engine (GCE). Fixes elastic#10968, elastic#10775 (docs) (cherry picked from commit f527cd5)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On GCE, the
add_cloud_metadata
processor populateshost.type
with a value such as thisprojects/NNN/machineTypes/n1-standard-2
In ECS,
host.type
is intended to be populated with short name liken1-standard-2
. Not an account-specific or a fully qualified (e.g. regions / dc / resource) URI.Could we adjust the processor to contain the short value?
The text was updated successfully, but these errors were encountered: