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 2024.
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:
- The main Kubernetes cluster - one basic monitor
- 5 nodes - 10 basic monitors
- 200 pods - 40 basic monitors
- 51 deployments - 11 basic monitors
- 53 ReplicaSets - 11 basic monitors
- 40 DaemonSets - 8 basic monitors
- 200 containers - 40 basic monitors
Related Links:
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. Your RUM license limit is reset at the start of every month. Please check the below list for ...
Licensing for Docker (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 ...
Add Node.js agent in Kubernetes via InitContainers (using prebuilt agent image)
To integrate the APM Insight Node.js agent into your Kubernetes applications using InitContainers, follow the steps given below: Step 1: Create an empty volume that will be used to copy the agent files during the initContainers process. Example: ...
Troubleshooting false positive alerts in monitoring
Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...
How does Site24x7 always ensure the availability of its location agents during monitoring?
Site24x7 uses a preferred location recheck logic in the back-end to ensure the availability of all monitoring locations. This logic is only applied when you've disabled the option "Restrict monitoring within selected locations" in the Add or Edit ...