Search All Patents in Edge Computing
Patent US10303576
Issued 2019-05-28
Systems And Methods For It Intelligence And Management Based On Container-level Metering
Systems and methods for containerized IT intelligence and management. In one embodiment, a system for containerized IT financial management comprises at least one collector, at least one meter, at least one connector, and a reporting dashboard. The at least one collector is customized and connected to at least one container platform. The at least one collector sends capacity and consumption metrics to the at least one meter for processing and aggregation.
Much More than Average Length Specification
View the Patent Matrix® Diagram to Explore the Claim Relationships
USPTO Full Text Publication >
- 1. A system for containerized Information Technology (IT) intelligence and management, comprising:
a meter platform and at least one analytics platform; wherein the meter platform comprises at least one collector, at least one meter application programming interface (API), and at least one connector; wherein the at least one collector comprises an infrastructure collector container, an inventory collector container, a metrics collector container, a local database container, and an on-premises connector; wherein the at least one collector is customized for at least one container application platform with information comprising an infrastructure name, a domain name, a log level, whether to use an Secure Sockets Layer (SSL), whether to verify the SSL, a Kubelet port, a Docker Cgroup namespace, a data age period, a default Local Area Network (LAN) Input/Output (I/O), a default Wide Area Network (WAN) I/O, and a default Disk I/O; wherein the infrastructure name is a unique name to be applied to a container cluster in a container environment, wherein the domain name is for a dedicated cluster in the container environment, wherein the log level indicates a verbosity of a collector log, wherein whether to use an SSL indicates access to a Kubernetes API over the SSL or not, wherein whether to verify the SSL indicates verifying a Kubernetes SSL certificate or not, wherein the Kubelet port is a port that a Kubernetes API pod is listening on, wherein the data age period is an age period of data for clean cache, wherein the default LAN I/O is a fallback value for LAN I/O speed per node if the at least one collector cannot determine an actual LAN speed, wherein the default WAN I/O is a fallback value for WAN I/O speed per node if the at least one collector cannot determine an actual WAN speed, and wherein the default Disk I/O is a fallback value for disk I/O speed per node if the collector cannot determine the actual disk speed; wherein the at least one meter API comprises a Workload Allocation Cube (WAC) calculator container, wherein the at least one meter API is configured with information comprising an organization ID, an Open Authorization token, a host address, a port, whether to use an SSL for the at least one meter API, and whether to verify the SSL for the at least one meter API; wherein the inventory collector container is operable to retrieve a list of application containers for metering from each container application platform, wherein the list of application containers is updated as application containers are added or removed for consumption; wherein the local database container is operable to store the list of application containers, a metered state of each application container in the list of application containers, and associated metadata; wherein the metrics collector container is operable to collect sample data of processor usage, memory usage, storage usage, Disk I/O, LAN I/O, and WAN I/O from application containers not metered yet; wherein the on-premises connector is operable to transmit the sample data to the at least one meter API; wherein the at least one meter API is configured to measure consumption of the at least one container application platform based on the sample data, thereby creating meter data; wherein the at least one connector is configured to extract, transform, and load the meter data to the at least one analytics platform; and wherein the at least one analytics platform is configured to track computing resource usage, provide insight into the computing resource usage, and optimize the computing resource usage of the at least one container application platform in real time.
- 17. A system for containerized Information Technology (IT) intelligence and management, comprising:
at least one collector, at least one meter, and at least one connector, and at least one analytics platform; wherein the at least one collector comprises an infrastructure collector container, an inventory collector container, a metrics collector container, a local database container, and an on-premises connector; wherein the at least one collector is customized for at least one container application platform, with information comprising an infrastructure name, a domain name, a log level, whether to use an Secure Sockets Layer (SSL), whether to verify the SSL, a Kubelet port, a Docker Cgroup namespace, a data age period, a default Local Area Network (LAN) Input/Output (I/O), a default Wide Area Network (WAN) I/O, and a default Disk I/O; wherein the infrastructure name is a unique name to be applied to a container cluster in a container environment, wherein the domain name is for a dedicated cluster in the container environment, wherein the log level indicates a verbosity of a collector log, wherein whether to use an SSL indicates access to a Kubernetes API over the SSL or not, wherein whether to verify the SSL indicates verifying a Kubernetes SSL certificate or not, wherein the Kubelet port is a port that a Kubernetes API pod is listening on, wherein the data age period is an age period of data for clean cache, wherein the default LAN I/O is a fallback value for LAN I/O speed per node if the at least one collector cannot determine an actual LAN speed, wherein the default WAN I/O is a fallback value for WAN I/O speed per node if the at least one collector cannot determine an actual WAN speed, and wherein the default Disk I/O is a fallback value for disk I/O speed per node if the collector cannot determine the actual disk speed; wherein the at least one meter comprises at least one meter application programming interface (API), wherein each of the at least one meter API comprises a Workload Allocation Cube (WAC) calculator container, wherein the at least one meter API is configured with information comprising an organization ID, an Open Authorization token, a host address, a port, whether to use an SSL for the at least one meter API, and whether to verify the SSL for the at least one meter API; wherein the inventory collector container is operable to retrieve a list of application containers for metering from each container application platform, wherein the list of application containers is updated as application containers are added or removed for consumption; wherein the local database container is operable to store the list of application containers, a metered state of each application container in the list of application containers, and associated metadata; wherein the metrics collector container is operable to collect sample data for processor usage, memory usage, storage usage, Disk I/O, LAN I/O, and WAN I/O from application containers not metered yet; wherein the on-premises connector is operable to transmit the sample data to the at least one meter API; wherein the at least one meter is configured to measure consumption of the at least one container application platform based on the sample data from the at least one collector, thereby creating meter data; wherein the at least one connector is configured to extract, transform, and load the meter data to the at least one analytics platform; and wherein the at least one analytics platform is configured to track computing resource usage, provide insight into the computing resource usage, and optimize the computing resource usage of the at least one container application platform in real time.
- 18. A method for containerized Information Technology (IT) intelligence and management, comprising:
providing at least one collector, at least one meter, at least one connector, and at least one analytics platform, wherein the at least one collector is customized for at least one container application platform, wherein the at least one collector comprises an infrastructure collector container, an inventory collector container, a metrics collector container, a local database container, and an on-premises connector, wherein the at least one meter comprises at least one meter application programming interface (API), wherein each of the at least one meter API comprises a Workload Allocation Cube (WAC) calculator container; customizing the at least one collector for at least one container application platform with information comprising an infrastructure name, a domain name, a log level, whether to use an Secure Sockets Layer (SSL), whether to verify the SSL, a Kubelet port, a Docker Cgroup namespace, a data age period, a default Local Area Network (LAN) Input/Output (I/O), a default Wide Area Network (WAN) I/O, and a default Disk I/O; wherein the infrastructure name is a unique name to be applied to a container cluster in a container environment, wherein the domain name is for a dedicated cluster in the container environment, wherein the log level indicates a verbosity of a collector log, wherein whether to use an SSL indicates access to a Kubernetes API over the SSL or not, wherein whether to verify the SSL indicates verifying a Kubernetes SSL certificate or not, wherein the Kubelet port is a port that a Kubernetes API pod is listening on, wherein the data age period is an age period of data for clean cache, wherein the default LAN I/O is a fallback value for LAN I/O speed per node if the at least one collector cannot determine an actual LAN speed, wherein the default WAN I/O is a fallback value for WAN I/O speed per node if the at least one collector cannot determine an actual WAN speed, and wherein the default Disk I/O is a fallback value for disk I/O speed per node if the collector cannot determine the actual disk speed; configuring the at least one meter API with information comprising an organization ID, an Open Authorization token, a host address, a port, whether to use an SSL for the at least one meter API, and whether to verify the SSL for the at least one meter API; the inventory collector container retrieving a list of application containers for metering from each container application platform, wherein the list of application containers is updated as application containers are added or removed for consumption; the local database container storing the list of application containers, a metered state of each application container in the list of application containers, and associated metadata; the metrics collector container collecting sample data of processor usage, memory usage, storage usage, Disk I/O, LAN I/O, and WAN I/O from application containers not metered yet; the on-premises connector transmitting the sample data to the at least one meter; the at least one meter measuring consumption of the at least one container application platform based on the sample data, thereby creating meter data; the at least one connector extracting, transforming, and loading the meter data to the at least one analytics platform; and the at least one analytics platform tracking computing resource usage, providing insight into the computing resource usage, and optimizing the computing resource usage of the at least one container application platform based on the meter data in real time.
