-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate Cloud Defend Telemetry #212496
Deprecate Cloud Defend Telemetry #212496
Conversation
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
💚 Build Succeeded
Metrics [docs]History
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! IIUC these fields will no longer be shipped / ingested.
Is there any impact on telemetry-cluster side? I'm thinking:
- Mapped fields that won't be populated anymore, is there a way to clean those up?
- If there are any consumers of these fields (dashboards, alerts, slos?), will they error?
Thanks for the review @gsoldevila.
|
Starting backport for target branches: 9.0 |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
# Backport This will backport the following commits from `main` to `9.0`: - [Deprecate Cloud Defend Telemetry](#212496) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ido Cohen","email":"90558359+CohenIdo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-03T10:28:37Z","message":"Deprecate Cloud Defend Telemetry","sha":"58e25b564e6b80816b8c8800e109021b1d30fc5a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud Security","backport:prev-minor","v9.1.0"],"title":"Deprecate Cloud Defend Telemetry","number":212496,"url":"https://github.com/elastic/kibana/pull/212496","mergeCommit":{"message":"Deprecate Cloud Defend Telemetry","sha":"58e25b564e6b80816b8c8800e109021b1d30fc5a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212496","number":212496,"mergeCommit":{"message":"Deprecate Cloud Defend Telemetry","sha":"58e25b564e6b80816b8c8800e109021b1d30fc5a"}}]}] BACKPORT--> Co-authored-by: Ido Cohen <90558359+CohenIdo@users.noreply.github.com>
solves:
Summary
As part of the Cloud Defend deprecation, this PR specifically deprecates Cloud Defend telemetry to address the error log issue.
How to test
Before this change, telemetry iteration—whether triggered by the Task Manager background task or manually via the API—generated an error log.
With this update, the error log no longer appear.