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

[SIEM][Detection Engine] Typo on Detection Engine page #53876

Closed
benskelker opened this issue Jan 1, 2020 · 1 comment · Fixed by #53877
Closed

[SIEM][Detection Engine] Typo on Detection Engine page #53876

benskelker opened this issue Jan 1, 2020 · 1 comment · Fixed by #53877
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM v7.6.0 v8.0.0

Comments

@benskelker
Copy link
Contributor

Kibana version: 8.0

Describe the bug: Typo on Detection Engine page when no SIEM indices are found.

Steps to reproduce:

  1. Make sure no SIEM indices are configured
  2. Navigate to the SIEM > Detection engine page

Screenshots (if relevant):
Screenshot 2020-01-01 at 12 25 16
Should be:
It looks like you don’t have any indices relevant to the detection engine in the SIEM application

@benskelker benskelker added bug Fixes for quality problems that affect the customer experience Team:SIEM labels Jan 1, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/siem (Team:SIEM)

@benskelker benskelker assigned benskelker and unassigned XavierM Jan 1, 2020
@MindyRS MindyRS added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Oct 27, 2020
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 Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM v7.6.0 v8.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants