Broadcom DX Application Performance Management Reviews

• Very powerful and flexible suite of tools which provide great insight into application and network performance.
• The features we use most are the introscope agents and CEM real business transaction monitoring.

Introscope Agent management is very manual, although the next version is looking to improve on this situation.

Dashboards are powerful but clunky and time-consuming. Again, the next version is looking to improve on this.

CEM/ADA are extremely powerful, but they require a lot of networking knowledge.

The user management for these tools is poor and we've found the EEM product to help with this to be quite flaky. Again, this is due to be improved upon in the coming version.

Cloud Monitor system seems to be pretty good, although I haven't used it as much as the other components.

Architecture of the OPMS (on premises monitoring system), which integrates with Cloud Monitor, seems over-complicated and doesn't integrate well with the main system.

Approximately 1 year.

Customer Service is excellent. They're very fast and provide knowledgeable responses.

The support personnel I've dealt with have been very responsive and professional.

The transition to APM Team Center as the primary console in APM 10 will definitely be the most valuable feature.

The ATC shows a lot of potential on how we view performance metrics on the front-end and back-end connections in a single view.

An APM tool should have the capability to provide a high-level view of the monitored application and APM 10 is heading in the right direction by just doing that. A single-window view of performance metrics, timeline, applications, alerts and heat maps (DA) throw a lot of data to an engineer in a quick glance.

Another new feature may just have to be Entry Point Discovery. The capability of the agent to detect the application entry point and create custom pbd for this. Interesting concept of automatic discovery and prescriptive change.

CA APM strength is the Custom Instrumentation - just having the capability to capture performance metrics for classes and methods in the application makes this tool a elite candidate.

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.

APM 10 has jumped leaps in feature improvement over the last few releases which in itself is an achievement.

The UI still feels a little outdated (though there is change) especially for Dashboards. New widgets and dynamic actions needs to be in place for this part of CA APM.

Integration with other DevOps toolsets. CA APM needs to provide easy integration capability with CI/CD and ALM tools which will provide strong value to all stages in an SDLC.

APM 10 Team Center provides a faster way to diagnose environmental issues and complements the existing APM WebView.

The enhancements related to Smart Instrumentation, Differential Analysis, and tracing will all contribute to enhanced troubleshooting during an issue and the ability to provide more intelligent alerting from the systems.

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.

Team Center requires a number of tweaks to allow per-user/group configuration to customize the interface for groups of users, though I believe these are already in the product roadmap.

In this version of CA APM team centre, everyone sees the same view of the server configuration. Ideally, groups of users would see a subset of the data which they are interested in by default. Currently, they can do this through filtering, but a user/group setup would allow pre-defined filters to be created for particular groups of users. Alternatively, users could be restricted to see a smaller section of the overall monitored services. In the current version, anyone who logs in sees everything, and can create their own filters.

The system monitoring is one area that we like. Transaction tracer is another area that has worked well. The platform monitoring features is great, as APM integrates very well with some of the application server performance monitoring interfaces.

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.

The end-to-end monitoring is not good. For example, a user reports a slowness issue, but we don’t have an option in the pool to find out which layer is causing the problem. The system doesn’t break down the application performance to show you what’s happening and where.

I've been using it for over three years.

It is a long process. Use-case monitoring - you have to know the application in and out to make it work. Other tools allow you to create the profile and configure it later. With APM, we don’t have anything like that. Configuring the use-cases monitoring is a long, time-consuming activity, and not a user-friendly one. It requires expertise and knowledge of the applications, and CA APM.

Outages with the solution are very frequent nowadays actually. We see the APM solution going down two to three times a day. And it’s a long troubleshooting cycle, as the CA APM system seems to add a lot of performance overhead.

We haven't scaled it yet.

It’s OK. They respond and acknowledge customer requests.

We are not happy about it, because we have had more than five or six tickets open for some months.

Previously, we worked with Dynatrace and AppDynamics. We changed because our organization decided to go with the enterprise licensing options that CA offers.

It was neither straightforward nor complex, but with some effort we were able to get it right. The application configuration for system monitoring is a good feature. It integrates well with application servers, but the application use-cases and monitoring was time-consuming.

We implemented internally, partnered with a vendor team. The vendor team were good but they had to depend on CA service tickets to complete the installation. This is because they don’t have clear guidelines to configure some of the solution’s features; for example the installation guide for URI monitoring feature doesn’t cover all the use-cases, and the partner had to raise tickets with CA for assistance so there was an impact on time.

I think pricing is good, actually. That’s what made our organization choose this solution. We didn’t face many challenges with the licensing because of our enterprise agreement.

• AppDynamics
• DynaTrace

For traditional technologies it’s the right tool, but for the latest technologies it might not be the right solution. I would tell them to consider all their options before deciding on CA APM, because the configuration, installation, and maintenance are time-consuming tasks. There seem to be a number of technology & support challenges with this tool.

Introscope, CEM and EP Agents

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.

Integration with other tools and out of the box reporting. Customization should be there for reports as this is the main feature asked for several times by customers.

Approx. 4 years

No issues. Easy deployments.

It's pretty much stable tool.

No issues

8 out of 10

6 out of 10

No, I haven't used any other APM Solution.

We work with CA.

Yes, I evaluated others as well - dynatrace. I also read Gartner's APM report.

Use the product how it was designed to be used. It allows you to test your application in a QA setup before moving an app from test to production. And after moving the application to production it encounter the ongoing issues with application which are met when an application is used to it's highest use and you can modify your application until it becomes highly stable and you will be able to submit 100% availability reports for your application to your customers. It can give a good business aspect to your application with 24x7 monitoring of your application.

Environment Profile Agents. I consider this as a trump card of CA APM. We have written almost 20-30 customized scripts to monitor non-Java/.Net calls. We have incorporated DB queries, shell scripts, curl scripts into EP agents involving business specific metrics.

Agent customization. Writing custom tracers, although tedious, gives a lot of flexibility when it's required to capture business specific information from the method calls. Interesting use case that we have also involved a work around to monitor asynchronous calls using custom tracers which would otherwise be very difficult to trace.

Customer experience management plugins. CEM plugins are another important supplement to the business appetite when it comes to business transaction data. Basically we have entire HTTP dumps coming onto the system. If one knows how to extract useful information from it, we pretty much get the entire picture of what's happening on the customer side. CEM is also quite handy when JavaScripts are disabled, although these days JavaScript is not blocked anywhere.

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.

CA APM has a steep learning curve as compared to other tools like Dynatrace and especially AppDynamics and New Relic, but in return it is very customization friendly. You can capture what is important and leave the rest, but it takes time to identify exactly what is important and what's not.

4 years

Agents with certain customized applications can increase overhead. This then requires careful analysis and tuning. The probability for this case, though, is 1 in 100.

Stability becomes a issue if it's wrongly configured. Defining incorrect business transactions and irregular use of SQL normalization are common causes of instability.

Scalability is, I think, one of the strongest points of CA APM. You can control individual agents and control the infrastructure requirement at micro level. This reduces the chances of over expenditure of resources for the tool.

We deployed at a customer site where they were using ITCAM. It was incorrectly implemented, was cumbersome to deploy, and was not that efficient in providing deep-dive diagnostics.

Vanilla setup is easy and quick. It's easy to understand, too. Because it has so many customization options available, services generally end up writing customization. This can be simple to complex, but nothing is too complex here.

CA APM gives a complete 360 degree view of application performance. You can measure important performance metrics related to application components and resources such as CPU, JVM, memory and back-end connectivity. I like the transaction tracer, tracer viewer and history event viewer in CA APM. Transaction traces are very useful and valuable to identify problem sources and isolate them.

Client user interface and user interface dashboard.

I've used it for three years.

No issues encountered.

No issues encountered.

It's very good.

It's very good.

I previously used Wily Introscope in 2008-9, which is now the core software of CA APM.

I searched for open-source software, but I could not find one that provides a complete 360 degree view of application performance.

Go for it as it is very good.

Custom Instrumentation is a good feature (instrumenting classes and methods).

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.

The web-view is a good app that needs to be improved. Also, it's a very useful tool but the architecture could be improved with better intelligence.

I've used it for one year.

No issues with deployment so far.

The tool is very stable and impressive.

One environment can only have a maximum of 10 collectors for supporting a maximum of 4000 agents.

They have very good technical support.

No previous solution was used.

It was a very straightforward setup.

We implemented it ourselves.

This tool has saved the organization a lot of money. I can see an improvement by a minimum of 3% in performance of any given application.

It depends on the requirements and varies accordingly.

We also looked at AppDynamics.

The architecture is very important, along with understanding your requirements.

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.

CA CEM's customer transaction view is valuable because it gives an insight into how our customers networks are performing. The ADA helps in isolating any response time issues on the network and hence, aid in root cause analysis (but we are yet to realise the benefit of it in production). Also, the transaction recording feature is valuable in understanding the paths our critical business transactions take within our IT environment.

The APM tools themselves work well within their respective silo's, but they need to work better in an integrated manner to give the end to end view of any business service.

CA Introscope has performance and data collection issues.

CA Introscope has had performance issues due to large number of metrics collected though it was scaled accordingly.

Customer Service:

Good.

Technical Support:

Average as they need more experts in APM technology.

For cloud monitoring, we had another tool and we had to switch because of the costs and features. Introscope has been running for a while.

• Too complex to get an integrated outcome
• ADA/CEM is complicated as it requires an understanding of networks
• CA Cloud monitoring is complex when creating customer journeys
• Introscope is complex when presenting and grouping metrics for dashboards
• The triage process is complex

It was through a vendor team whose expertise was above average.

Yes we did.

• You need strong architectural skills along with tool-set skills to implement such a tool
• You need to focus on integration as without this, the value might not be as expected
• Start it simple and then add more complex scenarios
• Document and design the system according to requirements
• It's easy to get carried away with all the features, so keep it simple to fit the business need
• Make sure what metrics are required to be monitored is clearly defined. Do not just collect data for all the metrics
• Make sure that RACI is clearly defined with various owners as this can easily slow down the implementation if it is not properly documented and agreed
• There is a lot of external team dependencies, like the application team, support team, network team, architects, an service owners, so make sure that this is documented along with RACI and efforts agreed
• A top down approach is always good, from the end users to actual technical metrics

• I really enjoy the dashboards. The dashboards are flexible and allow me to do what I need and want.

• The quantity of metrics/info that you can capture. For example: metrics about the garbage collection, memory being used for Java agents, etc.

• 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.

I like the product a lot. There are some areas which I'd like to see improved in 9.7 and 9.8. Issues with the workstation interface which could be more productive. Sometimes you have to go back and forth to do some tasks. The UI needs to be more intuitive.

Two years.

So far I haven't had any problems with stability.

I'm happy with scalability. One of our customers uses three collectors and another is using 10 collectors. We haven't had any problems with scalability.

I would like to see them resolve issues quicker.

This was the first one.

CA APM is a great product. I'm really happy that I'm using their technology. I hope to implement it for more customers. Once we provide the solution to our customers, they are very impressed since it provides them with a great deal of visibility. It saves a lot of money by increasing productivity.