Abstract: A computer device may include a processor configured to obtain key performance indicator (KPI) values for KPI parameters associated with at least one device and compute a set of historical statistical values for the obtained KPI values associated with the network device. The processor may be further configured to provide the KPI values and the computed set of historical statistical values to an anomaly detection model to identify potential anomalies; filter the identified potential anomalies based on a designated desirable behavior for a particular KPI parameter to identify at least one anomaly; and send an alert that includes information identifying the at least one anomaly to a management system or a repair system associated with the device. The computer device may further determine a root cause KPI parameter for the identified at least one anomaly and include information identifying the determined root cause KPI parameter in the alert.

Abstract: A computer device may include a processor configured to obtain key performance indicator (KPI) values for KPI parameters associated with at least one device and compute a set of historical statistical values for the obtained KPI values associated with the network device. The processor may be further configured to provide the KPI values and the computed set of historical statistical values to an anomaly detection model to identify potential anomalies; filter the identified potential anomalies based on a designated desirable behavior for a particular KPI parameter to identify at least one anomaly; and send an alert that includes information identifying the at least one anomaly to a management system or a repair system associated with the device. The computer device may further determine a root cause KPI parameter for the identified at least one anomaly and include information identifying the determined root cause KPI parameter in the alert.

Abstract: A computer device may include a processor configured to obtain key performance indicator (KPI) values for KPI parameters associated with at least one device and compute a set of historical statistical values for the obtained KPI values associated with the network device. The processor may be further configured to provide the KPI values and the computed set of historical statistical values to an anomaly detection model to identify potential anomalies; filter the identified potential anomalies based on a designated desirable behavior for a particular KPI parameter to identify at least one anomaly; and send an alert that includes information identifying the at least one anomaly to a management system or a repair system associated with the device. The computer device may further determine a root cause KPI parameter for the identified at least one anomaly and include information identifying the determined root cause KPI parameter in the alert.

Abstract: A computer device may include a processor configured to obtain key performance indicator (KPI) values for KPI parameters associated with at least one device and compute a set of historical statistical values for the obtained KPI values associated with the network device. The processor may be further configured to provide the KPI values and the computed set of historical statistical values to an anomaly detection model to identify potential anomalies; filter the identified potential anomalies based on a designated desirable behavior for a particular KPI parameter to identify at least one anomaly; and send an alert that includes information identifying the at least one anomaly to a management system or a repair system associated with the device. The computer device may further determine a root cause KPI parameter for the identified at least one anomaly and include information identifying the determined root cause KPI parameter in the alert.

Abstract: Techniques are provided for recording service invocation traffic in a format that is suitable for subsequent replay, perhaps in a different environment. In one technique, a computing device records invocation traffic. The computing device receives a first request that is directed to a first service. In response to receiving the first request, one or more computers store an identifier of the first request into a second request. After storing the identifier into the second request, the computing device causes the second request to be sent to a second service. After causing the second request to be sent to the second service, the computing device receives, from the second service, a response that contains the identifier of the first request. The one or more computers store, in a single record, the first request, the second request, and the response.

Abstract: Techniques are provided for mocking downstream services while regression testing a service. In one technique a version of a service processes a request, during which one or more computers intercept downstream service calls made by the version of the service. For each downstream service call of the downstream calls, a computer provides, to the version of the service, a response of the downstream service call, which was previously recorded while processing the request in a production environment. Processing, by the version of the service, the request involves processing the request based on the response of at least one of the downstream service calls.

Abstract: Techniques are provided for recording service invocation traffic in a format that is suitable for subsequent replay, perhaps in a different environment. In one technique, a computing device records invocation traffic. The computing device receives a first request that is directed to a first service. In response to receiving the first request, one or more computers store an identifier of the first request into a second request. After storing the identifier into the second request, the computing device causes the second request to be sent to a second service. After causing the second request to be sent to the second service, the computing device receives, from the second service, a response that contains the identifier of the first request. The one or more computers store, in a single record, the first request, the second request, and the response.

Abstract: Techniques are provided for mocking downstream services while regression testing a service. In one technique a version of a service processes a request, during which one or more computers intercept downstream service calls made by the version of the service. For each downstream service call of the downstream calls, a computer provides, to the version of the service, a response of the downstream service call, which was previously recorded while processing the request in a production environment. Processing, by the version of the service, the request involves processing the request based on the response of at least one of the downstream service calls.