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

[ES|QL] Filter by dashboard map bounds filter makes es|ql panel display empty panel #186578

Closed
bhavyarm opened this issue Jun 20, 2024 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Dashboard Dashboard related features Feature:ES|QL ES|QL related features in Kibana impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:needs-research This issue requires some research before it can be worked on or estimated Team:ESQL ES|QL related features in Kibana

Comments

@bhavyarm
Copy link
Contributor

bhavyarm commented Jun 20, 2024

Kibana version: serverless-qa/main

Browser version: chrome version

Original install method (e.g. download page, yum, from source, etc.): from QA

Describe the bug: If user has a "Filter by dashboard map bounds filter" on a dashboard and clicks to add an ES|QL panel - the initial panel display is empty.

esql_empty.mp4

This is filter by dashboard map bounds by the way

filter_by_dashboard
@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience Feature:Dashboard Dashboard related features Feature:ES|QL ES|QL related features in Kibana Team:ESQL ES|QL related features in Kibana labels Jun 20, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-esql (Team:ESQL)

@kibanamachine kibanamachine added loe:needs-research This issue requires some research before it can be worked on or estimated impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Jun 20, 2024
@bhavyarm
Copy link
Contributor Author

Please note - I did log this on dashboards for filter by dashboard map bounds - #186577

@stratoula
Copy link
Contributor

The query that runs is

POST /_query/async?drop_null_columns
{
  "query": "from logs* | limit 10",
  "locale": "en",
  "filter": {
    "bool": {
      "must": [],
      "filter": [
        {
          "bool": {
            "must": [
              {
                "exists": {
                  "field": "geo.coordinates"
                }
              },
              {
                "geo_bounding_box": {
                  "geo.coordinates": {
                    "top_left": [
                      -120.61818,
                      49.71596
                    ],
                    "bottom_right": [
                      -57.223960000000034,
                      33.58892
                    ]
                  }
                }
              }
            ]
          }
        },
        {
          "range": {
            "@timestamp": {
              "format": "strict_date_optional_time",
              "gte": "2024-06-20T06:00:00.000Z",
              "lte": "2024-06-21T06:02:58.114Z"
            }
          }
        }
      ],
      "should": [],
      "must_not": []
    }
  }
}

If you run it in DevTools it returns no data so this is expected.

If you change the index in a compatible with this DSL filter index it will work, as I did here

image

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 Feature:Dashboard Dashboard related features Feature:ES|QL ES|QL related features in Kibana impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:needs-research This issue requires some research before it can be worked on or estimated Team:ESQL ES|QL related features in Kibana
Projects
None yet
Development

No branches or pull requests

4 participants