Skip to content

[ML] Fix Anomaly Explorer population charts when multiple causes in anomaly #84254

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 25, 2020
Merged

[ML] Fix Anomaly Explorer population charts when multiple causes in anomaly #84254

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion x-pack/plugins/ml/public/application/util/chart_utils.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,10 @@ export function chartExtendedLimits(data = [], functionDescription) {
metricValue = actualValue;
}

if (d.anomalyScore !== undefined) {
// Check for both an anomaly and for an actual value as anomalies in detectors with
// by and over fields and more than one cause will not have actual / typical values
// at the top level of the anomaly record.
if (d.anomalyScore !== undefined && actualValue !== undefined) {
_min = Math.min(_min, metricValue, actualValue, typicalValue);
_max = Math.max(_max, metricValue, actualValue, typicalValue);
} else {
Expand Down