The bank here in Brazil, and the world, need to ensure that transactions are processed in the shortest amount of time possible. We closely monitor this to avoid penalties. Additionally, having the ability to closely monitor the resources of our machines with Broadcom DX Application Performance Management has been helpful for us.

In our organization, there is a bit of a learning curve of how to leverage the tool appropriately.

Introscope was our first modern APM tool, and the application deep dive capability gave us visibility into behaviours of requests from within the app engine & code. CEM was the first Business Transaction monitor that could report response times for every data hop. ADA reports TCP statistics that are app specific but still match command line output NW Engineers expect, and the tool revitalized a difficult relationship between app monitoring teams and Network support experts.

We can find out the bottlenecks before the customer encounters them. That's the major benefit.

It helps prioritize application performance issues because we can prioritize them in a test phase, or the development phase. We can find out that which queries are slow, what is the behavior of our application, and what we can tune our application to make it more reliable and faster.

What CA APM really does is that it allows us to see the inside of the managed code application, taking our performance to a more mature level. We're able to see things as they start to load up before we have a failure.

I don't know if I would call it proactive, because typically in our environment, things move so quickly. Only upon post-analysis do you see the actual build-up. Only then can we act and we end up having to build in thresholds.

Adding a layer with built-in some service level guarantees between the operations, development, and support, give us one of the key disciplines that this product has pushed us to evolve into. Previously, it was bunch of loosely built operations metric infrastructure applications. I would get a call (someone I know), you know me and let's start working together, because there is a problem. Now, having this alerting in place and metrics showing themselves for what is in store and what we should work on, there is a service level that is being built across these teams so they exactly know how to work. That is a very good thing to bring as a discipline.

It is very hard, especially for banks working from the Canadian space, because we are traditional in nature. So, it is very hard to bring about change. A product like this has broken the ice in two years in good amount of time in Canadian market and Canadian technical space. It has been able to establish itself. There has been a little push for certain disciplinary changes and behavioral changes within the teams that work in the bank.

The organization becomes quick in assessing hot spots and attacking any issues that are bringing down and application. It means meeting SLAs and reacting to issues quickly before they become problems when we see patterns, before the whole system becomes unusable.

In our organization, it was very common to create crisis rooms where we gathered experts from all areas to investigate an application problem by allegations of users about problems of slowness and errors. After we started using APM in our environment, we managed to reduce the creation of these rooms by 90%.

Currently, we are building a visibility dashboard which allows our level-1 and level-2 engineering teams to actually look at the events, and be able to designate which ones are critical, which are important. It alerts them. They are able to simply look at a dashboard to be able to predict and resolve issues.

The improvement for us is in the customer experience. The quicker the websites are, the more satisfied, the better experience the customer's going to have, hopefully the more product they're going to buy. The sales sites are more reliable, more up time.

It sounds kind of corny, but it helps bring us together because when a problem strikes and it’s happening, there's the tendency to start finger-pointing at different groups. With this tool in the hands of a tier-one or a tier-two technical individual, or small group, they can identify the issues without needing to go back and forth between different departments, who are all saying "Oh, that's not our problem." It then turns out to be their problem in the end. That's the main benefit.

It has helped to stabilize the environments and also quickly identify issues some while they are occurring and some proactively.

The extensive monitoring alert gave the ability to act quickly before an outage happens.

APM is the tool used by all support areas to monitor Java application and infrastructure performance. We have standardised support for the services running on the Java platform into one tool.

We are introducing 10.1 in our dev environment and then prod down the road. APM is a new culture here so we are working with customers in getting them introduced to the product. Want to show them how deep dive provided by APM can help them with DevOps lifecycle as well as proactive monitoring. The previous version v9.5.3. we've had for about a year since we introduced a the product in our environment has been a good hands on experience for our users. Now looking forward to getting hands dirty with 10.1 and utilizing the additional capabilities. Will continue to show customers the usefulness of this tool and how they can use it to generate reports on performance of their app as well as the service it provides. There has also been reactionary situations where we have used APM and pin point the issue or able to narrow down the focus.

Updated - 08/29/2018

We now have v10.5.2 SP2 running in our Dev & Prod environment since June 2018. So, far we've had a really good reception for APM by our internal app owners. The key is now for ESM Tools to be adapted by app owners (physical, network and app layer).

Updated - 2/3/2020

We now have upgraded to v10.7.0_SP3 which has provided yet another set up stability and more capabilities for our app environment. APM Command Center (ACC) has a more features and stability from a admin and maintenance perspective.

The next upgrade (v11) changes a lot of things as Broadcom has decided to go to Kubernetes platform as for as APM upgrade and/or rollout of v11 is concerned. It will be interesting to see how customers react to this and whether it pushes them to take a look at SaaS model.

The executive dashboard we created gives a lot of visibility out there, so from that standpoint if somebody sees something go red and they say, "Hey, what's going on?" we have to be on our toes. There's no working on something for a little bit before someone knows.

But having said that, there's a lot of flexibility in being able to see stuff in those customer systems, which is vital for us.

In the newer versions of the application, they had something called a Triage Map. That basically breaks it down from a service perspective. You actually see it from a service perspective and then you see what components make up that service.

It really helps the business. They are not seeing individual servers or individual devices, they're seeing it from a service level, which is what everybody wants to see. It works the logic, the mapping, and how the application sticks to the database or the web server. It automatically creates that map for you.

For us, it's given us completely brand new visibility that we never had before. Application owners are able to completely understand the application better now on the back end, as well as on the front end. It’s pretty much an eye opener for them.
A lot of it, we try to do it through alerts and dashboarding. You want customers to spend a lot less time poking around and we want the dashboards to be a tell-tale sign of what is going on in their environment.

Our organization has over 21,000 agents running. Being able to monitor all those agents at the same time, with the ability to be alerted when thresholds are exceeded. We can know when we are having problems without having dedicated people to watch monitoring screens all the time.

We have used CEM to get insights into what the user is actually experiencing.

It's improved our ability within the instant management realm. We are able to get the root cause faster than we had done before. We had to uninstall it two years ago, it was a matter of looking through log files and then making basically and guessing as to what the root cause was. It allowed us to avoid the same incidents occurring over and over.

In a production environment we check all the parameters. We can detect any leakage, any problems, whether RAM is sufficient, and whether CPU is crossing a threshold. We can determine if we need to add new servers or RAM or adjust the heap settings.

It helps save resources for a company.

It also helps us look at business-critical transactions and how fast they are happening. It helps us pinpoint the methods or functions that are taking longer to operate and we can advise the development team to look into it and fine-tune those areas. They can make adjustments immediately.

We use CA APM for monitoring and alerting of our Java applications.

It’s used internally to help us get a grip of our infrastructure environment, including datacenters, network, applications, voice solutions etc. and to help serve over 10,000 customers utilizing the CA framework.

Easily map between transaction and method recall

Useful automatics alerts

Easily understand graphics

APM tools are essential for finding performance bottlenecks and pervasive issues. It gives a high level point of view on where there is a problem. This tool, in particular, is not as good at deep dive analysis. Newer versions, like 10.5 with AXA, Dynatrace, and AppDynamics may be better at going deeper into root-cause analysis.

It secures traffic through the HTTPS. There are a huge number of cipher suites which are enabled. Unfortunately, some of the cipher suites are not being recognized by the APM tools. However, we are able to manage with the other cipher suites in the market, apart from ones offered by CA APM.

We have had a tough time getting these topics monitored.

It helps me know everything. When I know everything, like when there is a problem, I can find it very quickly. It reduces the time for solving problems in the website.

In many organizations I've seen this product working in, SEV1s have been reduced quite a bit. One particular organization, within the first 12 months, reduced their SEV1s by 90% just by introducing this product. They had previously been using a competing product, so it really speaks to the value provided by this one that they weren't getting out of the other products they were using.

Suddenly, we were able to evaluate based off how code was being traced. In one incident, it saved us 18 hours in finding the actual problem in the logic for that application once we had a problem.

It has provided application teams with another tool in the tool box to diagnose complex performance and availability issues. It also allows for the early detection of an issue before we hear about it from our customers. CA APM reduces our time to resolution and improves our customer confidence.

From the application speed perspective, we can install it in both the development and production environment for the applications. In the development environment, they're able to test and capture long-running transactions, database issues, too many threads, or memory leaks. We are able to identify those, in theory, before they make it to production. This gives us a much cleaner application when it goes up with potentially less issues from a newly deployed piece of code. That’s the kind of the big play that we're going for and we have yet to generate tickets because we're still working to capture the right level of noise. This is a better process then flooding application teams with a lot of details.

We are a government IT company that provides services to the government. Because of that, we're required to use a very wide range of products and applications. We also need to have a multitude of interconnections with diverse systems, and one of the biggest difficulties we had was how these interconnections were made. CA APM has provided us a solution for this, allowing us to discover the root cause of some speed issues we had in the systems that were very difficult to diagnose.

The CA Introscope dashboard of applications is the view our operations team uses to quickly identify any issues within the application space especially during peak trading season like Christmas/Easter. It is extensively used for quicker root cause analysis within the application area.

Introscope along with CA CEM and ADA is expected to further decrease the time taken for root cause analysis for critical customer facing incidents and also to identify bottlenecks before they impact our customers.

Application suite was installed to bring in compliance with international security standards like ISO 27001 and SAUX

Business-wise very much. We have the best solution in the local market because we are the most experienced APM vendor in our region and have very satisfied customers. They said that UX is much improved and MTTR is significantly decreased.

We are able to easily and quickly find some of the problems with the applications and coding, and some of the performance problems. Then, we monitor a lot of the performance via the application, and learn via the dashboard about the health and performance of all the applications.

It helps us to meet business transactions SLA for our critical end-user applications; proactively identify the issue and helps the application team make its diagnosis before it impacts the end-user experience.

When there is an outage or performance issue, the on-call teams are called to a conference line where we can triage the issue. Before APM was used, these calls would require all areas of support, which include network, server team, middleware, database and any other areas of expertise. Now, the Incident Management team has a set of APM dashboards that allow them to narrow down the issue and call the specific team(s) to the bridge call. One of the first questions that is asked now on the bridge calls is, “What does APM show?” For example, if it was a database issue, we can tell which query or stored procedure is having the issue.

In terms of stability of our application, that is key, it really helps, APM really drives that factor.

It helps prioritize application performance issues. Through the stress test environment we really evaluate it. We are able to determine what the application requires so that we will provide it and take it from there.

As our production increases, we have visibility of everything that's going on, especially since we run a lot of applications and we're able to monitor all of them. If something goes wrong, CA APM plays the primary role in helping us perform root-cause analysis.

The mean time to resolve has reduced dramatically since we started using CA APM Introscope. We found it very important for our DevOps strategy for resolving issues and for pre production tests.

It's important that our managers are able to measure the SLAs of our applications. They're able to do that with APM as it provides both real-time and historical performance data so that adjustments can be made accordingly.

We are using APM for troubleshooting and because of this product, the delay to solve and to fix issues has been reduced by 40% on average. We also use the APM data to analyze and predict if an application will work.

For us, the application is a new eye on the same data. Its quality and the way we access it is going to make the difference between an application you keep using and an application you won't. There are a lot of DevOps methodologies to improve the time to market and to deploy applications quicker. Sometimes it's not enough because at the end, the application expands some issues and the isolation of a root cause is quite complicated. We analyze about 3,000 incidents and predictions, classify them, choose our toolbox, including APM tools (the CA APM solution), and we are able to predict, to anticipate incidents and to assess a risk for an application to go live.

We're primarily using it for production-system monitoring of application errors, slowness, things like that. I identify issues for our customers.

Cultural issues prevent a product like this from making the impact it should have.

• User-defined transaction profiling
• Application topology discovery and visualization
• Application component deep dive.
  

Our development cycle has definitely improved as far as the turnaround time on fixes and improvements. The solution that gets put out is definitely better because of it.

Prior to the product, we only measured user/customer experience when they actually reported the issue however now we have the ability to understand user/customer experience when it takes place or even predict it with appropriate metrics. This means we can respond proactively when service is impacted without disputing/denying user/customer complaints.

Application teams gained visibility into application performance. CA APM improved our ability to troubleshoot application issues and shorten resolution time.

It's helped us improve in terms of solutions by displaying key system data easily.

CA APM is currently used in two areas of our business (SAP estate and SMART estate) but slowly we are delivering APM to a vast amount of people in the business. I think that is the biggest compliment I can give as more and more people are wanting to use APM.

It helps us identify and isolate issues when trouble arises; keep services up and running, basically.

We're using this solution to turn our support into being more of proactive approach than reactive to issues that are reported to us from the customers. We're actually trying to bring those issues to their attention before they bring it to our attention. With new features in version 10.5, it looks like we're taking more of an inside out approach to actually bringing the root cause immediately to our attention. This is instead of us having to start and dig down to identify what the root cause was. It brings it right to the forefront immediately without requiring additional triage. It's really changing the way that we're doing our business. This improvement is not only from a monitoring perspective where we're getting advanced notice of system issues that are occurring, but I'm actually using it as a tool to even identify where there are tuning opportunities based on our current configuration. We are also using it in working towards global standardization for our entire client base, which is something that's been lacking. It was very difficult to find all of that information in one place, readily available, and historical information like transaction activities and things of that nature. They're all now available at our fingertips, whereas before that just wasn't a possibility.

MTTR has greatly improved. Teams are now better focused on the cause of application performance issues, much earlier into any event. Additionally, development teams now leverage the data gathered in lower environments to ensure that a better quality product reaches production.

We have a key APM dashboard that is the primary dashboard utilized by IS Operations Center. We use it to evaluate the health of our primary customer and associated impacts on the application suite.

The different layers of monitoring helped to optimise the resource and reduce MTTR.If I found the issue in Infrastructure then team only focus in the infrastructure layer 

We use APM for application monitoring, which includes availability, performance of apps (stalls, errors, and response time), and transactions. The product is extremely customizable when it comes to setting up application monitoring. It provides app monitoring data with very effective, immediate alerting.

We use this for ticketing. This helps us to realize not only from the monitoring standpoint, but we make custom dashboards for our development areas so they can understand how busy traffic affects their application with traffic. They can see how traffic directly affects their application in positive or negative ways. It gives immediate feedback to know, when we have a bad day, we have to look at this area because that slows down first.

It shows us where our weakest link is.

It brings our operation side and our application side together. When it comes to implementing the tool, like when we supply the agent, we have to get permission from the application side to say, "Hey, we're installing such and such agent on this server. Are we able to go forward with it?" Then, whether they tell us, yes or no, we can do it.

It helps us prioritize application performance issues. It has assisted triage where we can drill down and see where exactly the problem lies. If it is a database issue, we can see the exact query that is causing the issue. Or, if it is a web service call that is having any issues we can look there as well. It is pretty accurate when it comes to that stuff.

• Reduced troubleshooting time by identifying the exact point of failure
• Capacity planning of infra based on application performance

The visualization of the solution takes you to the problem areas much faster.

We're able to remediate issues with quicker turn around time. So instead of taking a couple days to figure out what the issue is, we're able to figure that out probably within half-an-hour.

It helps us by simplifying the triage of application performance issues. We have a buy in from our developers that they're able to trust the information that we provide them. It has proven itself. It's really a trusted source of monitoring.

With this product, we were able to increase our applications' performance, their response times, and to improve the satisfaction of our customers.

It's provided us with consolidated reports and a monitoring dashboard. With the monitoring dashboard, it’s easy to monitor things all in one place.

Also, it's helped us greatly that the dashboard allows us to create very customizable views that give us the information we need to determine the overall status of network health.

The monitoring tool is able to monitor many teams at a time. We also use it to monitor our web agent. It’s also Java-based and versatile.

The alerting part – if the system goes down we get an immediate notification that a resource has gone down, so it reduces the impact on the business.

• Centralized point to start studying a problem
• Fast analyses
• Getting quick solutions on most cases, but sadly, not for the hardest ones

When the SAP requests start to become slow, I can proactively warn our internal customers to stay alert for any impact.

We were able to use CA APM to help diagnose a vendor provided product where we were experiencing slower than normal performance. While using the product, we were able to see that the issue resided in the database and were able to make adjustments to correct it.

We're CA partners and we work with their product and we deploy the solution to our customers. Working with CA APM is effective, simple, and the customers are satisfied with the solution.

Before APM, all the support/information diagnostic retrieval was post-mortem. Logs retrieval with tons and tons of useless info would generate a report after several days of an issue, with no clue as to a root cause, but with several hypotheses on what was it. Now, different teams can get info even before the system crashes and can take proactive steps and find the exact point to focus their efforts to fix it.

Also, not only are the main services now monitored, but the main website with no transactions at all are included. This helps us to monitor customer experience and verify the correct functions.

We've had some hits and some misses, but our successes have been well-noted. Overall, APM improves our total customer experience and reduces our operational costs.

That said, the downside for APM is, in our case, end-user acceptance and use. We're trying to expand to other departments, show them what the value points are, and show them that we can help them with their jobs, performance, and efficiencies. With version 10, CA shifted its marketing plan and its persona, and that's been rather disruptive. I'm hoping a good disruption, but a disruption to my end users, whom I'm still trying to get turned-on to performance monitoring improvements.

They tried to streamline the organization, that was the initial point of using APM. It led to so many internal changes, but it didn’t affect the organization much at all in the end.

But the good thing about the solution is there is little overhead. It has a very small footprint on the system and it doesn’t affect the performance of the CPU.

The time it takes to track problems in applications is the most valuable return that we have from this solution. 

1. We are receiving feedback from the DevOps teams in order to improve the way they are building new applications. 
2. We are discovering how the user uses the applications and what their performance is with them.

With Experience View, our operation team has all the required information in regards to the health and quality of transactions and applications. Thus, in turn, it improves collaboration and reduces the MTTR. It doesn’t require an expert to identify the RCA.

CA APM helps to identify problems and make faster decisions so as to re-establish the service in a precise way.

We're just now adopting APM, but we anticipate that it'll be very helpful with level-3 and level-4 triage.

CA APM is mostly used during production post-rollout week. This is when our developers can quickly pinpoint any performance issues we might be having in production. Since the tool gives us near-real-time information, we lag only 15 seconds, we can quickly see bad trends and respond to them. Before APM, we were more reactive then proactive.

CA APM is the go-to tool for any performance-related issues. It is always there monitoring the non-production and production environment. It is becoming part of the DevOps stack and becoming a key support tool for Performance testing.

The tool has supported many times in identifying slow transactions and the bottlenecks in applications.

We had for several applications performance issues. With Introscope we were in many cases able to pin-point the bottleneck(s) and debrief it to the dev organization to improve their applications.

In our organization, the critical applications are being monitored with thresholds set for any malfunctioning through APM. Also, we have configured Dashboards which display any deviation of the application from normal. Further, the Tool is integrated with CA SOI, which displays the alerts at the Service level. Overall the Tools helps to detect any issue emerging with indepth analysis available for the resolution through APM components.

It's critical that we're able to find actual problems or issues with applications on our network. We use APM to do that, as well as to troubleshoot the causes or triage them so that we know where to look for the problem.

It show us a clearer view of our business and we can take proactive decisions using data collected by CA CEM.

With the CA Customer Experience we take Marketing actions, for example, we know how many transactions ocurred in our internet banking.

With the CA CEM value settings we can measure the size of ours earnings and even more of our losses caused by defects.

We are constantly looking at the customer experience. Thus, in this aspect, it has helped us to improve the execution time and get real access to the problems.

• It helps in proactive monitoring.
• We can assess a risk in a test environment if application is going live.
• We can do OS, application and EUM with some part of network monitoring on single dashboard.

It helps us to troubleshoot issues or to isolate issues faster, and we can then take the appropriate actions to resolve those issues.

Back in the support days, we were able to provide Business Service availability and performance statistics rather than just the number of P1 / P2 Incidents rose within the service desk each month. With the change of mentality to a Service Offering approach through CA APM, we first used the SLA numbers for each day to then determine which incidents where of most criticality to the business and technical support team. This meant that support resources where used more efficiently to resolve bottlenecks in load and performance during peak periods of the day.

As such, no improvement after using CA APM.

Regarding how we utilize CA APM for container monitoring, our implementation team is not able to this information. Our implementation team was not able to understand and share information regarding the impact CA APM has when attempting to triage complex application issues; and similarly regarding the visibility CA APM provides across complex application environments. We are not aware of how the solution allows you to monitor and gain performance insights into the various technologies across the application environment, like docker monitoring and the ability to see into the database. The same is true of how the solution helps monitor system changes, topological changes or code updates. We would like to receive documentation to understand the above features.

As all of our applications are monitored by CA APM, it's now easy to analyze unusual behavior in a normalized way.

In terms of container monitoring, we are currently in the rollout phase. In the end, all containers will be instrumented by CA APM agents in order to have a complete view of the current operative status of the dynamic and volatile container world.

All application servers are instrumented to provide a standardized monitoring baseline for the given technology. We defined sets of base monitors in order to normalize analytics capabilities from a technology perspective. On top of this we monitor application specific classes.

As we are currently in rollout phase we can't yet report on the visibility CA APM provides across application environments, yet.

Regarding monitoring and performance insights into the various technologies across our application environment, it identifies the "worst" application in terms of which app has the highest number of errors, slowest SQL queries, etc.

System changes, topological changes, or code updates that are introduced into our environment are analyzed by our architecture team using CA APM.

We want to sell the project in Japan. We have users in Japan. By combining the APM and our product, CA can sell it. 

We are a partner. We bring our customers to CA, and they can sell the product. Recently, CA is focusing on customers in Japan, the Fujitsu customers. 

It helps us change from being being reactive to proactive.

For example, before each upgrade of critical mission application, we have the APM set for prep, and all administrators can do a stretch test, and they see how applications are working under the load. It is great, because they see which part of the code, network, or any programs on the database are slow. We are using it, not for productions, for the testing in pre-production.

Before CEM, we didn't know when the users were having issues. We always learned about issues when the users called management and the managers informed us about the problems. That was an embarrassment.

With CEM, we call the users, help desk, and application support before a situation becomes problematic. Therefore, problems are deflected and embarrassments of not knowing what is happening are avoided.

Having implemented into production, we found that initially the application had quite a few incidents, alerts, and problems as we used monitoring to unearth some technical debt.

However, after implementing “smoke detectors” and resolving the technical debt, the applications have become much more stable, with fewer production incidents, fewer defects, higher reliability and quality of service.

Implementation is underway currently, but there are various parts of APM 10 which will improve the use within the organization compared with APM 9.5.

We have deployed this product at many businesses and the reviews of the customers was that it increased the value and revenue for their business.

Identifying the performance bottlenecks in every environment (UAT, SIT and Prod) including features for Service Monitoring (through alerts).

It alerts to application performance dips.

It provides less critical incidents for gold-category applications. We get proactive resolution for events.

• Our customers are now able to figure out and better understand how their applications are performing. They can identify very quickly where the tension points are. It makes troubleshooting applications performance problems very quick.

• It allows our customers to quickly improve the process of their applications.

It reduces the downtime of applications, and has, in fact, minimized it to approximately 5 percent, and possibly even less than that.

It has helped us to showcase business use cases better to our clients during demos or PoCs.

We have deployed APM agents on multiple applications for our customers who had the worst performance. The application team was unable to pinpoint the problem and that was the main pain area of the business. We have collected and shared RCA for some problems with the business and application folks. Now, the application team has more visibility in regards to their application performance and they can easily pinpoint to the problematic area by transaction traces.

With CA APM, we can see the performance regarding the transactions of our applications and analyse the availability and quality of our environment to provide the best experience for our clients. With this product, it is possible to resolve the problems faster because all of the features are connected.

Most of our customers use the tool mainly for incident diagnostic and incident early detection. In this sense, I know that is quite useful for customers. Sometimes it is used to validate results of stress tests before going to production.

CA APM always helps in finding problems quickly rather than requiring us to check logs to pin-point the issue. The turnaround time to resolve the issues has improved after we started using CA APM.

Also, by looking at the dashboards, application teams are able to find the problematic component by just having a quick look at traffic lights and dial meters.

Using a combination of CEM plugin and EP agents, we were able to derive business specific metrics like day/hour-wise revenue opportunity, day/hour-wise conversion, and failure along with the reason for failure. So basically, a customer is able to identify that since opening of business hours, how much revenue opportunities came to the application, how many got converted, and how many failed, along with the exact amount each opportunity carried. This is also possible using customized agents, but it becomes difficult when these values are part of an object and not direct arguments or return-type method.

The tools help us resolve issues with applications. For example, an application team had an issue with the slow average response time of their application. By using CA APM, we found an issue with backend calls, as well as with classes and methods within the code.

• SLAs and User Experience improved (most of all- User Experience / Application performance)
• You can fix complex incidents with a quick look at the dashboards (CA dashboards or your custom dashboards)
• You can easily be proactive and can help to save departments a lot of time. If you have a great platform, (something that is actually very common in enterprise environments) you have a lot of log files.

The product has given us better visibility of the agent and communication of the WAS application to the MQ server.

Using CA APM has allowed us to know about the performance of our applications and servers and also to identify issues before they happen.

It helped us be proactive and resolve problems before they become system-wide issues.

Operations are able to view the performance of their applications and the real-user experience in business transactions, all through a single solution, CA Application Performance Management. Customers are able to understand when applications have issues and which component is causing performance degradation. From the end user to web servers, app servers and backend components, all components are monitored.

We've been able to detect a lot of anomalies, troubleshoot those and fix them. It helps us with where to look. We're able to find the key component that's causing the issue and drill down into it, get into the details, and then fix the issue.

It has improved our transaction monitoring significantly.

WAS GC monitoring enhanced our application performance and DB SQL performance.

It is very useful and helpful with the analysis of historical performance data.

My organization can find the correct solution to an alert the first time around. This shortens the resolution time.

CA APM gives us more transparency about our website environment and reduces time for root-cause analysis and minimizes service downtimes.

• Provided greater visibility to IT regarding necessary actions on its governance and relationship with suppliers and business areas. In the previous scenario, IT was surrounded by tools, but did not possess a vision focused on quality of service delivery and end-to-end. With the adoption of CA APM, we have accurate mapping, we're updated on what supports each business service and what, when, where an incident occurs and how it affects the business.
• Regained credibility of IT's role as a driving force for improvements result in greater business performance. In the previous scenario, IT was surrounded by tools, without any integration which forced us to dispense resources with a late result and sometimes without solving the issue. With the adoption of CA APM, there was a change in the relationship of the areas of IT, its own role and value to the success of the business.

It helps speed up the identification of the cause of performance problems, making us more efficient in terms of cost and time spent resolving issues.

I have personally audited the number of incidents opened for the Application Support Team before I implemented CA APM for one of my clients. The incidences raised by end users for application performance-related issues decreased from 1700 per quarter to 250 per quarter. CA APM/Wily was proactive in its monitoring.

We have reduced the triage times and don’t need long lasting analysis any more. It is one of the reasons we could improve and accelerate our development and operations procedures.

We don’t have performance bottlenecks or leaks in production any more. We act proactively to prevent their occurrence.

The main analysis is performed in a QA environment. We can eliminate the majority of problems concerning wrong configuration or capacity planning and even code errors before they go into production. We’re continuously working on improvement of our development and operations and Introscope helps us on this way.

The time to deliver, time to market, is the greatest improvement.

We can review recorded sessions of UXE.

An example would be the error reports, which shows the services with the higher error percentage and which errors occurs most, to they can be easily spotted to improve the application performance.

Handling of Issues has become proactive rather that reactive, with Introscope flagging issues before they become a crisis.

We have implemented all the above features and some extra features like EPAgents, Web Server Power Packs, Unix Field Pack, MQ Power Pack, Perfmon Collector Agents, Error Detector, Change Detector, Leak Hunter (Occasionally), etc.

I like APM because it is a complete solution that helps the production environment to identify the root cause of problems before affecting the application or services.

In our company, we have several simultaneous projects. We need the ability to manage all of them in terms of dates and costs when we deliver to our clients. APM allows us to analyze data and find problems that may affect delivery to them.

As a consultant, this product helps all of my customers find production issues quickly. It's capable of identifying the root cause of an issue within a few minutes. It helps monitor all of the environments of application servers and generate alarms if something is wrong. It generates sums to analyze and understand what is happening with the applications.

We can monitor several application in the same manner and same site.

It helps us find the cause and the errors in our application quickly.

It largely reduces turnaround time from application failure, and has reduced man hours in managing availability, performance, and scaling applications.