-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Legend order does not match with query result #154533
Comments
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Relevant links: |
## Summary This fix below query issues within DNS histogram: ### 1. The terms aggregates field should be `dns.question.regustered_domain` instead `dns.question.domain` **Steps to verify:** - Inspect the chart and observe the query should do terms aggregation on `dns.question.regustered_domain` **Known issue:** #154533 <img width="1673" alt="Screenshot 2023-04-06 at 12 40 38" src="https://user-images.githubusercontent.com/6295984/230366661-bb9ce5d3-7e80-460e-af64-8fbe26521c1c.png"> ### 2. It didn't respect `is PTR record included` flag **Steps to verify:** - Switch the toggle in DNS tab to `include PTR record` - Inspect the chart and observe the query should not exclude PTR record - Click on Add to new Case / Add to existing Case / Open in Lens and observe the query should not exclude PTR record. https://user-images.githubusercontent.com/6295984/230366687-8cf0a4dd-beca-46ef-b756-ce898f289c47.mov ### 3. It didn't respect `is PTR record included` when feature flag `chartEmbeddablesEnabled: is false` **Steps to verify:** - Set chartEmbeddablesEnabled to false - Switch the toggle in DNS tab to `include PTR record` - Click on Add to new Case / Add to existing Case / Open in Lens and observe the query should not exclude PTR record. https://user-images.githubusercontent.com/6295984/230420883-a1541d91-7414-4ce8-9ef5-ffb00e7d174d.mov **After:** https://user-images.githubusercontent.com/6295984/230366882-3fe857b0-b3d6-46cf-aaa7-646190ae661f.mov ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
Yes, the legend's sort order is now backward from what it has always been (at least on every version we have used in the last ~5 years), and it is counter intuitive. If the selected order is "descending", the largest value should be on top. |
This is a question about the legend’s order. I have a bar chart break down by
unique count of dns.question.name
ranked in descending order (screenshot 1, 2), the result comes out as expected order: key apple.com with greatest value 55 , but the legend is not following the order, would like to know if there’s a way I can apply the same order to the legend?Setup:
Request:
Result:
The text was updated successfully, but these errors were encountered: