-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Derivative aggregation gets stuck in error state #22833
Copy link
Copy link
Closed
Labels
Feature:VisualizationsGeneric visualization features (in case no more specific feature label is available)Generic visualization features (in case no more specific feature label is available)Team:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experienceregression
Metadata
Metadata
Assignees
Labels
Feature:VisualizationsGeneric visualization features (in case no more specific feature label is available)Generic visualization features (in case no more specific feature label is available)Team:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//Team label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experienceregression
Type
Fields
Give feedbackNo fields configured for issues without a type.
Kibana version:
6.4.0
Elasticsearch version:
6.4.0
Server OS version:
Cloud
Browser version:
Chrome Version 68.0.3440.106 (Official Build) (64-bit)
Browser OS version:
OSX 10.13.6
Original install method (e.g. download page, yum, from source, etc.):
Cloud
Describe the bug:
When Derivative aggregation gets in an erroneous state, it can't be fixed by fixing the error.
Steps to reproduce:
Create a simple derivative graph with a date histogram

Make any "mistake" (I thought it was possible to create a split chart with derivative...)

The tooltip just shows:

And hovering over the red box doesn't show anything.
Whatever I do I can't repair that error. If I create a new visualization from scratch without doing any mistakes the same visualization works again.
Expected behavior:
To be able to recover from errors
Errors in browser console (if relevant):
None
Any additional context: