The DAW, especially, is very nice. Even DXP has an agent migration feature, which is technically very nice. 

Initially, Broadcom said that migration was not feasible and that it would be a fresh implementation. But now we have found that instead of deploying a new agent, removing the 10.7 agent, and deploying the new agent, we can actually point the agent to the new server, the new DXP server. 

So, we don't need to remove the old agent and deploy a new one. We can just redirect it. This saves a lot of time and effort on the application server side and on the Wow agent where we serve. So, it's good in terms of migration.

And as an application of DXP itself, it's pretty good, comparatively. It's kind of on par with AppDynamics and Dynatrace, apart from the AI and ML capabilities, which are kind of missing. 

Broadcom is promising and going in the right direction, but still not up to the max of the industry standards whereas Dynatrace is, with a single click and a few hours of observed availability, showing end-to-end visibility.

There are multiple users related to Broadcom DX Application Performance Management. During any severity or incident, our company's customers have dealt with their applications with the help of the tool, and they also use it for daily alerts, team management, and reporting.

On a daily basis, our company's customers use the tool for dashboard creation and reporting. The tool is also useful for managing any incidents, or when any high utilization happens, as it triggers the alert, and after the users get the alert, they take care of the necessary steps on the applications. Basically, there are three types of use cases when it comes to Broadcom DX Application Performance Management. The tool is used to manage in case any drill down on severity is required, to take care of reporting, and to monitor the dashboards.

In the future release of the product, I would like to see the tool have better capabilities in terms of dashboard creation and reporting. Dashboards and the reporting part are related to Broadcom DX Application Performance Management. The dashboards need to be auto-populated as they happen in any generic kind of APM tool. There is a need to build an easy way to generate the report related to application utilization.

We primarily use Broadcom DX Application Performance Management with Java and JBoss, and for approximately 90 percent of our usage, we utilize the Introscope model with OpenShift. One issue we've encountered is that we're unable to use agents in OpenShift 4, which only affects agents installed in the image. This is one of the reasons we are considering updating to a more recent solution.

Monitoring the application layer for the various application teams. In our organization, we have the centralized monitoring team, and we work with a whole bunch of other teams. The application is trying to help their products get to know their applications monitored to where they need to be.

We have some people that know how to use the product fairly well, but only the older functionalities. Then, we have a lot of newer people that are using different monitoring tools. Some are okay and some do not really know a lot of the functionality, so we have been trying to help get better traction with that.

Easily find bottleneck of our applications. We have a BSR (Business Services Reliability dashboard), so we can find out how our business is behaving, how we are getting the orders and how many errors we are getting. We find out how reliable our application is.

It's performed very well.

It is a first line of defense for application performance monitoring and management to understand the customer usage patterns. When we get any major incident or a production issue, we can isolate the area where there is a probable problem. 

Our project is a logistic domain. DX passes all the infrastructure components which are managed by the Broadcom team. We are just deploying the different kinds of application versions, e.g. related to .NET, WebLogic, and other application agents.

We are also monitoring the infrastructure agents in Windows, Linux, and Unix which are combined into one infrastructure agent. We also do monitoring whenever the agent doesn't have the package that is supported through the infrastructure agent, e.g. Kubernetes from the Broadcom DX Application Performance Management perspective.

We have an e-commerce application. It's more of a business-to-business model, and employees of most companies come to our websites to order product. The APM tool allows us to monitor performance of that application, where are the pain points, where are the slowdowns, to focus on where we can fix those.

Product performance is awesome. It's covering all aspects of the application; good database metrics and internal application metrics. Just tons and tons of data.

I use Broadcom DX Application Performance Management for performance optimization, tuning, problem analysis, troubleshooting in production, and load testing support.

We are a network operation center. We measure the performance of the system.

We monitor the network and the application performance for any degradation in the performance of the system. 

If it is down then we need to get notified very quickly so that we can inform the consulting team to resolve the issue. 

We also have to inform the management of the incident management process, and the customer response team to notify the customer's agents.

A new concept (APM) to be introduced in our workplace which was never there before. Never had visibility into application (layer) performance. Prior to this our main focus was on server and network hardware monitoring. Having visibility into app performance and backend layer has been quite an eye opener in putting together the entire picture for management. We've put together a complete portrait from an ESM (Enterprise Systems Management) perspective with Broadcom/CA Tools.

Monitoring of customer applications. 

It has performed well. I won't necessarily say better than other solutions, but there's more focus because of the customer applications. 

A good example for us is Hurricane Irma. We have service territory that was impacted and our executive dashboard for APM was up and everybody under the sun was watching that, and keying off of that, for issues that were popping up, because we were performing storm restoration.

We look at the load patterns and server health by looking at server health parameters. Heap memory is of prime importance as well as how the heap is behaving and how the memory is behaving under load, as well as the CPU utilization. These are generally the parameters we will check.

We are using CA APM for Layer 7 applications, like SQL, as well as application debugging.

We are using the on-premise and cloud versions of Broadcom DX Application Performance Management.

It's for monitoring application performance and end user experience.

I'm checking customer experience, how they experience our website and how they use the systems inside the company. Customer experience, outside and inside.

It performs okay.

My users are satisfied with this solution, most are financial institutions such as banks or card processors and telecom companies.

The primary use case is for the monitoring of business applications in production. Banks use it for monitoring Internet banking solutions, internal back-office applications that have high number of users distributed on many locations, monitoring back-office applications for card transaction processing, and also for front office applications monitoring. DX APM is also used in a test phase of apps life cycle especially during a performance testing. 

Mainly for the application performance, the Java agent, and metrics collection.

It has performed well so far. Operationally, there are occasionally bugs in the agent, so we have to patch those or get those upgraded.

It's for application monitoring and it's extensively used for application performance management.

It works very well and we can get to know how the application really behaves internally, and based on that we will to know who the culprit is and figure it out.

Java-based enterprise application servers monitoring: for example, WebSphere Application Server, JBoss EAP, WebLogic.

We are a solutions provider. Obviously, depending on the customer, we are monitoring applications. 

We have deployed to several customers and they have all found benefit in seeing how the application is performing, what components are performing worse, and where they can improve. DevOps is definitely a big play for us. 

They are seeing that benefit to having the APM product instrumenting their applications and getting that insight before it goes to production. It is working well.

Our primary use cases are for IT monitoring, alarms, and tracking the behavior of the IT system. We are customers of Broadcom.

The solution is primarily used for monitoring such as network monitoring, application performance monitoring, infrastructure monitoring, et cetera. We also use it for the AI/ML to understand the kinds of effects that are coming from their different monitoring solutions. It can give a root cause analysis using multiple data points. It can monitor for and explain downtime and reduce the work of the ID operations team as it provides them with a root cause analysis for downtime events.

We primarily use this product for monitoring our IBM WebSphere environment. It more generally monitors all of our JVMs for our web environments, used for all of our websites.

This solution is an awesome monitoring tool for application monitoring, customized dashboards, and alerting. Many features are used, including its ability to dive into application data, the user experience, the application flow map, transaction traces, and the team center.

We use APM to monitor our production, our QUAIL Java environments, and our web framework environments.

It is heavily utilized. It functions very well. We look forward to new features, because as technology grows we look to incorporate some of that newer technology in our monitoring solutions as well.

Primary use case is to monitor our critical applications.

It performs pretty well. Right now, we use it to create dashboards and executive view dashboards, so our higher up managers can take a look and see where our application status stands. It creates transparency. We are satisfied with how it performs.

I use it to track performance on the production environment and QA environment.

We are using it for application performance monitoring. We have about 2000 applications and mobile applications. We are even using it for applications in the cloud now. So, we are pretty happy with the product.

Primarily the product is used for monitoring the Business critical banking applications of my Organisation like Internet Banking etc.

Monitoring application performance.

Monitoring of our internal business applications completely, through all business processes.

My use case is that we have system called "Systemwalker", so we are trying to collaborate that product with APM. We are trying to use the triage of the APM, and we are still evaluating that system. 

It is performing okay. We are waiting for the new release. They have not released that yet. 

We are using multiple functions like monitoring applications, files, storage, and DBs.

Performance is very good.

We are using it for application performance management (APM).

We use Broadcom DX Application Performance Management to monitor applications.

It is a monitoring tool used for business intelligence.

• System incident analysis 
• Performance monitoring

We run a very large OLTP system: Six IBM AIX 780 high-end applications and DB servers. Daily transaction amount 100,000,000 per day.

The use case is for crash analytics. We want to know what went wrong, and what is the area in my code that I can improve on.

In terms of performance, we are still evaluating it, but so far so good.

We are a service and solution provider, and this is one of the monitoring products that we implement for our customers.

The primary use case is network monitoring.

I have tested Applicare on Java Applications and it performed exceptionally well.