You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many screens in kibana feature a "share" link in the top bar to provide a short link to the current browser location. But lens doesn't.
It'd be great to have feature parity there.
Describe a specific use case for the feature:
Often when exploring data, you don't have a dashboard yet. You just have lens and you're poking around at things that might be useful angles on the problem.
When you find something, you want to share it with your colleagues (especially during problem investigations). Today on lens you have to first save the lens viz, but now what do you name it (naming is hard)?
Additionally the saved lens viz doesn't include a time frame, so there's no way to share a specific timeframe of a lens visualization without a dashboard (now what do you name the dashboard?).
Apologies if this is a duplicate, I thought I'd raised this in the past but I'm unable to find the issue at the moment.
The text was updated successfully, but these errors were encountered:
Describe the feature:
Many screens in kibana feature a "share" link in the top bar to provide a short link to the current browser location. But lens doesn't.
It'd be great to have feature parity there.
Describe a specific use case for the feature:
Often when exploring data, you don't have a dashboard yet. You just have lens and you're poking around at things that might be useful angles on the problem.
When you find something, you want to share it with your colleagues (especially during problem investigations). Today on lens you have to first save the lens viz, but now what do you name it (naming is hard)?
Additionally the saved lens viz doesn't include a time frame, so there's no way to share a specific timeframe of a lens visualization without a dashboard (now what do you name the dashboard?).
Apologies if this is a duplicate, I thought I'd raised this in the past but I'm unable to find the issue at the moment.
The text was updated successfully, but these errors were encountered: