Fix undefined Handler Type in current master branch #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Release 1.0.4, I noticed that the default Handler Type is not selected for new series as seen in the screenshot below:
I have only recently noticed this and suspect it could actually be due to new behaviour in Grafana version 4.4.1.
The issue results from upgradeOldVersion() being called multiple times on a new series when still on the Metrics tab and before the Options tab has a chance to set the default. This results in valueHandler being incorrectly set to "Regular" rather than the default of"Threshold" (i.e. valueHandlers[0]).
Looking at the code in status_ctrl.js, this occurs as follows:
I think this is new behaviour in the latest Grafana release as I cannot recall seeing this problem before. The fix uses (target.displayType != null) to limit the upgrade checks to only legacy series and not new ones.