Skip to content
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] [Sourcerer] Sourcerer matched indices not picking up .alerts index on fresh kibana + ES #150818

Closed
dhurley14 opened this issue Feb 9, 2023 · 11 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Sourcerer Security Solution Sourcerer feature impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detection Engine Security Solution Detection Engine Area v8.7.0

Comments

@dhurley14
Copy link
Contributor

When the .alerts index does not exist, sourcerer does not find it as part of the matched indices on the security default data view which results in some features not working as expected (opening 'inspect in timeline' from the alerts table doesn't load the data, some issues around the execution log, etc..). The fix is to simply perform a browser refresh on the page and the matched indices on the data view are reloaded however it would be great if the matched indices were updated when a new index matching the index patterns defined on the data view is created.

@dhurley14 dhurley14 changed the title [Security Solution] [Sourcerer] [Security Solution] [Sourcerer] Sourcerer matched indices not picking up .alerts index on fresh kibana + ES Feb 9, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 9, 2023
@dhurley14 dhurley14 added Team:Security Solution Platform Security Solution Platform Team v8.7.0 Feature:Sourcerer Security Solution Sourcerer feature bug Fixes for quality problems that affect the customer experience and removed needs-team Issues missing a team label labels Feb 9, 2023
@stephmilovic stephmilovic added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Feb 15, 2023
@dhurley14
Copy link
Contributor Author

The only way to go about fixing this is to refresh the data view every time we fetch it in sourcerer (https://github.com/elastic/kibana/pull/151954/files#diff-508f840edbd45c95151db939b1894ca52ec682fb0863eccdf420eed427f53663R15). This is a fairly heavy operation. And by replacing sourcerer with the ad-hoc data view component we will no longer need to rely on the matched indices property for fetching data. My focus for 8.8 will be on expediting the removal and replacement of sourcerer.

@dhurley14
Copy link
Contributor Author

Fixed here: #154076

@dhurley14 dhurley14 added fixed and removed won't fix labels Apr 4, 2023
@MadameSheema
Copy link
Member

@karanbirsingh-qasource @sukhwindersingh-qasource please validate the fix on current BC. Thanks!

@ghost
Copy link

ghost commented May 8, 2023

@MadameSheema @dhurley14 can we get steps to regress this issue we have checked this comment #150818 (comment) in which it is mentioned we dont have to do own browser refresh but if we can exact step to check this issue is fixed or not

@dhurley14
Copy link
Contributor Author

Sure thing! I just want to preface this by saying this is still an issue for the non-default space. So maybe this isn't "fixed" necessarily. But either way, here are the steps:

  1. Clean kibana
  2. Provide data
  3. Create a single rule that will alert on the given data
  4. navigate to the alerts page
  5. Alerts should appear without having to refresh the page.

@MadameSheema
Copy link
Member

@karanbirsingh-qasource do you have now all the needed information to validate the fix? Thanks!

@ghost
Copy link

ghost commented May 9, 2023

Here are observation to the above steps:

  1. Clean kibana

Created the fresh instance

  1. Provide data

Installed Audit beat Data Shipper to Kibana instance

  1. Create a single rule that will alert on the given data

Create a Custom Rule for process.name: "cmd.exe"
After Clicking on Create and Enable button
Run the cmd on machine

  1. navigate to the alerts page
  2. Alerts should appear without having to refresh the page.
Rules.-.Kibana.-.Google.Chrome.2023-05-09.16-19-06.mp4

@MadameSheema MadameSheema removed the fixed label May 9, 2023
@MadameSheema
Copy link
Member

Thanks @karanbirsingh-qasource!! Pending to be validated in different spaces as soon as the fix is complete.

@yctercero yctercero added Team:Detection Engine Security Solution Detection Engine Area and removed Team:Security Solution Platform Security Solution Platform Team labels May 14, 2023
@yctercero
Copy link
Contributor

Hey @MadameSheema ! Could we get this re-validated to see if we can close out?

@MadameSheema
Copy link
Member

Sure!! @karanbirsingh-qasource can you please take care of this? thx!

@ghost
Copy link

ghost commented Jun 5, 2024

Hi @MadameSheema

This is issue if fixed ✔️ . Alert entries show up without refreshing the page

Default Space

237075060-f87fa8ef-bfa2-47ef-9f36-4356ba77a3fb.mp4

Non Default Space

Create.new.rule.-.Kibana.Mozilla.Firefox.2024-06-05.15-34-54.mp4

@ghost ghost closed this as completed Jun 5, 2024
@ghost ghost added the QA:Validated Issue has been validated by QA label Jun 5, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Sourcerer Security Solution Sourcerer feature impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detection Engine Security Solution Detection Engine Area v8.7.0
Projects
None yet
Development

No branches or pull requests

4 participants