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
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, ...
Exclude the selective SSH algorithms in On-Premise Poller during SFTP Transfer monitoring
By excluding SSH algorithms, you can restrict Site24x7 SSH Client from using the excluded algorithm while connecting to the SSH server during SFTP Transfer monitoring. Follow the steps mentioned below for SSH algorithm exclusion in On-Premise Poller ...
How do I monitor an Oracle database hosted in a Docker container in the same machine?
To monitor your Oracle Database hosted in a Docker container, follow these steps: Log in to Site24x7 and install the Site24x7 Linux monitoring agent. Execute the following command in your terminal and enter your Oracle Database instance's username ...
Response time in Website monitoring
In website monitoring, response time is calculated as the total time taken to resolve the DNS, complete the TCP hand-shake, negotiate an SSL handshake (for HTTPS) and download the full HTML output from the server. However, it does not include getting ...
Difference between website monitoring and REST API monitoring
Website monitoring allows you to monitor your websites and web applications to ensure that they are up and running. Website monitor verifies the availability of specified, addressable, standard HTTP and HTTPS URLs from over 100+ global locations and ...