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] [Bug] Error The "event.category" field can not be used for filtering. is shown under Rule Preview section for graphs. #213705

Open
arvindersingh-qasource opened this issue Mar 10, 2025 · 5 comments
Open

[Security Solution] [Bug] Error The "event.category" field can not be used for filtering. is shown under Rule Preview section for graphs. #213705

arvindersingh-qasource opened this issue Mar 10, 2025 · 5 comments
Assignees
@yctercero
Labels
bug Fixes for quality problems that affect the customer experience 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. triage_needed v8.18.0

Comments

@arvindersingh-qasource
Copy link

Describe the bug
Error The "event.category" field can not be used for filtering. is shown under Rule Preview section for graphs.

Kibana/Elasticsearch Stack version

VERSION: 8.18.0
BUILD: 82626
COMMIT: d3a58d9029840ade8ef9600388f5b102db889e09

Pre Conditions

  1. Kibana v8.18.0 must be available.
  2. Few Endpoints must be available.
  3. Few Alerts should be available on Kibana,

Steps

  1. Navigate to Security -> Detection Rules.
  2. Click on Create New Rule
  3. Select Custom Query as Rule Type.
  4. Under Custom Query as Host.name : *
  5. Under Rule Preview Section, Click on Refresh button.
  6. Observe that there will be Error The "event.category" field can not be used for filtering. is shown under Rule Preview section for graphs.

Expected Result
There should be no error The "event.category" field can not be used for filtering. shown under Rule Preview section and appropriate graphs should be visible.

Screen Shot
Image
@arvindersingh-qasource arvindersingh-qasource added bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v8.18.0 labels Mar 10, 2025
@elasticmachine
Copy link
Contributor

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

@arvindersingh-qasource
Copy link
Author

@muskangulati-qasource Please review this ticket.

Thanks.

@MadameSheema MadameSheema added Team:Detections and Resp Security Detection Response Team Team:Detection Engine Security Solution Detection Engine Area labels Mar 10, 2025
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

@muskangulati-qasource
Copy link

Secondary review is Done for this ticket!

Open
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 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. triage_needed v8.18.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@yctercero @elasticmachine @MadameSheema @muskangulati-qasource @arvindersingh-qasource