Container monitoring configuration deployment

1. A method comprising:

determining, by a monitoring server external to a container cluster environment, that a new container has been added to the container cluster environment;

receiving, by the monitoring server, metadata of the new container from the new container;

comparing, by the monitoring server, the metadata of the new container to a plurality of configuration templates for monitoring metrics related to operation of the new container, wherein the plurality of configuration templates is stored on the monitoring server;

determining, by the monitoring server, a configuration template from the plurality of configuration templates appropriate for monitoring the metrics related to the operation of the new container based on the comparison;

customizing, by the monitoring server, the configuration template for the new container by modifying a template path of the configuration template with the metadata of the new container; and

subsequent to customizing the configuration template, deploying the configuration template for the monitoring server to monitor the metrics related to the operation of the new container.

2. The method of claim 1 wherein deploying the configuration template comprises:

generating a new group of monitors for the new container using monitoring policies defined in the configuration template.

3. The method of claim 1 comprising:

determining, by the monitoring server, that a first container is no longer running on the container cluster environment; and

removing the first container from a group of the monitoring server.

4. The method of claim 1 wherein determining that the new container has been added comprises:

determining whether a group of monitors belonging to a plurality of groups corresponding to the new container exists; and

enabling the group of monitors for the new container in response to a determination that the group of monitors corresponding to the new container exists.

5. The method of claim 1 wherein the metadata of the new container is received using a standardized application programming interface.

6. The method of claim 1 , wherein the metadata of the new container includes an image name and a container name of the new container, and wherein comparing the metadata of the new container to the plurality of configuration temples comprises:

mapping the image name of the new container to a plurality of container image names included in the plurality of configuration templates; and

mapping the container name of the new container to the plurality of container image names included in the plurality of configuration templates.

7. The method of claim 1 wherein the container cluster environment includes a first container deployed by a first container deployment tool and a second container deployed by a second container deployment tool.

8. The method of claim 7 comprising:

retrieving, by the monitoring server, monitoring metrics from the first container and the second container belonging to the container cluster environment using a standardized application programming interface (API); and

combining the monitoring metrics from the first container and the second container into a unified view for display on an output device, wherein the monitoring server uses the standardized API to directly access the first container and the second container and ignore added management layers of the first and second container deployment tools.

9. The method of claim 1 wherein the metadata of the new container includes an image name of the new container.

10. The method of claim 1 further comprising:

receiving metrics from a cluster manager layer, node layer, container daemon layer, containers layer, and application layer of the new container.

11. A system comprising:

a processor; and

a memory storing instructions that are executable to cause the processor to:

determine that a new container has been added to a container environment;

receive metadata of the new container from the new container;

match the metadata of the new container to a plurality of configuration files to determine a configuration file for monitoring metrics related to operation of the new container;

determine a template for monitoring the metrics related to the operation of the new container corresponding to the configuration file;

customize the template for the new container by modifying a template path of the template with the metadata of the new container; and

subsequent to customizing the template, deploy the template for the processor to monitor the metrics of the operation the new container.

12. The system of claim 11 wherein the metadata of the new container identifies a deployment manager of the new container.

13. The system of claim 11 , wherein the metadata of the new container includes an image name and a container name of the new container, and wherein the instructions are further executable to cause the processor to:

map the image name of the new container to a plurality of container image names included in a plurality of configuration templates; and

map the container name of the new container to the plurality of container image names included in the plurality of configuration templates.

14. The system of claim 11 wherein the instructions are further executable to cause the processor to:

receive monitoring metrics from a first container and a second container belonging to the container environment using a standardized application programming interface (API); and

combine the monitoring metrics from the first container and the second container into a unified view for display on an output device, wherein the processor uses the standardized API to directly access the first container and the second container and ignore added management layers of first and second container deployment tools used to deploy the first and second containers, respectively.

15. A non-transitory machine-readable storage medium encoded with instructions, the instructions executable to cause a processor of a monitoring system to:

determine that a new container has been added to a container environment;

receive metadata of the new container from the new container;

compare the metadata of the new container to a plurality of configuration templates for monitoring metrics related to operation of the new container, wherein the plurality of configuration templates is external to the container environment, wherein each configuration template includes corresponding container monitoring policy information;

determine a configuration template from the plurality of configuration templates appropriate for monitoring the metrics of the operation of the new container based on the comparison;

customize the configuration template for the new container by modifying a template path of the configuration template with the metadata of the new container; and

subsequent to customizing the configuration template, deploy the configuration template for the monitoring system to monitor the metrics related to the operation of the new container using the container monitoring policy information corresponding to the configuration template.

16. The non-transitory machine-readable storage medium of claim 15 , wherein the instructions are further executable to cause the processor of the monitoring system to:

determine that a first container is no longer running in the container environment, wherein the container environment includes a plurality of containers, each container having a corresponding group on the monitoring system; and

disable a first group of the monitoring system corresponding to the first container.

17. The non-transitory machine-readable storage medium of claim 15 , wherein the instructions are further executable to cause the processor of the monitoring system to:

determine whether a group of monitors corresponding to the new container exists; and

enable the group of monitors for the new container in response to a determination that the group of monitors corresponding to the new container exists.

18. The non-transitory machine-readable storage medium of claim 15 , wherein the metadata of the new container includes an image name and a container name of the new container, and wherein the instructions are further executable to cause the processor of the monitoring system to:

map the image name of the new container to a plurality of container image names included in the plurality of configuration templates; and

map the container name of the new container to the plurality of container image names included in the plurality of configuration templates.

19. The non-transitory machine-readable storage medium of claim 15 , wherein the instructions are further executable to cause the processor of the monitoring system to:

receive monitoring metrics from a first container and a second container belonging to the container environment using a standardized application programming interface (API), wherein the first container is deployed by a first container deployment tool and the second container is deployed by a second container deployment tool; and

combine the monitoring metrics from the first container and the second container into a unified view for display on an output device, wherein the processor uses the standardized API to directly access the first container and the second container and ignore added management layers of the first and second container deployment tools.