US 11,886,297 B2
Restart tolerance in system monitoring
Nigel Slinger, Los Gatos, CA (US); Wenjie Zhu, Dublin (IE); Catherine Drummond, Morgan Hill, CA (US); Roxanne Kallman, Ham Lake, MN (US); Sudipta Sengupta, Richmond, TX (US); Jeremy Riegel, Houston, TX (US); and John Flournoy, Lago Vista, TX (US)
Assigned to BMC Software, Inc., Houston, TX (US)
Filed by BMC Software, Inc., Houston, TX (US)
Filed on Nov. 9, 2022, as Appl. No. 18/054,024.
Application 18/054,024 is a continuation of application No. 17/248,396, filed on Jan. 22, 2021, granted, now 11,526,400.
Prior Publication US 2023/0115166 A1, Apr. 13, 2023
Int. Cl. G06F 11/07 (2006.01); G06F 11/14 (2006.01); H04L 41/0893 (2022.01)
CPC G06F 11/1438 (2013.01) [G06F 11/0715 (2013.01); H04L 41/0893 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer program product, the computer program product being tangibly embodied in a non-transitory computer-readable storage medium and comprising instructions that, when executed by at least one computing device, are configured to cause the at least one computing device to:
monitor, at the at least one computing device, a stream of performance metrics received from components of a technology landscape;
generate a performance characterization of the technology landscape, using the stream of performance metrics, the performance characterization including characterizing each component of the components as operating normally or abnormally based on scores assigned to the performance metrics using a common scoring scheme that defines a normal range and a restart range;
detect, based on the stream of performance metrics, a restart event within the technology landscape and associated with a component of the components;
determine, in response to the restart event, restart-impacted performance metrics that have scores that are outside of the restart range and non-restart-impacted performance metrics that have scores that are within the restart;
include scores of the non-restart-impacted performance metrics within the performance characterization;
monitor, at the at least one computing device, scores of the restart-impacted performance metrics while excluding the restart-impacted performance metrics from the performance characterization;
detect that a score of a restart-impacted performance metric is no longer within the restart range;
automatically transition the restart-impacted performance metric of the restart-impacted performance metrics to a non-restart-impacted performance metric to be included within the performance characterization; and
generate an alert within the performance characterization indicating that the component is operating outside of the normal range.