Looking for a guide that can provide more information related to the Site24x7 web client?
Our web client is simple, easy-to-understand, and direct. But, if you need to find more information related to a field, learn how a particular feature can help you, or need to troubleshoot an issue, then the Quick Help section is your answer. With Quick
Tip #60: How to use notification delays to your advantage
We’ve tried our best to engineer Site24x7 so that it doesn't send users any false alerts. However, you would want to delay notifications to you till any home grown scripts that you may have deployed also does not fix the problem. In such scenarios, you can use notification delays. A notification delay is the time gap between when a monitor goes to a Trouble or Down state and the moment you're alerted about it. You can choose to be notified immediately after a single failure, or a bit later after
Tip #64: Track the performance of business-critical transactions by marking them as Key Transactions
The Key Transactions feature allows you to analyze the performance of specific web transactions at a glance. Let's say you want to monitor the metrics of certain transactions, like those made to a payment gateway, login requests, or the action of fetching customer info from the database. In the normal view, you have to dig these metrics out from the bucket of other transactions. Instead, you can mark these transactions as Key Transactions in APM Insight, and view them separately. This helps you to
Tip #63: What should I do if data collection has not been initiated for a RUM application?
If you've added a RUM script in your application but still don't see any data, here's what you need to do. 1. Check if you've added the RUM script properly. To do this, select the RUM tab on the left pane, and then click Summary. Under Step 2, paste the URL of the webpage where you have added the script. If your script has been added properly, you will get a message telling you that data collection will start in a few minutes. If your script has not been added properly, you'll get an error message.
Tip #62: Adding or deleting a user in Site24x7
When you create an account in Site24x7, it's automatically mapped to a Zoho Org account by default. If you're already part of an existing Zoho account and would like to access Site24x7, your access level depends on your role in the Zoho Org account. For example, if your role in Zoho Org is User but you’re a Super Admin in Site24x7, you won't be able to add new users since your Zoho Org role doesn't have this privilege. In this case, you can contact the respective Super Admin at the Zoho Org level
Tip #61: Here's a hassle-free way to import your monitors into Site24x7
If you receive the error message "Your import task has failed" while you're trying to import your monitors into Site24x7, don't worry. You're not alone, and the fix is easy. This error message can occur if you attempt to rewrite default parameters with your previous values. For example, let's say you're importing monitors from account A to account B; the threshold profiles written for account A may not be present in account B, which can trigger this error. To avoid this situation, choose YES to "Overwrite
Tip #59: Share reports to your customers without requiring a login
Site24x7 offers you the flexibility to share reports, including availability reports, performance reports, and any other report on monitor groups or selected monitors, with your customers without requiring them to log in. Additionally, you can embed these reports in your website or on a chosen webpage. Here's how you can do it: Log in to Site24x7 > Reports and choose the required report. Select Share This > Publish Report. Fill out essential details like the report name, resource type, and report
Tip #58: Add your own logo to Site24x7 reports and Status Pages
Did you know that you can customize your Site24x7 reports and Status pages by adding your company logo? You can also include your company name and customize the color theme of your reports. To customize your reports: Log in to your Site24x7 account. Navigate to Admin > Report Settings > Customize reports. Change the logo and other necessary parameters, such as company name, title foreground, and background color etc.. You can also review your changes before saving them. If your changes look good,
Tip #57: How to use Site24x7 On-Premise Poller as another location agent
By default, you can monitor your website's availability from over 100 geographical locations using Site24x7’s website monitors. However, if you want to add a custom monitoring location, you can do so with the help of our On-Premise Poller. Example: Site24x7 has four default monitoring locations in India: Hyderabad, Bangalore, Mumbai, and Chennai. To monitor the performance and availability of your website from any other location within India, you can use Site24x7 On-Premise Poller as a location agent.
Tip #56: Receive instant alerts about network issues with SNMP trap processing
Connectivity issues, high traffic, software issues, and hardware failures—any of these could cause network failure. Sometimes, waiting until the next poll to receive an alert might not be the best option. This is where SNMP trap processing comes into play, allowing you to configure your SNMP devices to send SNMP traps to Site24x7, which instantly processes the traps and sends you alert notifications. You can also set multiple thresholds and rearm conditions for each trap processor to decide when
Tip #55: Understanding the different statuses of APM Insight monitors
We all know that if your application is working fine, it's marked Up. But what about the various other statuses, such as Down and Trouble? Well, here's an overview of the different monitor statuses: Up: Your application is Up if all of your instances are Up. Trouble: Your application is marked Trouble when any of your instances go into the Trouble state.* Critical: Your application is marked Critical when any of your instances go into the Critical state. ** Down: Your application will only be marked
Tip #54: View the total number of visitors on your website using RUM
Apart from monitoring website performance in real time, you can also assess how many people have visited your website during a particular time using Site24x7 Real User Monitoring. The RUM dashboard shows you the number of unique visitors, as illustrated in the figure below. In the image above, we can see that nearly 9,000 people visited this website in the past month, contributing to about 100,000 pageviews. Note: Unique visits are browser-specific. You can read more about pageviews and unique visits
Tip #53: Network Monitoring: Suspend interfaces in bulk using multiple conditions
When you add a switch for monitoring, all its interfaces are added automatically. However, you might not want to monitor all of them, like those not in use (admin state Down), those that aren’t functioning properly (operational state Down), and interfaces of a particular type. You can suspend all these interfaces at once under Network > Settings > Bulk Activate/Suspend Interfaces. Interfaces can be chosen in bulk based on their device, operational state, admin state, status, and type.
Tip #52: How to cross-check if your chosen CDN is working
One best practice in website optimization is to use a content delivery network (CDN) to optimize the loading time of your resources. But what if the resources loaded from a CDN take more time than expected and impact your end-user experience? This is where Site24x7 real user monitoring (RUM) comes in handy. You can inspect the time taken by various resources from respective CDNs across geographies. You can also view where a particular resource is taking more time to load. This helps with determining
Tip #51: Track excessive requests from a single source using Site24x7 AppLogs
Let's take a free, online tool that only receives a few requests per minute as an example. If this tool suddenly starts receiving hundreds of requests per minute, there's a good chance that it's being spammed, and this demands immediate action, such as blocking the particular IP the requests are coming from. With AppLogs Alerts, you can configure and receive alerts when your servers receive too many requests from a single source. When there are too many requests to your IIS server, use the following
Tip #50: Resolve JS errors by analyzing error trends
With Site24x7 RUM, you can contextually debug JS errors by analyzing their frequency over time. This helps you to correlate and narrow down to the root cause of specific issues. Let's look at the example below. From the image above, you can see that the number of Type Errors was initially low. After that, there was a gradual increase and a sudden peak which was subsequently contained. This variation may have been caused by product enhancements, new build updates, or some other change. By viewing
Tip #49: Visualize critical parameters in application dependency maps using Graph Views
Did you know you can view key parameters of your external components as a graph? Previously, connections to external dependencies were depicted in map and tabular views. We've enhanced our reports so you can view parameters for all components, for all hosts corresponding to individual components, and for individual hosts in easy-to-understand graphs. Related articles: Visualize your application topology with application dependency maps
Tip #48: How to monitor AJAX calls in your traditional web applications
For single-page applications, the performance of AJAX calls is monitored with Site24x7 real user monitoring (RUM) by default. These calls are not monitored by default for traditional web apps. Nevertheless, you can still monitor the performance of AJAX calls in your traditional web applications by including an additional code snippet in your existing RUM code. Here's how you can do it. For traditional applications, every AJAX call is counted as a pageview. You can see the number of pageviews consumed
Tip #47: View real-time changes in application response time across geographies
We've enhanced our RUM geographic maps so you can now view the response time of your application across various regions for a chosen time period. Since the RUM maps already show you your application's Apdex score, you can now correlate the changes between Apdex and response time with just a quick glance. Increased response times result in poor Apdex scores and vice versa—knowing the response time and Apdex score of your application helps you enhance the end-user experience. Aside from Apdex scores
Tip #46: How to avoid unnecessary consumption of APM licenses
Did you know that when your APM Insight application is DOWN, it still utilizes a license? Yes, DOWN monitors still consume an APM Insight license. Your application could go DOWN if: Your application's server is down. You've removed the APM Insight agent from your application. For the latter, even if you've removed the APM Insight agent from your application, it will still consume a license. To avoid unnecessary license utilization, you need to either delete or suspend your application. Happy monitoring!
Tip #45: Actionable items in the APM Insight dashboard
The APM Insight dashboard has a lot more to offer than a view of application statuses. Here are three actionable items designed to make the dashboard easy to use. 1. Did you know that you can customize metrics that appear for each application in your dashboard? In the APM Insight tab, you'll find this icon in the top, right corner. By clicking on this icon, you can choose which metrics (Apdex, average response time, throughput, error, and fatal count) need to be displayed for each application in
Tip #44: Capturing stack traces for SQL queries
In general, whenever a transaction exceeds the specified threshold limit, its trace is captured. SQL queries involved in the corresponding transactions are also captured by default. However, to pinpoint the exact line of code causing a problem, you need the stack trace of SQL queries. You can get the stack trace by configuring the threshold value of SQL queries in the transaction trace. By default, the threshold value of SQL queries in the transaction trace is set to three seconds. You can change
Tip #43: Pinpoint issues in external components with regards to host level details
In general, you can view the time taken by external components using application dependency maps. But did you know you can also find out which specific host an issue is stemming from? Let's analyze the time taken by an external component, MySQL queries, in Zylker. The total response time taken by all the SQL queries is around 1.0 ms. Inspecting further, we find that SQL queries to 10.**.***.**:5080 alone have taken around 5.3 ms. In this case, transactions made by users belonging to this cluster
Tip #42: Avoid having page views consumed by synthetic monitoring in RUM
In synthetic monitoring, you may simulate your application from various browsers and geographic locations to optimize its performance. For instance, let's say you simulate 10 stages of your application from 7 different locations at a 5-minute poll interval. If you're using both synthetic and real user monitoring, you would end up consuming 20k (10x7x12x24) page views per day from your RUM license. In such cases, you can exclude specific user agents. A user agent is a specific piece of software that
Tip #41: Understanding traces: Un-instrumented blocks of code
In APM Insight, slow transactions are displayed as a list with their corresponding trace. By inspecting the transaction trace, we can find out the total number of methods tracked by the agent as well as the time taken by the individual methods. By default, the APM Insight agent tracks known frameworks and methods. However, in the case of user-defined classes or frameworks, the agent classifies them as "un-instrumented blocks of code." So, how is this useful for debugging? Let's use the transaction
Tip #40: Understanding Traces - Timestamp
In APM Insight, every transaction's trace details includes the following information: Timestamp Exclusive time taken Total time taken Timestamp give us the timeline of the entire transaction from the second it begins to the second it's completed. Exclusive time taken is the time taken by the individual method call alone, excluding the method calls nested within and tracked by the agent. Total time taken is the combined time taken by the method call along with its subsequent child method calls. So
Tip #39: Identify and troubleshoot instance-specific issues
Applications often have multiple instances, and an increase in response time in one instance can cause an overall spike in your application performance. It's easy to identify the transaction that's responsible for the increase in response time. But how do you identify which instance the transaction stemmed from? In such cases, you can easily track transactions and their traces to their respective instances using APM Insight. Every transaction trace is mapped to its instance and can be viewed under
Tip #38: Get deeper visibility in your application performance using custom instrumentation
By default, the APM Insight agent captures pre-defined classes of several web components and frameworks. However, in the case of user-defined frameworks, the agent can't identify such classes by default. This is where custom instrumentation comes in handy. With custom instrumentation, you can track the performance of your methods and classes. Include the specified code at the beginning of your class or method, and the agent will start tracking its performance. Using custom instrumentation, you can
Tip #37: Easily monitor your AJAX calls using real user monitoring (RUM)
In single-page applications (SPAs), most web transactions are UI driven, and every web page consists of multiple AJAX calls. For every state change, the web page is dynamically loaded with the help of asynchronous calls; the response time taken by the asynchronous calls impacts the overall response time of your SPA. This is why it's important to monitor the performance of AJAX calls. With Site24x7 RUM, you can monitor the count, response time, throughput, and HTTP error codes of every AJAX call during
Tip #36: Monitor critical metrics using App Parameters
In general, you can monitor the performance of your application using default parameters like response time, throughput, errors, exceptions, etc. However, to monitor how your users interact with your application or application-specific parameters, you need some additional metrics. Consider a ticket booking application—its performance is monitored using the parameters mentioned above. But to monitor application-specific metrics such as the number of tickets booked in a day, the number of users logging
Tip #35: Assess the end user experience by integrating RUM with APM Insight
With APM Insight, you can identify and troubleshoot bottlenecks in your application. However, the way your application affects your end users might still remain a mystery. This is where real user monitoring (RUM) comes in handy. With RUM, you can assess how your end users interact with your application in real time. Even if your application appears to work fine, there are various reasons why it may not be rendering properly for your customers, including browser issues, responsiveness across various
Tip #34: Use a single template in APM Alerts for various APM monitors
In APM Insight, you can configure alerts at the application level. You can choose to receive alerts if there's a threshold breach in any of the following parameters: application response time, error count, error rate, and exception count. You can choose one or all four parameters while configuring your alerts. You also don't need to configure alerts with the same specifications for every APM Insight application. Instead, save yourself the time and use existing APM alert templates if you'd like to
Tip #33: Keeping up to date with the latest product enhancements
In general, it's recommended that you upgrade your APM Insight agents to their latest versions for the best performance. However, upgrading your agents manually or keeping track of new agent releases may be time-consuming. That's why we recommend you to automatically upgrade these agents. By checking the box beside Agent Auto-upgrade, your agents will get updated to the latest version automatically. See Figure 1 below. Figure 1. Basic configuration profiles in Site24x7. Once Agent Auto-upgrade is
Tip #32: Assess whether end-user experience is impacted by internet service providers
A slow website is a big turnoff for customers. But when your website's response time shoots up, should you always blame your website? Occasionally, your end user's experience might be impacted by their internet service provider (ISP). If your website functions normally over particular geographic regions but you still have users complaining about slow response times, then their ISP may be the culprit. In such cases, you can analyze your website response time over various ISPs used by your customers.
Tip #31: Why you need to monitor scheduled jobs
Scheduled jobs are basically background transactions that don't concern user. Basic tasks like data collection, data archiving, and alerting are some common examples. These tasks may get frequently executed at regular intervals. Since these tasks take place in the background, it's easier to overlook any issues or errors arising from them. Often you won't know if these transactions are successful or not unless a major issue erupts and bogs down your entire application. This is why monitoring background
Tip #30: Monitor dynamic URLs by grouping similar transactions
Your application may have multiple dynamic URLs executing the same operation. For example, viewing a user profile is a single transaction, but the URL varies with respect to the user. In such cases, you can group these URL to effectively monitor the performance of each. In the above example, the same transaction invokes multiple URLs, since each individual checks their own profile. This actually clutters the monitoring environment and can be handled more effectively by grouping them based on their
Tip #29: Effectively monitor your application performance by configuring the sampling factor
Your application may experience the same transaction repeatedly. Logging in or placing orders in e-commerce applications are just a few such examples. You don't need to monitor repeated transactions like these within the same polling interval (one minute). Here's where the sampling factor comes in handy. The sampling factor helps monitor transactions based on a set frequency. When set to five, one in every five similar transactions is monitored. You can adjust this number based on your requirements.
Tip #28: Drill down and debug issues with RUM Snapshots
The RUM Snapshots feature enables you to identify issues when webpage load time exceeds your specified threshold level. Clicking on a particular snapshot displays all the webpages accessed during that particular session, sequentially. For every URL, resources with the maximum response time are displayed under Critical Resources. With detailed information about your webpage resources, you can pinpoint issues to the exact conditions they arose from.
Tip #27: Debug issues faster by inspecting instance-level metrics
An application can have multiple instances running on various ports or servers. In APM Insight, application-level metrics are shown by default. But an application's performance can be impacted by performance issues at an instance level as well. Let's say your application has two instances. While the response time of one instance is within the specified threshold limit, the response time of the other instance has spiked up. This could be caused by various factors, including issues with load balancing
Tip #26: Bulk install the .NET agent across Active Directory
If your .NET application is hosted in more than one server, configuring the APM Insight .NET agent for every single server would be time-consuming. In those cases, you can install the .NET agent using the Bulk Installation Tool instead. This allows you to install the .NET agent across multiple servers in an Active Directory network simultaneously. And don't worry, the bulk installation tool retains the same agent configuration when deploying your .NET agent across your Active Directory servers. Go
Next Page