Licensing for Kubernetes monitoring
The main Kubernetes cluster is considered one basic monitor. For the other components, licensing is done as follows:
Each node will consume 2 host licenses. The first 10 containers on each host are free. After that, every 10 additional containers require one host monitor license.
Component | Licensing |
Nodes | One node monitor consumes two host license |
Containers | 10 container monitors consume one host license |
Namespaces | Free license |
Pods | Free license |
DaemonSets | Free license |
Jobs | Free license |
Horizontal Pod Autoscaler (HPA) | Free license |
Services | Free license |
ReplicaSets | Free license |
StatefulSets | Free license |
Deployments | Free license |
Persistent Volumes (PV) | Free license |
Persistent Volumes Claim (PVC) | Free license |
ConfigMaps, Endpoints, and Ingress | Free license |
For example, consider a Kubernetes setup having five nodes and 200 containers. This would consume a total of 1 basic monitor and 25 host monitors. The split-up will be as follows:
- The main Kubernetes cluster: One basic monitor
- Five nodes: Ten host monitors
- 200 containers: 15 host monitors (the first 10 container monitors are free with every node monitor)
1 host monitor license = 2 basic monitor licenses
Related Articles
Licensing for Kubernetes monitoring (old)
This article contains the licensing model for the customers who signed up before August 2024. Check out this article for more information on the new licensing pattern. Note that the new licensing model applies to users who signed up after August ...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. ...