-
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
[Lens][TSVB] Add support for default fields in convert to lens #151109
Comments
Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations) |
Edit Was that a dataView with no default time field set? What's the rest of the TSVB time series configuration? |
I guess it is a TSVB that works on the deprecated index pattern mode. |
When we try converting panels from existing dashboards (for example ActiveMQ), it won't show option Edit visualisation in lens. But if we will click on the time field and select @timestamp field then the Edit visualisation in lens option will be available on top. This is happening in imported/integration's dashboard only. As the "time_field" value is empty in the json file of dashboard. |
Closing this as we cant reproduce it |
Describe the feature:
The "Convert to lens" feature will be added at the dashboard level in 8.7.0. This feature does not migrate TSVB visualizations that have not configured
time_field
.Describe a specific use case for the feature:
The "Convert to lens" feature helps to migrate visualizations to the lens at the dashboard level. But for TSVB visualization, if
time_field
is not configured, it won't show the "Convert to lens" option. Although, after selectingtime_field
the "Convert to lens" will appear.Before configuring
![tsvb-i1-b](https://user-images.githubusercontent.com/121489654/218705370-662e0013-9e67-46af-9fc9-15f6b7d9f454.png)
time_field
:After configuring
![tsvb-i1-a](https://user-images.githubusercontent.com/121489654/218705361-5b112528-2b3b-455f-8ed6-7a5d015c8daf.png)
time_field
:The text was updated successfully, but these errors were encountered: