Abstract: An example device is described for facilitating pull request reviews based on event-trace streams. In various aspects, the device can comprise a processor. In various instances, the device can comprise a non-transitory machine-readable memory that can store machine-readable instructions. In various cases, the processor can execute the machine-readable instructions, which can cause the processor to perform an automated pull request review for a first version of a computing application and a second version of the computing application, based on a first event-trace stream associated with the first version and a second event-trace stream associated with the second version.

Abstract: In some examples, a computing device can include a processing resource and a memory resource storing instructions to cause the processing resource to receive an audit request for a web application, locate runtime data located in an execution trace of the web application in response to receiving the audit request, where the execution trace is generated by an omniscient debugger monitoring the web application, and annotate the runtime data in response to the runtime data being located.

Abstract: A system includes: a distributed computing subsystem to execute an adjustable number of instances of a request handling process; and a scaling control subsystem connected with the distributed computing subsystem to: allocate received requests among the instances of the request handling process; receive respective self-perceived load indicators from each of the instances of the request handling process; generate, based on the self-perceived load indicators, a total load indicator of the distributed computing subsystem; and compare the total load indicator to a threshold to select an adjustment action; and instruct the distributed computing subsystem to adjust the number of instances of the request handling process, according to the selected adjustment action.

Abstract: An example system includes: an application comprising code segments and execution location markers which return indicators identifying behavior of the code segments in response to receiving a request to process the application. The example system includes an application manager engine to receive the request and pass the request to the application. The example system includes the application manager engine including an awareness builder engine to: receive from the application, a response to the request that includes the indicators identifying the behavior of the code segments; store the indicators local to the application manager engine; and transmit the response.

Abstract: An example system includes a source code change engine to: retrieve a source code change location in an application, as maintained at a first database. The example system further includes: a source code test location engine to: retrieve a source code test location, tested by a regression test, as maintained at a second database in association with the regression test. The example system further includes: a regression test selection engine to: select the regression test to test the application based on comparing the source code change location for the application with the source code test location associated with the regression test. The example system further includes: a regression test engine to: execute the regression test, as selected, on the source code test location of the application; and in response to the application passing the regression test, return an indication of passing the regression test.

Abstract: An example system includes: an application engine comprising code segments and execution location markers which return time indicators identifying times to implemented the code segments; a circuit breaker (CB) awareness builder engine to: receive from the application engine, the time indicators; and store the time indicators; a CB awareness engine to: receive a request to process the application engine; retrieve, via the CB awareness builder engine, the time indicators; determine whether a code segment is open or closed based on the time indicators; modify the request to include CB indications of respective code segments of the application engine that are open; and provide the request, as modified to include the CB indications, to the application engine to cause the application engine to return an exception for open code segments in response to receiving the request, as modified to include the CB indications.

Abstract: Examples are described herein of methods for generating a graph from a plurality of logs from microservices. In some examples, a method includes generating nodes of a graph based on a plurality of logs from microservices. In some examples, a method includes generating edges of the graph based on a sequence of the plurality of logs.