[Attack Discovery][Scheduling] Telemetry (#12008) #220998
Merged
+920
−461
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e40pud
added
release_note:skip
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
andrew-goldstein
approved these changes
May 20, 2025
There was a problem hiding this comment.
Thanks @e40pud for the additional telemetry, and for paring on the review!
# Conflicts: # x-pack/solutions/security/plugins/elastic_assistant/server/lib/attack_discovery/schedules/register_schedule/executor.ts
💚 Build Succeeded
Metrics [docs]
History
cc @e40pud |
|
Starting backport for target branches: 8.19 |
|
Example of the reported event for AD schedule 
|
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
May 21, 2025
) ## Summary Main ticket ([Internal link](elastic/security-team#12008)) These changes add attack discovery schedules telemetry similarly to existing manually generated attack discoveries added in this commit elastic@3c41972. ## NOTES The feature is hidden behind the feature flag (in `kibana.dev.yml`): ``` feature_flags.overrides: securitySolution.assistantAttackDiscoverySchedulingEnabled: true ``` (cherry picked from commit 94113be)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
May 21, 2025
…221142) # Backport This will backport the following commits from `main` to `8.19`: - [[Attack Discovery][Scheduling] Telemetry (#12008) (#220998)](#220998) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-05-21T15:35:46Z","message":"[Attack Discovery][Scheduling] Telemetry (#12008) (#220998)\n\n## Summary\n\nMain ticket ([Internal\nlink](https://github.com/elastic/security-team/issues/12008))\n\nThese changes add attack discovery schedules telemetry similarly to\nexisting manually generated attack discoveries added in this commit\nhttps://github.com//pull/184949/commits/3c419729337cf3fa9f1ff5ddb49a4ed07d102324.\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"94113be9f19c15412beee25fbac627fa07bf7d1a","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0"],"title":"[Attack Discovery][Scheduling] Telemetry (#12008)","number":220998,"url":"https://github.com/elastic/kibana/pull/220998","mergeCommit":{"message":"[Attack Discovery][Scheduling] Telemetry (#12008) (#220998)\n\n## Summary\n\nMain ticket ([Internal\nlink](https://github.com/elastic/security-team/issues/12008))\n\nThese changes add attack discovery schedules telemetry similarly to\nexisting manually generated attack discoveries added in this commit\nhttps://github.com//pull/184949/commits/3c419729337cf3fa9f1ff5ddb49a4ed07d102324.\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"94113be9f19c15412beee25fbac627fa07bf7d1a"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/220998","number":220998,"mergeCommit":{"message":"[Attack Discovery][Scheduling] Telemetry (#12008) (#220998)\n\n## Summary\n\nMain ticket ([Internal\nlink](https://github.com/elastic/security-team/issues/12008))\n\nThese changes add attack discovery schedules telemetry similarly to\nexisting manually generated attack discoveries added in this commit\nhttps://github.com//pull/184949/commits/3c419729337cf3fa9f1ff5ddb49a4ed07d102324.\n\n## NOTES\n\nThe feature is hidden behind the feature flag (in `kibana.dev.yml`):\n\n```\nfeature_flags.overrides:\n securitySolution.assistantAttackDiscoverySchedulingEnabled: true\n```","sha":"94113be9f19c15412beee25fbac627fa07bf7d1a"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <[email protected]>
akowalska622
pushed a commit
to akowalska622/kibana
that referenced
this pull request
May 29, 2025
) ## Summary Main ticket ([Internal link](elastic/security-team#12008)) These changes add attack discovery schedules telemetry similarly to existing manually generated attack discoveries added in this commit elastic@3c41972. ## NOTES The feature is hidden behind the feature flag (in `kibana.dev.yml`): ``` feature_flags.overrides: securitySolution.assistantAttackDiscoverySchedulingEnabled: true ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Main ticket (Internal link)
These changes add attack discovery schedules telemetry similarly to existing manually generated attack discoveries added in this commit 3c41972.
NOTES
The feature is hidden behind the feature flag (in
kibana.dev.yml):