Licensing for Kubernetes Monitoring

Licensing for Kubernetes monitoring

 The main Kubernetes cluster is considered one basic monitor. For the other components, the licensing is done as follows: 

Component
Licensing
Nodes
1 monitor consumes one basic license
Pods
5 monitors consume one basic license
Containers
5 monitors consume one basic license
Services
5 monitors consume one basic license
DaemonSets
5 monitors consume one basic license
Jobs
5 monitors consume one basic license
Horizontal Pod Scaler (HPA)
5 monitors consume one basic license
Controllers
5 monitors consume one basic license
ReplicaSets
5 monitors consume one basic license
StatefulSets
5 monitors consume one basic license
Persistent Volume Claim (PVC)
5 monitors consume one basic license
Persistent Volumes (PV)
5 monitors consume one basic license
Endpoints and ConfigMaps
free license 

For example, consider a Kubernetes set up having 5 nodes, 200 pods, 51 deployments, 53 ReplicaSets, 40 DaemonSets, and 200 containers. This would consume a total of 116 basic monitors. The split-up will be like the following:
  1. The main Kubernetes cluster - one basic monitor
    1. 5 nodes - 5 basic monitors
    2. 200 pods - 40 basic monitors
    3. 51 deployments - 11 basic monitors
    4. 53 ReplicaSets - 11 basic monitors
    5. 40 DaemonSets - 8 basic monitors 
    6. 200 containers - 40 basic monitors 


   

   

    • Related Articles

    • How do I monitor specific resource types like Pods, Containers, and Deployments?

      To monitor specific resource types of Kubernetes like Pods, Containers, and Deployments:   Log in to your Site24x7 account. Go to Admin > Inventory > Configuration Rules. Click Add Rule. Enter a proper Display Name and Description. Define the ...
    • Why is No Data shown for the Pod metrics?

      In your Site24x7 web client (Server > Kubernetes > Pods > select the Pod monitor > click Performance), you might get No Data for metrics such as CPU Limit and Requests, Memory Limit and Requests, CPU Utilization, and Memory Utilization (%) as shown ...
    • Comparison between Site24x7 VMware Monitoring and VM monitoring using Site24x7 server agent

      Site24x7 VMware Monitoring capabilities Site24x7 VMware monitoring is agentless. An On-Premise Poller acts as a probe to collect data and sends it to Site24x7. With Site24x7 VMware Monitoring, you will be able to: Monitor vCenter Monitor VMware ...
    • How to host Site24x7 docker image into my private container registry

      To host Site24x7 docker image into your private container registry, use the following steps: Log into your Cloud Container Registry in the terminal using the below command: docker login <ur_container_registry_login_server> Enter your username and ...
    • Ignore transactions from monitoring

      To ignore or drop transactions from monitoring by the APM Insight PHP agent, follow the below-given steps. Install APM Insight PHP agent in your application and add a configuration file /opt/zpa/conf/transaction_drop_patterns.conf Add transaction ...