Get started with a 30-day free trial.

Location is generally a set of geographically diverse points where the servers receive the response for the defined monitors.

Primary location is the main location from which the defined monitors are polled from. When this location detects a downtime, the polling happens also from the secondary location, which helps to exclude false alerts.

The secondary monitoring location serves as a backup or supplementary checkpoint for validation and redundancy. Employing multiple monitoring locations improves the scope of coverage and the dependability of monitoring services.

To conduct monitoring from additional locations beyond those supported by your package, you can utilize supplementary check add-ons. These add-ons enable you to perform extra location checks and decrease the polling frequency for secondary locations compared to those provided in your package.

For instance, suppose you have a monitor with a secondary polling frequency of 30 minutes and eight included locations in your plan. If you wish to monitor every five minutes from all your secondary locations, the total polling that would occur from the eight locations within an hour would be 8 * 12, out of which 8 * 2 will be complimentary.

We have run-based pricing for Web Page Speed and Real Browser Monitors (RBMs). Each monitor runs in each location and will be counted as a check.

Let us say, there are 1,440 checks allowed for a plan. You can use it as 288, 5-minute checks per monitor per day for five days, or split it across WPA or RBMs in your account.

Monitor-based pricing is about the three types of monitors, basic, host and advanced monitors that we support in this new pricing version.

Check-based pricing allows you to adjust your location count and polling frequency. With this option, you can increase the number of locations and decrease the polling frequency compared to the defaults provided in your plan.

For website monitor, with a minimum poll frequency of 1 minute from the primary location and seven secondary locations polling at a 30-minute frequency is allowed with the basic monitor license. Say, if you have a requirement to monitor the website at a 1-minute poll frequency from all eight locations, it will be allowed through the Additional Check-based add-on. Following this way, you can calculate the additional checks required:

Total runs: 60 checks/hr * 24 hrs/day * 30 days/month * 8 locations = 3,45,600 checks

Allowed via Basic monitor: 60 checks/hr (Primary) * 24 hrs/day & 30 days/month + 2 checks/hr (Secondary) * 24 hrs/day * 30 days/month * 7 (Secondary locations) = 53,280

Additional checks required = 3,45,600 - 53,280 = 2,92,320 checks / month

The default polling frequency of monitors aligns with the plans selected. Users have the option to adjust the polling frequency for websites to a minimum interval of 30 seconds, which will require two basic licenses. However, for the on-premise poller, the frequency is fixed at 5 minutes.

In real browser monitoring, a transaction is a series of steps in a monitored web application, crucial for assessing user experience and identifying performance issues. A synthetic run with a Real Browser Monitoring (RBM) tool refers to a simulated test-run within a web browser to evaluate system performance. Combining these, one transaction equals one synthetic run, meaning each monitored transaction represents a simulated test-run in real browser monitoring. Conducting synthetic runs ensures the reliability of a RBM, to optimize remote monitoring for a seamless user experience.

Synthetic run license is supported for transaction monitors (RBMs) and Web Page Speed browser.

In the advanced monitoring license, you can add a WPA/RBM monitor, which will conduct polling at 8/16 locations based on your plan, either every 30 seconds or every minute. Opting for a synthetic run-based license allows you to conduct up to 10,000 checks for a monitor. Additionally, you have the flexibility to allocate this run-based license across multiple advanced monitors.

If a user has numerous WPA or RBM monitors with multiple location checks to execute, opting for a run-based license would prove more cost-effective. The advanced license included in your package can then be utilized for adding other advanced monitors based on your requirement.

Our RBM and Web Page Speed monitors simulate how actual users experience your website. These monitors are typically categorized as advanced or use a check-based pricing model.

Root cause analysis (RCA) is an in-depth analysis to ascertain the actual reason behind a downtime incident. Pinpointing the root cause helps reduce the resolution time and ensure smooth running of your websites or applications.

All plans include a detailed RCA report, however video RCA is exclusive to the Enterprise plan.

Each webpage loaded in the browser is counted as a page view, regardless of the quantity of resources loaded in the background.

RUM is licensed based on the number of page views. Users have to purchase page views to use RUM monitor.

Agent-based involves software installed on a device (like an agent) which gathers performance data and sends it to a central server for analysis and alerts.

Agent-based monitoring includes:

• Windows Server Monitoring
• Linux Server Monitoring
• FreeBSD Server Monitoring
• OS X Server Monitoring

Agentless monitoring includes:

• HP Server Monitoring
• IBM Server Monitoring
• Solaris Server Monitoring
• SNMP Server Monitoring
• WMI Server Monitoring
• VMware (VMs/ESX/ESXi hosts/Clusters)
• NutanixHosts (VMs/Clusters)
• Kubernetes Nodes
• Azure VMs
• GCP Compute
• Cloud AWS EC2 instances

Agentless refers to fetching performance data from the servers using existing protocols and APIs, without having to install an agent.

Both agent-based and agentless are counted as host monitors.

Plugins are custom scripts or integrations that can be used to monitor various aspects of your IT infrastructure or applications beyond the standard monitoring capabilities provided by Site24x7. These plugins allow you to gather specific metrics or perform custom checks.

Each plugin with 25 specific attributes costs one basic monitor. Adding extra plugins uses your basic monitor licenses. Each plugin can track up to 25 specific aspects (attributes) of your server.

Our monitoring solution autonomously identifies and monitors processes and services running on every host. Moreover, if necessary, you have the option to manually include specific processes or services for monitoring.

Enjoy the capability to monitor up to 25 processes per host at no extra cost with our Professional plan! To monitor beyond 25 processes, a basic license is necessary (covering an additional 25 processes).

With the Enterprise plan, you can monitor up to 50 processes per host for free. Should you require monitoring beyond this limit, additional licenses would be required.

For Docker, the first 10 containers on each host are free. After that, every 10 additional containers require one host monitor license.

For Kubernetes, the main Kubernetes cluster is considered as one basic monitor. For details on additional components, please refer to this article.

Each individual database instance is considered a database host. Let's say if two MySQL instances are running on the same server machine, then it will be considered as two database licenses.

We currently support databases such as MSSQL, MySQL, and PostgreSQL, as well as plugin-based databases like Oracle, Cassandra, MongoDB, ClickHouse, CouchBase, etc.

Each database server consumes an advanced monitor license with which you can monitor 10 databases for free. Additional databases within the server will start consuming one basic monitor license each.

The cloud VMs like AWS EC2, Azure VM, GCP Compute will be monitored in following two ways:

• Agentless monitoring using respective API's: This will help to discover new VM resources added, Auto-scaled environments and hypervisor level resource utilization.
• Agent-based monitoring using Site24x7 server agents: This will help to monitor system resources, process/services, identify dependencies, and self-heal an incident.

For VMware monitoring, VMware Cluster, VMware ESX/ESXi and VMware VM consume one host license each. Datastore and Datastore Snapshots will be Basic monitors.

ESX Hardware will be weightage based monitor where the license depends on number of associated Sensors, one basic monitor license for every 50 Hardware sensors.

vCenter is a free monitor. Monitoring Nutanix clusters, hosts, and VMs in your environment will require a separate host license for each.

Infrastructure events are notifications that signal significant changes or occurrences within your IT environment. These are included at no additional cost.

AWS resources are monitored as host or basic monitors depending on the service type monitored. The number of basic monitor licenses consumed by a service depends on the number of metrics and monitoring complexity. View the list of AWS monitor types.

A child monitor in Site24x7 refers to a supplementary monitoring instance that operates under a primary monitor. It's used to monitor specific aspects or components of a service or application.

Each host operating system (virtual or physical) being monitored counts as one server and consumes one host monitor license.

By default for AWS, you can monitor up to 25 key resources per server, including like containers, and volumes. Should you require monitoring of more, five child monitors will consume one basic license.

For Azure and GCP, you can track up to 25 key resources running in the server including like processes, services, and resource usage within each server. If you need to monitor more than 25 resources on a single server, those additional checks will tap into your basic monitor licenses.

An auto scaling group is a logical collection of EC2 instances grouped together to facilitate scaling. Using Site24x7, you can monitor resource metrics such as CPU usage across the group and set alerts. This allows for informed adjustments to scaling policies based on application workload fluctuations, ensuring instances scale appropriately with changing demands.

If we find more resources than your licensed limit, we typically suspend them and hold them in your account. You can purchase a license and activate it whenever you need to.

Enabling hourly pricing activates these monitors to automatically begin collecting your metrics. You only pay for the period during which your resources are active in your account. You have the option to suspend them if desired.

We will only bill you for the duration that the resource is active, allowing you to monitor multiple resources at the cost of a single host monitor.

For example, under the Professional plan:

• Monitoring an EC2 instance for 1-4 hours daily over 30 days costs $0.72 (calculated as 0.4 hours x $0.006 per hour x 30 days).
• Monitoring an EC2 instance for 6 hours daily over 30 days costs $1.08 (calculated as 6 hours x $0.006 per hour x 30 days).
• The combined cost of EC2 1 and EC2 2 is $1.80, which is lower than the individual per host monitor cost of $2.

With this, you can monitor your resources according to your requirements, such as during business hours, weekends, and other specific times.

No. Our device-based licensing requires a separate license for each monitored device. You can monitor up to 100 network interfaces and one Netflow interface per device. Additionally, the license includes Network Configuration Management (NCM) for managing device configurations.

No. You can increase your monitoring capacity by 500 interfaces by purchasing an additional 50 basic monitor licenses.

If you purchase 100 bundles, you can utilize them in the following ways:

i) Network Interfaces: You can monitor a total of 10,000 network interfaces across all devices. This can be distributed among devices in various combinations.

For example:

• 50 devices with 200 network interfaces each
• 25 devices with 400 network interfaces each
• 20 devices with 500 network interfaces each
• Any other combination that totals up to 10,000 network interfaces, but the devices count should not exceed 100.

ii) NetFlow Interfaces: You can monitor a total of 100 NetFlow interfaces across all devices. Similar to network interfaces, this can be distributed among devices in various combinations.

For example:

• 10 devices with 10 NetFlow interfaces each
• 5 devices with 20 NetFlow interfaces each
• 2 devices with 50 NetFlow interfaces each
• Any other combination that totals up to 100 NetFlow interfaces, but the devices count should not exceed 100.

iii) NCM Devices/IPs: With 100 bundles, you can monitor 100 NCM devices/IPs. This means you can manage the configurations of 100 devices using NCM.

Please note that the allocation of network and NetFlow interfaces can be customized between devices as long as the total does not exceed the limits for each type of interface and the total number of devices does not exceed 100.

Yes, we can install On-Premise Pollers in containers.

Cisco IPSLA monitors and Wireless LAN Controllers (WLCs) are not included in the bundle-based license. You'll need to purchase separate network basic licenses for them.

In Site24x7, we provide plans for MSPs to efficiently monitor multiple accounts through a unified portal. Each monitored account is termed as a "customer."

The MSP can assign a license limit for each customer. If customers are not added individually, they can still collectively utilize monitors up to the MSP's license limit.

Initially, Site24x7 allows users to add nine customers. Additional account monitoring requires purchasing a customer add-on.

For increased monitor capacity, the MSP administrator must purchase additional licenses.

Capping is like setting a limit. It defines the highest point of monitors customers can use within an MSP account.

With capping, customers have a set limit on the number of monitors they can add to their account. Reaching this limit prevents adding any further monitors.

Without capping, all customers under a single MSP account share a pool of available monitors. Each customer can add monitors as long as there's availability within the total pool.

MSP admins can set limits for each customer using the step given below.

Subscriptions > Apply license > Basic, Advanced, Host licenses (you can set limits for each of these monitors for each customer).

Assigning licenses to customer accounts is reserved for MSP admins only. For easy tracking, you can enable the "Show allocation" option to view the licenses distributed to your customers.

The MSP admins will have the permissions to activate or deactivate the customer portals at any given point of time.

For both plans and add-ons, we facilitate automatic renewals for users who make purchases using credit cards and for recurring PayPal users. Furthermore, any customer usage limits established via the Apply license option will be retained and carried forward.