-
Notifications
You must be signed in to change notification settings - Fork 419
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
Fix the actual cloud.provider example. #348
Conversation
@@ -222,7 +222,7 @@ | |||
fields: | |||
- name: provider | |||
level: extended | |||
example: ec2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The implementation in Beats populates this with ec2
. It would be helpful to have a list of names in ECS to use for popular providers. Ironically one of the providers is using ecs
. https://github.com/elastic/beats/blob/master/libbeat/docs/processors-using.asciidoc#add-cloud-metadata
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the document example is better using "aws" but there could be a case for using service.name
in cloud-provider relevant events to capture the service such as "ec2." Agree we could expand the list of examples to eventually become a set of defined names.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed on the enums. However they will come after 1.0 :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR elastic#330 only fixed the text in the description :-)
5550f71
to
91f921f
Compare
PR #330 only fixed the text in the description :-)