Automatic provisioning of monitoring for containerized microservices

1. A computer-implemented method of automatic monitoring of containerized microservices, comprising:

receiving, by a processor, information regarding a microservice executed in one or more containers of a computing cluster in accordance with a configuration dataset for the microservice that is managed by a cluster manager of the computing cluster;

submitting, by the processor, a request to the cluster manager of the computing cluster via an application programming interface (API) for adding one or more configurations specifically for monitoring the microservice to the configuration dataset for the microservice;

as a result of adding the one or more configurations to the configuration dataset for the microservice, receiving monitoring data related to the microservice as the microservice is executed in the one or more containers in accordance with the configuration dataset for the microservice; and

transmitting the monitoring data to a user device associated with the microservice.

2. The computer-implemented method of claim 1 , further comprising

issuing one or more initial requests via the API for data regarding new microservices that have been instantiated or created,

the information being received in response to the one or more initial requests.

3. The computer-implemented method of claim 2 , the one or more initial requests including a first request to determine whether any new microservice has been created followed by a further request to gather details regarding the new microservice.

4. The computer-implemented method of claim 1 , further comprising:

receiving an identifier of a creator of the microservice; and

determining the user device based on the identifier.

5. The computer-implemented method of claim 1 , the one or more configurations indicating a criterion associated with a performance metric for generating an alert, routing information for the alert, an organization or a granularity of a report of the monitoring data, or access privilege information for the report.

6. The computer-implemented method of claim 1 ,

the cluster manager being Kubernetes,

the one or more configurations leading to creating and storing one or more annotations, labels, or namespaces in a configuration file of a service managed by the cluster manager.

7. The computer-implemented method of claim 1 , further comprising:

generating a graphical user interface (GUI) for managing the one or more configurations;

sending instructions to access the GUI to a second user device associated with the microservice;

receiving an update to the one or more configurations via the GUI; and

submitting the update to the cluster manager via the API.

8. The computer-implemented method of claim 1 , further comprising:

managing a plurality of configuration templates of configurations for monitoring microservices;

receiving an instruction to select one or more configuration templates of the plurality of configuration templates; and

obtaining the one or more configurations from the one or more configuration templates.

9. The computer-implemented method of claim 1 , further comprising:

receiving contextual information related to the microservice for the monitoring data, including firewall rules, filtered ports, configurations for a virtual private network (VPN), or file access policies; and

transmitting the contextual information to the user device.

10. The computer-implemented method of claim 1 , the monitoring data including a computing performance metric for each container of the one or more containers.

11. One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause performance of a method of automatic monitoring of containerized microservices, the method comprising:

receiving information regarding a microservice executed in one or more containers of a computing cluster in accordance with a configuration dataset for the microservice that is managed by a cluster manager of the computing cluster;

submitting a request to the cluster manager of the computing cluster via an application programming interface (API) for adding one or more configurations specifically for monitoring the microservice to the configuration dataset for the microservice;

as a result of adding the one or more configurations to the configuration dataset for the microservice, receiving monitoring data related to the microservice as the microservice is executed in the one or more containers in accordance with the configuration dataset for the microservice; and

transmitting the monitoring data to a user device associated with the microservice.

12. The one or more non-transitory storage media of claim 11 , the method further comprising

issuing one or more initial requests via the API for data regarding new microservices that have been instantiated or created,

the information being received in response to the one or more initial requests.

13. The one or more non-transitory storage media of claim 12 , the one or more initial requests including a first request to determine whether any new microservice has been created followed by a further request to gather details regarding the new microservice.

14. The one or more non-transitory storage media of claim 11 , the method further comprising:

receiving an identifier of a creator of the microservice; and

determining the user device based on the identifier.

15. The one or more non-transitory storage media of claim 11 , the one or more configurations indicating a criterion associated with a performance metric for generating an alert, routing information for the alert, an organization or a granularity of a report of the monitoring data, or access privilege information for the report.

16. The one or more non-transitory storage media of claim 11 ,

the cluster manager being Kubernetes,

the one or more configurations leading to creating and storing one or more annotations, labels, or namespaces in a configuration file of a service managed by the cluster manager.

17. The one or more non-transitory storage media of claim 11 , the method further comprising:

generating a graphical user interface (GUI) for managing the one or more configurations;

sending instructions to access the GUI to a second user device associated with the microservice;

receiving an update to the one or more configurations via the GUI; and

submitting the update to the cluster manager via the API.

18. The one or more non-transitory storage media of claim 11 , the method further comprising:

managing a plurality of configuration templates of configurations for monitoring microservices;

receiving an instruction to select one or more configuration templates of the plurality of configuration templates; and

obtaining the one or more configurations from the one or more configuration templates.

19. The one or more non-transitory storage media of claim 11 , the method further comprising:

receiving contextual information related to the microservice for the monitoring data, including firewall rules, filtered ports, configurations for a virtual private network (VPN), or file access policies; and

transmitting the contextual information to the user device.

20. The one or more non-transitory storage media of claim 11 , the monitoring data including a computing performance metric for each container of the one or more containers.