[Elastic-Agent] ECS compliant Elastic agent metadata sent to fleet #18006
[Elastic-Agent] ECS compliant Elastic agent metadata sent to fleet #18006michalpristas merged 4 commits intoelastic:masterfrom
Conversation
|
Pinging @elastic/ingest-management (Project:fleet) |
|
|
||
| // ECSMeta is a collection of agent related metadata in ECS compliant object form. | ||
| type ECSMeta struct { | ||
| Agent *AgentECSMeta `json:"agent"` |
There was a problem hiding this comment.
@ph Same question as on the Kibana issue: I remember we said we prefix this agent meta data by elastic. as there might be other agent metadata which correlates better with the ECS defition.
There was a problem hiding this comment.
The guidance is that no brand name (or proper names in general) should get into the schema. ECS should only contain concepts to which multiple technologies can map.
So there's no need to "reserve" the prefix elastic., IMO.
There was a problem hiding this comment.
Okay, my concern was teams using namespaces and possible clash because in the "elastic" namespace. But I do understand the no "brand name" but I wonder if is something we should have internally or a process.
💚 Build Succeeded
Expand to view the summary
Build stats
|
…lastic#18006) * use meta object * changelog * agent.* => elastic.agent.*
What does this PR do?
Fixes sending of metadata to fleet where instead of generated map we send an ECS compliant object.
Tested with elastic/kibana#64452
Why is it important?
To be fully ECS compliant
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.