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.

Sign up for GitHub

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

Jump to bottom

[Security Solution] Rule creation UI: incorrect link for index patterns #163503

Open
abdonpijpelink opened this issue Aug 9, 2023 · 2 comments
Open

[Security Solution] Rule creation UI: incorrect link for index patterns #163503

abdonpijpelink opened this issue Aug 9, 2023 · 2 comments
Assignees
@yctercero
Labels
bug Fixes for quality problems that affect the customer experience consider-next Feature:Rule Creation Security Solution Detection Rule Creation workflow impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@abdonpijpelink
Copy link
Contributor

Kibana version:
8.9

Description of the problem including expected versus actual behavior:
The Security rule creation UI allows you to create a rule based on index patterns or data views. Confusingly, Elastic has two different things called "index pattern": an Elasticsearch construct, and a Kibana construct (deprecated, now called "data view"). I think the link for "index patterns" (see red arrow in the screenshot) goes to the wrong docs. It points to API docs for the deprecated Kibana construct, but it should point to the ES construct.

I think a better page to link to could be https://www.elastic.co/guide/en/elasticsearch/reference/current/api-conventions.html#api-multi-index, or even better a new standalone page that explains what index patterns are in this context.

image

cc: @Arnovandevelde
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 9, 2023
@banderror banderror added bug Fixes for quality problems that affect the customer experience triage_needed Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Feature:Rule Creation Security Solution Detection Rule Creation workflow Team:Detection Engine Security Solution Detection Engine Area and removed needs-team Issues missing a team label labels Aug 9, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@banderror banderror assigned yctercero and unassigned banderror Aug 9, 2023
@banderror banderror changed the title Security rule creation UI: incorrect link for index patterns [Security Solution] Rule creation UI: incorrect link for index patterns Aug 9, 2023
@peluja1012 peluja1012 added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yctercero yctercero

Labels
bug Fixes for quality problems that affect the customer experience consider-next Feature:Rule Creation Security Solution Detection Rule Creation workflow impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
Security Bug Audit
Status: To do
Milestone
No milestone
Development

No branches or pull requests
5 participants
@peluja1012 @banderror @abdonpijpelink @yctercero @elasticmachine