-
Notifications
You must be signed in to change notification settings - Fork 524
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
intake: add cloud.service.name to metadata #4626
Conversation
closes 4625
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
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.
Maybe add the field to docs/data/elasticsearch/generated
?
Also, it would be great to create some section in the README with a link to this PR as a reference implementation of how to add a field to the intake (things have changed...)
@@ -96,6 +96,7 @@ Traces are written to `traces-apm.*` indices. | |||
|cloud.project.name|Cloud project name|keyword| ![](https://doc-icons.s3.us-east-2.amazonaws.com/icon-yes.png) | | |||
|cloud.provider|Cloud provider name|keyword| ![](https://doc-icons.s3.us-east-2.amazonaws.com/icon-yes.png) | | |||
|cloud.region|Cloud region name|keyword| ![](https://doc-icons.s3.us-east-2.amazonaws.com/icon-yes.png) | | |||
|cloud.service.name|Cloud service name, intended to distinguish services running on different platforms within a provider.|keyword| ![](https://doc-icons.s3.us-east-2.amazonaws.com/icon-no.png) | |
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.
this is wrong, isn't it? I think we need to update the ECS version
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.
It hasn't been released, so for now this is true.
Co-authored-by: Andrew Wilkins <[email protected]>
@jalvz good idea; I updated the description to contain a How to add a new Intake API Field and index it section and linked to it from the updated Contribution guid. |
When running |
@simitt yes, that's fine - thanks and sorry. |
closes elastic#4625 # Conflicts: # changelogs/head.asciidoc # include/fields.go
closes #4625 # Conflicts: # changelogs/head.asciidoc # include/fields.go Co-authored-by: Silvia Mitter <[email protected]>
The go agent doesn't let you trick into thinking is running on cloud, so I just sent handcrafted payloads to apm-server. Data is ingested as expected |
Motivation/summary
This PR adds
cloud.service.name
to the set of available cloud information in themetadata
. The field was introduced with elastic/ecs#1204.Checklist
For functional changes, consider:
How to test these changes
Send a
metadata.cloud.service.name
information along with event data and check that it is indexed askeyword
forerror,transaction,span,metric
events.Related issues
closes 4625
How to add a new Intake API Field and index it
approval
files by runninggo test ./...
andmake check-approvals
make update
and ensure that the Intake Spec, the generated model logic and the apmpackage and the generated fields are properly updated