All Apps and Add-ons

When to establish boundaries for MLTK based alerts?

SMM10
Explorer

I was working in the MLTK, very new to it and exploring. I was working to establish a few searches where I will fit a algorithm and then apply it to identify if any values out of a set boundary and then alert on that. I have two question from this.

 

Is this a valid use case or not so much?

I have a predicted value after my fit but, its too close to my actual values so I was thinking of doing something like(+ or - depending on need):

eval bound = (predictedavg - (stdev * 3))

 Would it be more beneficial to calculate this in the fit search or when applying the model?

Labels (2)
Tags (2)
0 Karma
Get Updates on the Splunk Community!

Get ready to show some Splunk Certification swagger at .conf24!

Dive into the deep end of data by earning a Splunk Certification at .conf24. We're enticing you again this ...

Built-in Service Level Objectives Management to Bridge the Gap Between Service & ...

Now On-Demand Join us to learn more about how you can leverage Service Level Objectives (SLOs) and the new ...

Database Performance Sidebar Panel Now on APM Database Query Performance & Service ...

We’ve streamlined the troubleshooting experience for database-related service issues by adding a database ...