Skip to content
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

[ML] Overall swimlane and job swimlane should query same data #18488

Open
elasticmachine opened this issue Apr 25, 2017 · 0 comments
Open

[ML] Overall swimlane and job swimlane should query same data #18488

elasticmachine opened this issue Apr 25, 2017 · 0 comments

Comments

@elasticmachine
Copy link
Contributor

elasticmachine commented Apr 25, 2017

Original comment by @sophiec20:

Found in {"build":{"hash":"b02dfdf","date":"2017-04-24T13:33:22.536Z"}

image

The Overall swimlane is the max(anomaly_score) where result_type is bucket_influencer.

The Job swimlane is the anomaly_score where result_type is bucket.

These values should be identical, because the bucket anomaly_score is calculated to be the max(bucket_influencer anomaly_score).

It seems wise that the overall swimlane should query the same results as the job_id swimlanes.

Perhaps this should be max(bucket_influencer anomaly_score) as this will allow us to filter by influencer type, at some point in the future. e.g. Show me the most unusual client_ips..

Requires further investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants