-
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
[Security Solution][Detection Engine] deprecates signals migration APIs #198173
Draft
vitaliidm
wants to merge
38
commits into
elastic:main
Choose a base branch
from
vitaliidm:de_8_17/deprecate-signals-migration
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
[Security Solution][Detection Engine] deprecates signals migration APIs #198173
vitaliidm
wants to merge
38
commits into
elastic:main
from
vitaliidm:de_8_17/deprecate-signals-migration
Conversation
This file contains 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
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
vitaliidm
added
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Team:Detection Engine
Security Solution Detection Engine Area
release_note:deprecation
backport:prev-minor
Backport to (8.x) the previous minor version (i.e. one version back from main)
labels
Oct 29, 2024
…com/vitaliidm/kibana into de_8_17/deprecate-signals-migration
…com/vitaliidm/kibana into de_8_17/deprecate-signals-migration
…com/vitaliidm/kibana into de_8_17/deprecate-signals-migration
# Conflicts: # oas_docs/output/kibana.yaml
…com/vitaliidm/kibana into de_8_17/deprecate-signals-migration
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Unknown metric groupsAPI count
ESLint disabled line counts
Total ESLint disabled count
History
cc @vitaliidm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:prev-minor
Backport to (8.x) the previous minor version (i.e. one version back from main)
release_note:deprecation
Team:Detection Engine
Security Solution Detection Engine Area
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
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
.alerts-*
indices, listing them as outdated.tasks
indexHow to test
How to create legacy siem index?
run script that used for FTR tests
These would create legacy siem indices. But be aware, it might break Kibana .alerts indices creation. But sufficient for testing
How to test deprecated APIs?
Kibana Upgrade list of deprecations
How to test deprecated feature?
Kibana Upgrade feature deprecation flyout
How to test snapshot telemetry
Snapshot
For snapshot telemetry use API call
OR
Check snapshots in Kibana adv settings -> Global Settings Tab -> Usage collection section -> Click on cluster data example link -> Check
legacy_siem_signals
fields in flyoutSnapshot telemetry