[Fleet] Install final pipeline#100973
Conversation
|
Pinging @elastic/fleet (Team:Fleet) |
x-pack/plugins/fleet/server/services/epm/elasticsearch/template/template.ts
Outdated
Show resolved
Hide resolved
|
Just a small question/comment on this approach. Does this mean that final_pipeline will be set for all indices used by packages/integrations? |
Yes with that PR the final_pipeline will be used for all indices, user will still be able to define a pipeline to overwrite module fields, but not a final_pipeline |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @nchaulet |
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…2805) This updates the Fleet final pipeline added in #100973 to match the specification of `event.agent_id_status` field as defined in ECS. The field was added to ECS in elastic/ecs#1454. Basically the values of the field were simplified from what was originally proposed and implemented.
…stic#102805) This updates the Fleet final pipeline added in elastic#100973 to match the specification of `event.agent_id_status` field as defined in ECS. The field was added to ECS in elastic/ecs#1454. Basically the values of the field were simplified from what was originally proposed and implemented.
…2805) (#102832) This updates the Fleet final pipeline added in #100973 to match the specification of `event.agent_id_status` field as defined in ECS. The field was added to ECS in elastic/ecs#1454. Basically the values of the field were simplified from what was originally proposed and implemented. Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
Summary
Resolve #97181
To ensure the agent do not tamper agent id when sending event, we are going to use a final pipeline that check the agent id against the agent id contained in the api key.
For that:
.fleet_final_pipelineduring the fleet setupNot done in that PR:
Decisions made in that PR:
What to test?
every event ingested with Elastic agent should have the field
event.agent_id_status.