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

Log explorer ->Discover retains column names even when they are not relevant to current search/dataview in serverless observability projects #172628

Closed
bhavyarm opened this issue Dec 5, 2023 · 4 comments · Fixed by #170200
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Discover Discover Application Feature:LogsExplorer Logs Explorer feature Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. Team:obs-ux-logs Observability Logs User Experience Team

Comments

@bhavyarm
Copy link
Contributor

bhavyarm commented Dec 5, 2023

Kibana version: main

Elasticsearch version: main

Browser version: chrome latest

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

Describe the bug: Log explorer auto-selects service name, host name, message as "Selected fields" in discover side bar. When user clicks on open in Discover and picks any dataview - even though the picked dataview doesn't have these fields - they get displayed as columns in discover.

This used to happen in analytics ->discover and I cannot find my bug but it did get fixed a while ago.

columns_get_retained.mp4
@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience Feature:Discover Discover Application Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. Team:obs-ux-logs Observability Logs User Experience Team Feature:LogsExplorer Logs Explorer feature labels Dec 5, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

@bhavyarm
Copy link
Contributor Author

bhavyarm commented Dec 5, 2023

Please note this also caused another display issue and specific to non-time series data. I used the data visualizer to upload a csv of squirrel census data (non-time series data). The ingestion went through fine and squirrels dataview got created successfully. When I navigated to log explorer -> open in discover -> picked squirrels as data view - no documents got displayed. Once I manually removed selected columns - service name, host name and messages - I could see my data. may be we will never have logs data without time? In which case its user error (the problem is me :)) Just thought will note it down here.
Screenshot 2023-12-05 at 4 08 59 PM

Screenshot 2023-12-05 at 4 09 08 PM

@weltenwort
Copy link
Member

Thanks for reporting this, @bhavyarm! In #170200 we completely rewrite the way state is represented in the URL, so I will try to make sure this doesn't happen anymore.

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:Discover Discover Application Feature:LogsExplorer Logs Explorer feature Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. Team:obs-ux-logs Observability Logs User Experience Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants