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] [Question] Warning messages shown under Upgrade Assistant are different in PR and Kibana environment. #128353

Closed
ghost opened this issue Mar 23, 2022 · 3 comments
Assignees
Labels
Question Ticket having question for Dev team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed

Comments

@ghost
Copy link

ghost commented Mar 23, 2022

Describe the Question:
Warning messages shown under Upgrade Assistant are different in PR and Kibana environment.

Build Details:

Version: 7.17.2 Snapshot
Build: 46718
Commit: b43ac3cb94a84577caa0dd40aba6f20c58feb677

Preconditions

  1. Elasticsearch should be up and running
  2. Kibana should be up and running

Steps to Reproduce

  1. Navigate to Stack Management-->Kibana--> Index Patterns.
  2. Create Index Pattern .siem-signals-* .
  3. Navigate to Stack Management-->>Security Roles.
  4. Create role with below configuration.
    image

image

image

  1. Create a new user and assign above created role to created user.
  2. Login with created user in Kibana Environment.
  3. Navigate to Stack Management-->Stack-->Upgrade Assistant.
  4. Click on Kibana Warnings.
  5. Click on the Warning The Detections Rule Preview feature is changing.

Screenshots:

PR Screenshot
#116878

Annotation 2022-03-23 150454

Kibana Environment
Annotation 2022-03-23 150515

@ghost ghost added triage_needed Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Question Ticket having question for Dev team labels Mar 23, 2022
@ghost ghost self-assigned this Mar 23, 2022
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@ghost ghost assigned MadameSheema and unassigned ghost Mar 23, 2022
@MadameSheema
Copy link
Member

@karanverma-qasource the behavior described above is correct.

@marshallmain feel free to reopen the ticket if you don't agree with it.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Ticket having question for Dev team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed
Projects
None yet
Development

No branches or pull requests

2 participants