-
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] Rename old xpack.siem kibana config to xpack.securitySolution #69874
Conversation
Pinging @elastic/siem (Team:SIEM) |
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.
Checked out locally and tested with legacy xpack.siem.*
configuration -- verified below deprecation warning, and also that the feature worked as expected. Also verified functionality using the new configuration xpack.securitySolution.*
as well. LGTM! Thanks @XavierM & @joshdover 🙂
Note: I did see three occurrences of the deprecation warning during startup -- not sure if this is expected or perhaps a result of having a deeper logging level?
log [20:58:03.999] [warning][config][deprecation] "xpack.siem.signalsIndex" is deprecated and has been replaced by "xpack.securitySolution.signalsIndex"
server log [21:00:57.053] [warning][config][deprecation] "xpack.siem.signalsIndex" is deprecated and has been replaced by "xpack.securitySolution.signalsIndex"
optmzr log [21:00:57.202] [warning][config][deprecation] "xpack.siem.signalsIndex" is deprecated and has been replaced by "xpack.securitySolution.signalsIndex"
@elasticmachine merge upstream |
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
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.
Great, glad we caught this early enough :)
These are only in development where we have multiple processes running. Should not see this in production builds. |
Have we updated any related documentation? |
@benskelker can you make sure we get the doc updated |
* master: (90 commits) [Encrypted Saved Objects] Adds support for migrations in ESO (elastic#69513) [SIEM] Replace WithSource with useWithSource hook (elastic#68722) [Endpoint]EMT-451: add ability to filter endpoint metadata based on presence of unenrolled events (elastic#69708) rename old siem kibana config to securitySolution (elastic#69874) Remove unused Resolver code (elastic#69914) [Observability] Fixing dynamic return type based on the appName (elastic#69894) [SECURITY SOLUTION][INGEST] Task/endpoint list tests (elastic#69419) Fixes special clicks and 3rd party icon sizes in nav (elastic#69767) [APM] Catch annotations index permission error and log warning (elastic#69881) [Endpoint][Ingest Manager] minor code cleanup (elastic#69844) [Logs UI] Logs ui context menu (elastic#69915) Index pattern serialize and de-serialize (elastic#68844) [QA] Unskip functional tests (elastic#69760) [SIEM][Detection Engine] - Update DE to work with new exceptions schema (elastic#69715) Fixes elastic#69639: Ignore url.url fields above 2048 characters (elastic#69863) PR: Provide limit warnings to user when API limits are reached. (elastic#69590) [Maps] Remove broken button (elastic#69853) Makes usage collection methods available on start (elastic#69836) [SIEM][CASE] Improve Jira's labelling (elastic#69892) [Logs UI] Access ML via the programmatic plugin API (elastic#68905) ...
Co-authored-by: Elastic Machine <[email protected]>
Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* master: [Encrypted Saved Objects] Adds support for migrations in ESO (elastic#69513) [SIEM] Replace WithSource with useWithSource hook (elastic#68722) [Endpoint]EMT-451: add ability to filter endpoint metadata based on presence of unenrolled events (elastic#69708) rename old siem kibana config to securitySolution (elastic#69874) Remove unused Resolver code (elastic#69914) [Observability] Fixing dynamic return type based on the appName (elastic#69894) [SECURITY SOLUTION][INGEST] Task/endpoint list tests (elastic#69419) Fixes special clicks and 3rd party icon sizes in nav (elastic#69767) [APM] Catch annotations index permission error and log warning (elastic#69881) [Endpoint][Ingest Manager] minor code cleanup (elastic#69844) [Logs UI] Logs ui context menu (elastic#69915) Index pattern serialize and de-serialize (elastic#68844)
Pinging @elastic/security-solution (Team: SecuritySolution) |
Summary
Thanks for @joshdover insomnia ;) but I think it is most related to his work ethics. Anyway, He just saved us from a big problem here.
This PR is to rename our old property in kibana config file like
xpack.siem.enabled
toxpack.securitySolution.enabled
.To test this PR, just add a property in your
kibana.dev.config
likexpack.siem.signalsIndex
and you should see thatAlos the doc is here -> https://github.com/elastic/kibana/blob/master/src/core/MIGRATION.md#handle-plugin-configuration-deprecations