-
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] Users can insert vertical line annotations on timeseries charts #87564
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
Can we please prioritise this, this is one of the key feature for our page load distribution chart, which we are planing to implement via lens embeddable in https://github.com/elastic/uptime-dev/issues/46 |
@shahzad31 I don't think this issue is the right one for your use case, but it depends on where the data will be stored. This issue is specifically for annotations that are owned by the Lens app, not annotations from external sources. We are also tracking an issue to query ES for annotation data as a read-only source. It's also possible that your use case is not on our roadmap right now, and we may need to open a new issue or reorganize the existing issues. |
@shahzad31 Sounds like you've talked with @flash1293. Based on this clarification, the right issue for you is this one: #87551 |
I do miss the annotation feature on Lens. My use-case is to have a vertical line to show when a change is applied on systems, so I can correlate systems changes in errors and/or drop of requests. The information about when a change is applied is stored on another doc and it is quite easy to extract it with a filter on an index. Does anyone know if Lens will get support for this? |
@unixsurfer we are currently working on this very feature - see #119240 for our preliminary roadmap |
@flash1293 thanks a lot for the quick reply. |
8.2 delivers the core tech preview of this issue. #62277 will be used to track the query-based aspects of these requirements. |
This issue depends on a decision on where to store annotation data as well as the ability for visualizations to have multiple layer types and to query data asynchronously for visualizations.
There are three important user flows that we should support:
Each time the visualization time range is updated, the annotations need to be queried again, so that we only show annotations within the time range:
User flow to insert annotation
I think users need to click on the chart to insert an annotation, so I think the flow here starts on the annotation list:
Users will click "insert annotation", which causes the chart to enter edit mode. The next click on the chart will set the marker and open the popover to type the label and tags.
The text was updated successfully, but these errors were encountered: