#Sumo logic sum count timeslice verification#

However, we've modified our unsupervised machine learning significantly to scale for 24x7 data streams. Like Continuous Verification, our 24x7 Service Guard sits on top of all your APM, monitoring, and log tools. We want to give developers total operational visibility of their production apps across all tools, and protect them when they weren't looking. Catching post-deployment issues and tool fatigue are why we created the 24x7 Service Guard. Unifying these data sets is a huge challenge for developers and teams. In a microservices world, a customer could have tens of microservices with tens of different monitoring tools, logs, and instrumentation. They had one of everything to monitor different aspects of their application. Sometimes deployments are done out-of-hours when minimal traffic is using the app, or specific functionality in the app might not be accessed or stressed immediately by users.Īt the same time, our customers were struggling with monitoring tool fatigue. This capability was great at catching two thirds of performance anomalies and/or quality regressions because most applications fail within minutes of deployment.Ģ4x7 Service Guard was created to catch the anomalies/regressions that surfaced many hours after a new deployment.

#Sumo logic sum count timeslice verification#

Customers could customize this verification duration but it was always finite in scope. Our initial Continuous Verification was focused on deployments or canary phases, analyzing the performance/quality of new code during the first 15-20 minutes of its life.