[Fleet] Fix dataset suffix in permissions for OTel policies#266101
[Fleet] Fix dataset suffix in permissions for OTel policies#266101jsoriano merged 2 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/fleet (Team:Fleet) |
ApprovabilityVerdict: Needs human review This PR modifies how agent index permissions are computed for OTel policies by appending You can customize Macroscope's approvability policy. Learn more. |
teresaromero
left a comment
There was a problem hiding this comment.
tested integrated with elastic-package 👍🏻
Yes, the elasticsearch exporter in the OTel collector appends |
💚 Build Succeeded
Metrics [docs]
History
cc @jsoriano |
|
Starting backport for target branches: 9.4 https://github.com/elastic/kibana/actions/runs/25070561455 |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…66101) (#266206) # Backport This will backport the following commits from `main` to `9.4`: - [[Fleet] Fix dataset suffix in permissions for OTel policies (#266101)](#266101) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jaime Soriano Pastor","email":"jaime.soriano@elastic.co"},"sourceCommit":{"committedDate":"2026-04-28T18:27:33Z","message":"[Fleet] Fix dataset suffix in permissions for OTel policies (#266101)\n\nPermissions added for data streams in OTel policies should include the\n.otel suffix in the dataset. Without this the permissions don't match\nand ingestion fails.\n\nThis is an issue with integration packages without `dynamic_dataset:\ntrue`. In the case of input packages this is not an issue because this\nparameter is always true.","sha":"283d848b4e9f67b4b4354f51214c699c484a8a04","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:version","v9.4.0","v9.5.0"],"title":"[Fleet] Fix dataset suffix in permissions for OTel policies","number":266101,"url":"https://github.com/elastic/kibana/pull/266101","mergeCommit":{"message":"[Fleet] Fix dataset suffix in permissions for OTel policies (#266101)\n\nPermissions added for data streams in OTel policies should include the\n.otel suffix in the dataset. Without this the permissions don't match\nand ingestion fails.\n\nThis is an issue with integration packages without `dynamic_dataset:\ntrue`. In the case of input packages this is not an issue because this\nparameter is always true.","sha":"283d848b4e9f67b4b4354f51214c699c484a8a04"}},"sourceBranch":"main","suggestedTargetBranches":["9.4"],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/266101","number":266101,"mergeCommit":{"message":"[Fleet] Fix dataset suffix in permissions for OTel policies (#266101)\n\nPermissions added for data streams in OTel policies should include the\n.otel suffix in the dataset. Without this the permissions don't match\nand ingestion fails.\n\nThis is an issue with integration packages without `dynamic_dataset:\ntrue`. In the case of input packages this is not an issue because this\nparameter is always true.","sha":"283d848b4e9f67b4b4354f51214c699c484a8a04"}}]}] BACKPORT--> Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
Summary
Permissions added for data streams in OTel policies should include the .otel suffix in the dataset. Without this the permissions don't match and ingestion fails.
This is an issue with integration packages without
dynamic_dataset: true. In the case of input packages this is not an issue because this parameter is always true.Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify 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.