Analytic model execution engine with instrumentation for granular performance analysis for metrics and diagnostics for troubleshooting

1. A system, comprising:

an interface;

a processor configured to:

receive, at the interface, an analytic model for processing; an input data stream;

inspect the analytic model to determine a programming language of the analytic model, an action to be performed on the input data stream, a type of the input data stream, and a type of an output data stream;

generate a virtualized execution environment (VEE), the VEE including executable code to implement the analytic model, the implemented analytic model for processing the input data stream;

add, at runtime of the VEE, a sensor to instrument the implemented analytic model, wherein the sensor is configured to instrument the VEE for an analytic engine, wherein the sensor provides metrics for debugging a performance of the analytic model;

debug the performance of the analytic model until the analytic engine is optimized and at least one bug is eradicated from the analytic model; and

remove the sensor via the interface after a determination that the sensor is no longer required for the debugging; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system recited in claim 1 , wherein the analytic model is implemented using a container to provide the VEE for the analytic engine.

3. The system recited in claim 2 , wherein the container is a portable and independently executable microservice.

4. The system recited in claim 1 , wherein the analytic model includes an input configuration schema that specifies the type of the input data stream, an output configuration schema that specifies the type of the output data stream, and an I/O descriptor abstraction that specifies abstracts the input data stream type.

5. The system recited in claim 1 , wherein the VEE includes a plurality of runtime engines that each supports a distinct analytic model programming language.

6. The system recited in claim 4 , wherein the processor is further configured to:

bind the analytic model and the I/O descriptor abstraction;

receive the input data stream at a stream processor;

process the input data stream using the executable code that implements the analytic model, wherein the stream processor enforces the type of the input data stream; and

generate the output data stream using the stream processor based on the type of the output data stream, wherein the output data stream includes a score and/or a metric.

7. The system recited in claim 1 , wherein the interface for receiving the analytic model includes an Application Programming Interface (API), a Command Line Interface (CLI), and/or a dashboard interface.

8. The system recited in claim 5 , wherein the analytic model is coded in a first programming language, and wherein the processor is further configured to:

translate the first programming language to a first analytic model programming language; and

route the executable code to one of the plurality of runtime engines based on the first analytic model programming language.

9. A method, comprising:

receiving at an interface an analytic model for processing an input data stream;

inspecting the analytic model to determine a programming language of the analytic model, an action to be performed on the input data stream, a type of the input data stream, and a type of an output data stream;

generating a virtualized execution environment (VEE), the VEE including executable code to implement the analytic model, the implemented analytic model for processing the input data stream;

adding, at runtime of the VEE, a sensor to the implemented analytic model, the sensor to instrument the VEE for an analytic engine, wherein the sensor provides metrics for debugging a performance of the analytic model;

debugging the performance of the analytic model until the analytic engine is optimized and at least one bug is eradicated from the analytic model; and

removing the sensor via the interface after determining that the sensor is no longer required for the debugging.

10. The method of claim 9 , wherein the analytic model is implemented using a container to provide the VEE for the analytic engine.

11. The method of claim 10 , wherein the container is a portable and independently executable microservice.

12. The method of claim 9 , wherein the analytic model includes an input configuration schema that specifies the type of the input data stream, an output configuration schema that specifies the type of the output data stream, and an I/O descriptor abstraction that abstracts the input data stream type.

13. The method of claim 9 , wherein the VEE for the analytic engine includes a plurality of runtime engines that each supports a distinct analytic model language.

14. A computer program product, the computer program product being embodied in a tangible non-transitory computer readable storage medium and comprising computer instructions for:

receiving at an interface an analytic model for processing an input data stream;

inspecting the analytic model to determine a programming language of the analytic model, an action to be performed on the input data stream, a type of the input data stream, and a type of an output data stream;

generating a virtualized execution environment (VEE), the VEE including executable code to implement the analytic model, the implemented analytic model for processing the input data stream;

adding, at runtime of the VEE, a sensor to the implemented analytic model, the sensor to instrument the VEE for an analytic engine, wherein the sensor provides metrics for debugging a performance of the analytic model;

debugging the performance of the analytic model until the analytic engine is optimized and at least one bug is eradicated from the analytic model; and

removing the sensor via the interface after determining that the sensor is no longer required for the debugging.

15. The computer program product recited in claim 14 , wherein the analytic model is implemented using a container to provide the VEE for the analytic engine.

16. The computer program product recited in claim 15 , wherein the container is a portable and independently executable microservice.

17. The computer program product recited in claim 14 , wherein the analytic model includes an input configuration schema that specifies the type of the input data stream, an output configuration schema that specifies the type of the output data stream, and an I/O descriptor abstraction that abstracts the input data stream type.

18. The computer program product recited in claim 14 , wherein the VEE for the analytic engine includes a plurality of runtime engines that each supports a distinct analytic model language.