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 two basic licenses
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
Deployments
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
ConfigMaps, Endpoints, and Ingress
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 121 basic monitors. The split-up will be like the following:
  1. The main Kubernetes cluster - one basic monitor
    1. 5 nodes - 10 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

    • Real User Monitoring (RUM) Licensing

      RUM licensing is based on Pageviews. Site24x7 includes RUM in all the plans available. The number of Pageviews and Sites provided differs based on the plan. Please check the below list for more details. Plan type Plan includes Starter 100K RUM ...

    • A few nodes or pods are not discovered for monitoring. Why?

      Check for the below cases if applicable. Case 1: License inadequacy Check if you have adequate licensing. If not, upgrade your license. Case 2: Taint configurations If a few nodes are not discovered for monitoring, it might be because the node has a ...

    • How to uninstall the Site24x7 Kubernetes monitoring agent

      Execute the below commands to uninstall the Site24x7 Kubernetes monitoring agent from your cluster: Deletion command for the DaemonSet agent deployed using a YAML file: kubectl delete -f site24x7-agent.yaml or kubectl delete ds,sa site24x7-agent -n ...

    • How to migrate Kubernetes monitors from one Site24x7 account to another

      Use case An existing Site24x7 user has Kubernetes monitoring in a Site24x7 account and plans to migrate his Kubernetes monitors to a different account. The historic data and the current display name of the Kubernetes monitors will not be migrated. ...

    • Licensing for VMware monitors

      For VMware components, the pricing is as follows: Monitor Licensing vCenter Free VMware Cluster Consumes two basic monitor licenses ESX/ESXi Host Consumes two basic monitor licenses ESX/ESXi Hardware Weightage-based [Consumes one basic monitor ...