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] Count for lines of ES|QL query under Timeline is wrongly shown #182811

Closed
arvindersingh-qasource opened this issue May 7, 2024 · 7 comments
Labels
bug Fixes for quality problems that affect the customer experience impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.14.0

Comments

@arvindersingh-qasource
Copy link

Describe the bug
Count for lines of ES|QL query under Timeline is wrongly shown

Build Details

VERSION: 8.14.0
BUILD: 73762
COMMIT: 2a492e1625f24336f3259b2b8df62b2b18127e81

Browser Details
This issue is occurring on all browsers.

Preconditions

  1. Kibana v8.14.0 must be available.

Steps to Reproduce

  1. Navigate to Security -> Timelines
  2. Create new Timeline or Open any already available Timeline.
  3. Navigate to ES|QL tab.
  4. Under Query section, add multiline query.
  5. Observe that Count for lines in query is shown correctly.
  6. Click on Run option.
  7. Observe that the Count for lines of ES|QL query on right hand side of query section under Timeline is wrongly shown.

Actual Result
Count for lines of ES|QL query under Timeline is wrongly shown

Expected Result
Count for lines of ES|QL query under Timeline is correctly shown

What's Working

  • N/A

What's Not Working

  • N/A

Screen Recording

Alerts.-.Kibana.-.Google.Chrome.2024-05-07.14-43-31.mp4
@arvindersingh-qasource arvindersingh-qasource added bug Fixes for quality problems that affect the customer experience triage_needed Team:Threat Hunting Security Solution Threat Hunting Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team v8.14.0 labels May 7, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

@elasticmachine
Copy link
Contributor

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

@arvindersingh-qasource arvindersingh-qasource added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label May 7, 2024
@arvindersingh-qasource
Copy link
Author

@karanbirsingh-qasource Please review this ticket.

Thanks.

@ghost ghost assigned MadameSheema and unassigned ghost May 7, 2024
@MadameSheema MadameSheema added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels May 7, 2024
@logeekal
Copy link
Contributor

logeekal commented May 7, 2024

Hey @arvindersingh-qasource

I tried to reproduce this error.. but I am not able to... Could you please chckec again..See video below

reproduce_ESQL_line_error.mp4

@MadameSheema MadameSheema removed their assignment May 24, 2024
@MadameSheema
Copy link
Member

@arvindersingh-qasource any update on the above? Thanks

@arvindersingh-qasource
Copy link
Author

arvindersingh-qasource commented Oct 22, 2024

Hi @logeekal

We have validated this issue on Kibana v8.16.0 and found that as per the latest UI of Kibana, this issue is now not reproducible.

Please find below observations

Build Details

VERSION: 8.16.0
BUILD: 79314
COMMIT: 5575428dd3aef69366cddb4ccf07a2a26d30ce48

Observations

Image

Hence, we are closing this ticket as QA Validated.

Thanks.

@arvindersingh-qasource arvindersingh-qasource added the QA:Validated Issue has been validated by QA label Oct 22, 2024
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 impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team v8.14.0
Projects
None yet
Development

No branches or pull requests

5 participants