ARCHITECTURE FOR MONITORING METRICS OF NETWORK MANAGEMENT SYSTEM

1 . A method for monitoring a multi-tenant network management system deployed in a public cloud to manage a plurality of groups of datacenters, the method comprising:

for each datacenter group of a plurality of datacenter groups managed by the multi-network management system, wherein each respective datacenter group comprises one or more datacenters of a respective tenant that defines the datacenter group:

deploying a set of network management service instances in the cloud specified by the tenant for the datacenter group, each of the network management service instances providing a specified service to the datacenters of the datacenter group; and

deploying a metric monitoring service instance in the cloud for the datacenter group, the metric monitoring service instance for collecting and analyzing metrics from services belonging to each of the network management service instances deployed for the datacenter group, wherein the metric monitoring service instance comprises an anomaly detection microservice that analyzes collected flow data to identify anomalous behavior in network traffic and generates alerts based on the anomalous behavior.

2 . The method of claim 1 , wherein the network management system is deployed within a Kubernetes cluster in a public cloud.

3 . The method of claim 2 , wherein:

each respective network management service instance is deployed in a separate respective namespace of the Kubernetes cluster; and

each respective metric monitoring service instance is deployed in a respective namespace that is separate from the namespaces of the network management service instances and the other metric monitoring service instances.

4 . The method of claim 3 , wherein:

metrics collection agents are deployed in each of the namespaces of the network management service instances; and

each metrics collection agent collects metrics from one or more services in the same namespace as the metrics collection agent and provides the collected metrics to the metric monitoring service for the datacenter group that is managed by the network management service instance to which the metrics collection agent is deployed.

5 . The method of claim 1 , wherein the method is performed by a multi-tenant deployment service that is accessible to the each of the respective tenants that defines a respective datacenter group.

6 . The method of claim 1 , wherein each respective metric monitoring service instance for a respective datacenter group is further for collecting and analyzing metrics from services belonging to the metric monitoring service for the respective datacenter group.

7 . The method of claim 1 , wherein the set of network management service instances for a particular datacenter group comprises at least (i) a policy management service instance that manages network policy for the particular datacenter group and (ii) a network monitoring service instance that performs flow collection and monitoring for the particular datacenter group.

8 . The method of claim 1 , wherein the sets of network management service instances comprise at least two service instances of a same type of service instance, each of the at least two service instances performing the same service for a different respective datacenter group.

9 . The method of claim 1 , wherein at least two sets of network management service instances comprise different types of service instances.

10 . The method of claim 1 , wherein:

the public cloud is a first public cloud; and

a particular datacenter group of a particular tenant comprises at least (i) a physical on-premises datacenter belonging to the tenant and (ii) a virtual datacenter implemented 4 in a second public cloud.

11 . The method of claim 10 , wherein the first and second public clouds are different cloud datacenters of a same public cloud provider.

12 . The method of claim 10 , wherein the first and second public clouds are a same public cloud datacenter.

13 . The method of claim 1 , wherein the collected metrics for a particular service comprise at least one of API response time for a particular API call, memory usage, CPU usage, execution time for a particular process, and execution time for a particular RPC call.

14 . A non-transitory machine-readable medium storing a program which when executed by at least one processing unit deploys entities for monitoring a multi-tenant network management system that is deployed in a public cloud to manage a plurality of groups of datacenters, the program comprising sets of instructions for:

for each datacenter group of a plurality of datacenter groups managed by the multi-network management system, wherein each respective datacenter group comprises one or more datacenters of a respective tenant that defines the datacenter group:

deploying a set of network management service instances in the cloud specified by the tenant for the datacenter group, each of the network management service instances providing a specified service to the datacenters of the datacenter group; and

deploying a metric monitoring service instance in the cloud for the datacenter group, the metric monitoring service instance for collecting and analyzing metrics from services belonging to each of the network management service instances deployed for the datacenter group, wherein the metric monitoring service instance comprises an anomaly detection microservice that analyzes collected flow data to identify anomalous behavior in network traffic and generates alerts based on the anomalous behavior.

15 . The non-transitory machine-readable medium of claim 14 , wherein:

the network management system is deployed within a Kubernetes cluster in a public cloud;

each respective network management service instance is deployed in a separate respective namespace of the Kubernetes cluster; and

each respective metric monitoring service instance is deployed in a respective namespace that is separate from the namespaces of the network management service instances and the other metric monitoring service instances.

16 . The non-transitory machine-readable medium of claim 15 , wherein:

metrics collection agents are deployed in each of the namespaces of the network management service instances; and

each metrics collection agent collects metrics from one or more services in the same namespace as the metrics collection agent and provides the collected metrics to the metric monitoring service for the datacenter group that is managed by the network management service instance to which the metrics collection agent is deployed.

17 . The non-transitory machine-readable medium of claim 14 , wherein each respective metric monitoring service instance for a respective datacenter group is further for collecting and analyzing metrics from services belonging to the metric monitoring service for the respective datacenter group.

18 . The non-transitory machine-readable medium of claim 14 , wherein the set of network management service instances for a particular datacenter group comprises at least (i) a policy management service instance that manages network policy for the particular datacenter group and (ii) a network monitoring service instance that performs flow collection and monitoring for the particular datacenter group.

19 . The non-transitory machine-readable medium of claim 14 , wherein the sets of network management service instances comprise at least two service instances of a same type of service instance, each of the at least two service instances performing the same service for a different respective datacenter group.

20 . The non-transitory machine-readable medium of claim 14 , wherein at least two sets of network management service instances comprise different types of service instances.

21 . The non-transitory machine-readable medium of claim 14 , wherein:

the public cloud is a first public cloud; and

a particular datacenter group of a particular tenant comprises at least (i) a physical on-premises datacenter belonging to the tenant and (ii) a virtual datacenter implemented in a second public cloud.