intake: add cloud.service.name to metadata#4626
Conversation
closes 4625
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Steps errors
Expand to view the steps failures
|
jalvz
left a comment
There was a problem hiding this comment.
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...)
| |cloud.project.name|Cloud project name|keyword|  | | ||
| |cloud.provider|Cloud provider name|keyword|  | | ||
| |cloud.region|Cloud region name|keyword|  | | ||
| |cloud.service.name|Cloud service name, intended to distinguish services running on different platforms within a provider.|keyword|  | |
There was a problem hiding this comment.
this is wrong, isn't it? I think we need to update the ECS version
There was a problem hiding this comment.
It hasn't been released, so for now this is true.
Co-authored-by: Andrew Wilkins <axwalk@gmail.com>
|
@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
|
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.nameto 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.nameinformation along with event data and check that it is indexed askeywordforerror,transaction,span,metricevents.Related issues
closes 4625
How to add a new Intake API Field and index it
approvalfiles by runninggo test ./...andmake check-approvalsmake updateand ensure that the Intake Spec, the generated model logic and the apmpackage and the generated fields are properly updated