Tip #25: Assess your website's performance across various devices and browsers
A website may not always perform consistently across all devices and browser types. Site24x7 helps in assessing this performance latency with Real User Monitoring (RUM). Something as simple as a software enhancement or a version update could cause a spike in the response time of your web application. This is why you should track trends in your web application's life cycle on different devices (mobile phones, laptops, tablets, etc.) and browser types (Chrome, Safari, Firefox, etc.) across multiple
Tip #24: Manage your application and instance configurations easily
Your application may have multiple instances and configuring the agent settings for each instance individually can be cumbersome. In APM Insight, you can configure the same agent settings for your choice of all or just selected instances. This gives you the flexibility to easily monitor your instances the way you want. To change your instance configurations, click Edit Agent configuration in APM Insight. Click Select all if you want to apply the same configuration to all instances, or choose specific
Tip #23: Figure out the root cause of exceptions by inspecting their stack trace
At times, application transactions may be successful but throw exceptions internally. For instance, consider a transaction where information is usually retrieved from the cache. Should a problem arise with the cache, the information is instead retrieved from the database, marking a successful transaction. But on the downside, extracting this information from the database instead of the cache increases the response time of the application and slows down your app. In such cases, analyzing the stack
Tip #22: View response time changes in real time using RUM Playback
Analyze the response time of your application over various time periods and geographies with Real User Monitoring (RUM) Playback. You can choose a time period and view the gradual changes in response time across various regions with RUM Playback. You can also stop, pause, and analyze response times while the Playback is being rendered. This helps you discover subtle performance changes over various geographies.
Tip #21: Identify where SQL queries are being slowed down
Slow performing SQL queries can be identified and pinpointed with the help of stack traces. Whenever your queries exceed the specified threshold limit, their stack trace is captured by the APM Insight agent, which can be viewed in the corresponding transaction trace. This helps you find out which methods yield slowly executed queries. The stack trace of SQL queries can be viewed under the Traces tab.
Tip #20: Fix slow webpages with On-Demand Snapshots [Real User Monitoring]
Experiencing a slow webpage can quickly turn prospective customers away from your products and services. And what's worse-many times we might not even know the exact root cause of the problem without exhaustive analysis. In such scenarios,RUM On-Demand Snapshots come in handy. A Snapshot is a collection of URL's accessed by the user during a session, which is taken at fixed intervals. You can trigger On-Demand Snapshots as and when you experience a sluggish webpage. This will help you analyze webpage
Tip #19: Debug error transactions with ease by inspecting their stack trace
People often talk about "finding the needle in the haystack," and this phrase definitely applies when debugging error transactions. In general, not all transactions are successful; issues like corrupted data formats, external component failure, and improper exception handling can contribute to transaction failure. So how exactly do you identify these transaction problems using APM Insight? With error transactions, inspecting each transaction's stack trace comes in handy. Stack traces are like reports-they
Tip #18: Monitor your cloud apps efficiently with APM Insight auto scaling
With APM Insight, you can monitor your applications hosted in cloud environments. In general, when an application auto scales, new APM instances gets added automatically (depending on your license limit). But when your application scales down, it still consumes your APM Insight license. In such cases, APM Insight auto scaling comes in handy. Whenever your application scales up, APM Insight checks for any DOWN instances. If there are any, it suspends that monitor and adds the new instance without
Tip #17: Analyze pageview consumption with Real User Monitoring
Want to gain insight into your Real User Monitoring (RUM) applications' pageviews consumption? You can analyze how many page views are consumed by your individual applications as well as their monthly usage. What's more, you also get an estimate of current month's projected pageview usage based on your applications' page view usage. This helps you forecast whether your pageview consumption will fall within your license limit or if you need to upgrade your plan. So, how do you get details about your
Tip #16: View APM metrics for specific time periods using APM Insight Performance reports
Where do you look when you want to assess your application's performance over a period of time? Sure, you can always view data from the last hour to the last 24 hours to gather the latest insights. You can also choose a specific date or compare two dates to analyze your application's performance. But what if you want to assess your application's performance over the past three months? Or from July to December of 2017? Where would you look for these metrics? Don't worry - We have this data archived
Tip #15: Enhance the end-user experience by integrating RUM into Public Status Pages
With a Site24x7 Public Status Page, you can share the real-time status of your applications and services to your customers. You can make these Status Pages publicly visible with permalinks or iFrames, eliminating the need for users to log in to your application to view this information. You can also notify your customers beforehand with announcements, like in the case of scheduled maintenance. Additionally, you can integrate real user monitoring (RUM) into your public status pages-which is just icing
Tip #14 : Debug performance issues by analyzing HTTP parameters
Sometimes, simple events like updating your application may contribute to your application slowing down. You'll make some changes and it appears to be functioning normally for you, but the application may not be working for others. In these situations, analyzing HTTP parameters would help you to identify the intensity of an issue, so you can determine whether this affects a particular set of users or everyone. HTTP parameters like user ID, resource ID, and URL ID will help you debug the issue. To
Tip #13: View changes in your application response time without drilling for details
Imagine that you have just rolled out an update in your application and now want to check if that update has had any impact on your application performance. You can track the changes with Milestone Marker and observe the variation in response time in a graph. Or you can simply look into your application details in the RUM dashboard. Changes in response time are quantified by a red or green icon for active web apps in the dashboard. Red denotes an increase in response time while green denotes a decrease.
Tip #12: Detect slowness in external components using Application Dependency Maps
Failure in one or more of your external components, such as your database, Memcache, or HTTP connections, can slow down your application's performance. With Application Dependency Maps, you can easily identify failed components and their metrics like average response time, failed request, total request, and throughput. Mapping all transactions with their respective components eliminates the need for searching. View the transactions involved in calling an external component by clicking the View Components
Tip #11: Exclude insignificant transactions from monitoring
Few transactions or extensions can be excluded from your application monitoring process. For instance, webpages with static content (HTML, CSS, JavaScript) can be safely excluded from your monitoring process. Similarly, multimedia files such as images and videos (JPG, PNG, GIF) need not be monitored. You can exclude those kinds of URLs from monitoring by providing their file extensions in APM Insight. That way, you can focus on monitoring crucial areas of your application instead.
Tip #10: Resolve JS errors by analyzing the stack trace and browser version
JavaScript errors are browser-specific; what works properly for one browser may cause an error in another. With Site24x7 real user monitoring (RUM), you can identify JavaScript errors and view metrics such as browser version, count, device type, and stack trace. Using these details, you can debug errors with ease. The best way to check if resolved errors get repeated is by inspecting the date and time of the last occurrence. Just select JavaScript Errors in the RUM dashboard to take a look. Happy
Tip #9: Troubleshoot CPU spikes with thread profiling
Any number of things can cause high CPU usage, including frequent garbage collection, heavy data processing, or infinite loops in your code structure. Identifying the cause of a CPU spike often requires taking thread dumps and analyzing an enormous amount of raw data. Instead, APM Insight's thread profiling feature helps you to narrow down the root cause of CPU spikes by identifying the most time-consuming threads. With on-demand thread profiling, you can easily identify time-consuming threads along
Tip #8: Resolve database issues by analyzing query parameters
When a query is duplicated, or when a single query begins handling too much data, it can impact the performance of your application. In these instances, analyzing query parameters can shed some light on resolving issues. In general, query parameters are obfuscated in APM Insight for security reasons. By disabling SQL parameter obfuscation, you can view those values along with their respective queries.
Tip #7: Track your garbage collection performance with APM Insight
APM Insight gives you everything you need to assess your app server's garbage collection performance. Track how many objects are collected and how much time is spent cleaning them, as well as how much heap and non-heap memory your application is consuming. Mitigate and prevent out of memory errors using these metrics and memory stats. Identifying your application's memory usage patterns will help you fine-tune your application's JVM configuration.
Tip #6: Compare APM reports from specific dates to assess your application performance
Every once in a while the performance of an application may suddenly deviate from its normal course. This performance change is not always caused by a product update or feature enhancement. Common issues like memory outages, lack of space in the database, or changes in the application environment can contribute to sudden application slowness. In such cases, comparing your application performance with previous data can be insightful. Comparing key metrics like average response time and throughput-as
Tip #5: View a browser-specific resource breakdown with Real User Monitoring
With Site 24x7's Real User Monitoring you can analyze how your application performs across various geographies, device types, ISPs, and browsers. You can even view the average response time and throughput for each browser and all its different versions. View the count, response time split up, and domain split up of resources that were called during a particular transaction. These resources could be your CSS, scripts, XHR, iframes, and images. With the resource breakdown, you can easily find why a
Tip #4 : Detect .NET application performance issues using app pool visibility
Identify process-level performance issues in your .NET application by monitoring your IIS app pool. Viewing metrics including network usage (bytes in/bytes out), cache performance, processor utilization, and memory consumption helps you get a quick overview of any abnormalities in your application. Figure 1: Application details Figure 2: App pool details By integrating the APM Insight .NET agent with the IIS server monitor, you can view metrics specific to your app pool. Or the other way around,
Tip #3 : Check if product updates are causing performance problems in your application
Not all product enhancements have a positive effect on application performance. In fact, some enhancements only present their negative side effects after a long while. What you need is something to assess the impact of enhancements over a period of time. This is where Milestone Marker comes in handy. With Milestone Marker, you can record every update you make and analyze each one over time. These markers appear in key metrics like Response Time and Throughput graphs. Note: Milestone Marker is available
Tip #2 : Assess if your application performance is impacted by external services
Application running slow? See how external services are contributing to your application's total response time with the help of the app server component graph. As shown below, this graph tells you what percentage of your application's response time is caused by each external service. You can also track your own components with the help of custom instrumentation. So, the next time your application lags, have a look at the component graph before you blame your code.
Tip #1 : How to get the most out of APM Insight Performance Graphs
We all use the Performance Graphs in APM Insight to assess our application's status using key metrics including Apdex Score, Response Time and Throughput. But did you know that every data point in the graph is clickable? Yes, and furthermore, it helps you to drill down for further analysis. These graphs are correlated with each other and a drop or increase in the graphs always communicate us the status of the application. Here's how you can find the needle in your haystack - Let's inspect the highest