[ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
[ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
:robot: Jobs for this PR can be triggered through checkboxes. :construction:
:information_source: To trigger the CI, please tick the checkbox below :point_down:
- [ ] Click to trigger **kibana-pull-request** for this PR!
- [ ] Click to trigger **kibana-deploy-project-from-pr** for this PR!
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Otel
ECS
Additional test with synthtrace
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breaking
label should be applied in these situations.release_note:*
label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.