DX Unified Infrastructure Management Reviews

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 CA tools allow to me to get into detailed transactions for custom ranking, and be able to make predictions. It also gathers data. Some other tools may be good at one area, but not good overall, including the mainframe.

CA has been very famous for the mainframe. I think that's actually the edge, by the way, for CA products, as there are many, many dotcom products that don't touch mainframes. I think that CA should still keep that. 

The area where CA is changing is, I'll give you an example. The fresh technology should have been out a long time ago. But it appears to be we're catching up on the UIM, because Microsoft basically says they are not going to support the fresh, starting next year. That means they are a little bit behind on the waves in the architecture, etc. I think that can be improved.

Another thinking is, if the developer can get to the level-1 engineer level, they will develop a better product. I suggest the developers at CA really work as a level-1 engineer, because then you have a different sort.

• Cloud monitoring

• Easily skinnable
• SAP monitoring
• Reporting Tools
• Probe packages and probe deployment

Through action automation (using NAS and robot actions) we got reduced operational effort, improved operative tasks, and optimization of resources.

I would like to see improvements in the maintenance mode area. I would like to set only a probe from a robot or group in maintenance or place profiles from probes in maintenance. Making a GUI with criteria such as selection by robot/hub/probe etc.

I've been using it for five years.

No deployment issues encountered.

No stability issues encountered.

No scalability issues encountered.

We didn't use customer service.

10/10 CA Support team is excellent we get from them issue resolution within a single interaction and anchoring alternative solution.

Previously we had multiples tools to monitor IT infrastructure and other apps e.g ManageEngine to monitor databases, Nagios to monitor telco devices (switches, and routers, etc.) We switched to CA UIM because we had a lot of issues when we tried to correlate events and get unified metrics from our monitoring tools databases, in the same way we had maintain multiple tools and open tickets with multiples vendors.

Initial setup was straightforward. Installing and deploying software was very quick and easy. We have experience with similar tools implementation.

We did the full implementation in house.

Licensing model and packaging:

Server pack - Charged per server.
Server and application pack - Charged per server.
Service response time advanced pack - charged per site.
Ping pack - Charged per device.
Network advanced pack - Charged per device.
Flow analysis - Charged per device.
Storage pack - Charged per terabyte.
Ecometer pack - Charged per device.

We also looked at OpsView and SCOM.

Monitor governance and solution sizing are key topics to start solution implementation.

We find the flexibility and portability the most valuable features. We are using it for synthetics, E2E, and its ability to monitor itself. We're getting rid of one product and bringing UIM to take over. We're using it for our application SLAs. We're writing, synthetically, all these transactions that can perform to our service levels. We are monitoring application performance with UIM at this time.

Currently, the environment that we're using it in is strictly application performance. We want to be able to give the business visibility on how the application is performing, whether it's in the cloud, a simple URL hit, or a thick or thin client. We're using it within the Citrix environment also.

Right now, I don't have any new features in mind. We’ll see once we get in and start playing with it a lot more in depth. We do have another team that's looking at implementing it, so that may be something down the road on which we can give more information.

The product out of the box is great. We were very impressed with it. We have only used it for what we need so far; the SLA piece for monitoring our apps.

We heard at a recent CA World conference that APM integrates with UIM. Spectrum also integrates with UIM, depending on the release and can actually cross-correlate alerts. When we have APM and Spectrum and we get them on the right versions, we'll be able to link all three together. That would be an improvement.

We have not had any stability issues.

We have not had any scalability issues.

We have not needed to use technical support for UIM. It's been great.

The other product was at the end of its life, so we had to find something.

The initial setup was straightforward. We had the engineer on site to walk us through the way the environment would be set up. We had it set up in a couple of days. He sat with us and went over the architecture, the way it was laid out, what our goals were, when we upgrade, and what we could do in the future to make it more beneficial.

Because I don't know the bottom line, I'd say it was a very good investment that we made.

We looked at other solutions, but they really didn't meet our needs. Dynatrace is one of them and Micro Focus may have been also. UIM met everything we needed and more when you consider other areas and departments with whom we work closely. It actually helped them out as well. It's not just our department utilizing UIM. It's going to scale across the company.

Give UIM a try. Build out a PoC environment. Play with it. Utilize all the probes you can that you think would meet your company's needs. Take advantage of it.

When choosing a vendor, we look at technical support.

• CA UIM Solution is very easy and fast to use, it offers both agent-base and agent less monitoring options. UIM have lots of monitoring options that help us to manage our Enterprise heterogeneous monitoring demand.
• Database monitoring - helps us with monitoring critical database instances. We have many different databases from various vendors -- Oracle, SQL, Sybase -- and UIM helps us with managing all of them in one place.
• Infrastructure monitoring - Helps us to manage the data center, critical Ci's and v Center.
• Application monitoring probes - we are using Middleware application probes for monitoring critical apps.

It helps us to monitor critical servers, applications services, etc. We have many databases, hundreds of probes, and thousands of applications. This tool helps us manage all these and gives us insight into what's going on in our infrastructure.

There are several areas for improvement, among them are --

• Reporting capability - We're unable to drill down to the specific data that we'd like. We're also not able to get some data, such as trends, that we want when trying to determine root causes of issues in our applications. This is particularly frustrating because we have so many applications that we use and depend on that we need to know with some certainty what the issues are affecting them.
• End-to-end application monitoring probes function - We're quite large with over 500 probes, and there's no ability in UIM to monitor all of them through our many, many applications. We're relying too much on middleware applications to do this.

There was no issue with the deployment.

There has been no issue with the stability.

There have been no issues scaling it.

8/10

I've used them many times, and they were OK.

It's very easy to implement and use. If you want to onboard devices and applications, it's just drag-and-drop. Very user friendly.

In-house.

It has helped us cut manual efforts and reduced manpower. It's helped us with automation. ROI 50%.

This is very good product for monitoring as it has lots of functionalities and probes.

I primarily use DX UIM to capture performance data and faults.

DX UIM's reporting and customization need to be improved. There are also issues with its stability, and it requires a lot of effort to execute and implement something.

I've been using DX UIM for two years.

There are issues with DX UIM's stability.

DX UIM is scalable.

DX UIM's technical support team are good, but there's a shortage of resources, which means they can be slow to respond.

Positive

The initial setup was difficult compared to other tools available in the marketplace. Deployment took three to six months for us as we were working on complex architecture, but on a simpler one, it would take around two to three weeks.

I wouldn't recommend DX UIM to other users because of its issues with reporting and stability - SolarWinds would be a better choice. I would give DX UIM a rating of seven out of ten.

Server and database availability as well as performance monitoring in my environment. We also monitor URLs using UIM.

We now use only one console to monitor all servers, the database and the network. It has allowed us to consolidate four previous tools (BMC, HP, SolarWinds, Nagios).

It is easy to implement but requires good planning. If you don't plan the number of probes it can lead to an event flood. It is also reliable when it comes to monitoring.

Reporting capability can be improved especially when it comes to availability. Additionally, automatic baselines can help reduce the count of alerts.

Monitoring the servers, the infrastructure and we also monitor applications with a specific probe doing Synthetic transactions. We use a dirscan probe to monitor files to make sure that they transfer at the correct times, and it will send alerts if they don't. We use logmon monitoring and we use the event log monitoring processes. We monitor processes for up/down state, CPU usage, memory usage. We use the NT Services probe, the monitor services on the Windows boxes. That's to name a few.

Regarding performance, we've had some struggles with it at times, but we get a support case opened up and support has been very good at helping us resolve the issues that we encounter.

The monitoring of the applications to let our business know when things are performing and that they're up and available.

We have less downtime. We have alerting to let us know when disks are filling up so that we get that taken care of before it becomes an issue and is noticeable to customers.

In the UMP, certain devices will show up multiple times and they don't correlate correctly. That's one of the issues. 

Sometimes the probe, on its first release, we will find some bugs with it and notify support and then they escalate it to the upper level and they get things corrected.

The dashboarding. They're going in the right direction, getting away from flash and using the HTML5 with the Cabbie dashboards. That has been very helpful with us in developing dashboards. But maybe some additional out-of-the-box dashboards with different standard tools that people are using. 

The one thing that our company has started to use is MarkLogic, and they don't have a specialized probe for that. We've reached out to them and put feedback on the community trying to get votes on that. But so far, it hasn't gotten a lot of votes.

The stability is good. They have an HA feature, high availability. And whe we were setting it up with use of support, we decided not to even set up that functionality because it's very seldom that we have a problem with it going down.

Scalability has been fine. As the new servers are brought on with the new MCS tool, it allows us to get configuration on the servers put on in a faster time.

I'm happy with the technical support we've received, and their response time.

We actually had UIM before it was UIM. It was Nimbus in 2004. Then it went to Nimsoft, then CA bought it and then rebranded it CA UIM. When it got brought into our company, in 2004, we used it for Synthetic transactions, to monitor the email and different products on the web, and the response times to that. And then we were using a different product for our network monitoring. 

We wanted to try to eliminate some of the excessive tools we had so we moved our network monitoring into CA UIM at that time.

When we first moved on to UIM, and brought the network monitoring in, at that time, the event correlation product wasn't built in - so one event happens and then it triggers three or four other things. And when we were doing that, the product we were getting rid of did do that. CA had said that that would be on the roadmap. It seems like the roadmap has changed now, and they're doing more of the event correlation with Spectrum, but we don't own Spectrum. So we have a little bit of a struggle there with the event correlation, and it seems like CA is not doing the event correlation with their SNMP Collector probe. They've moved more towards Spectrum.

It was straightforward. I and another person set up how the servers are going to be set up and then we got approval through CA. We asked them if that looked good to them, and they came back and with what we had set up, they didn't have anymore recommendations. They thought that what we're going to do was going to be successful.

When our company is looking to invest in a vendor, our criterion is that we will try to stay with a vendor that we have a relationship with already. 

I rate it an eight out of 10 because the ability to configure the probes is much easier than with other products. Before we went with the UIM product, I had to evaluate other products and the configuration of those was much more difficult than with UIM.

I would advise, because they have the new SaaS product - and I have a feeling we're going to be looking at that at our company also - doing a demo of the SaaS product and see if that meets their needs.

UIM is very configurable. You can do lots of things with it. Now that comes with a caveat, right? If it's highly configurable, generally speaking, it's not easily cookie cutter place-able, right? There's a lot of programming that comes along with it. Once you figure out that piece of it, you can do pretty much anything with it.

I don't think it’s very complicated. It takes time, just like anything, but once you figure it out it's pretty much the same for each individual section of the product. It's just applied in a different way.

Currently, my reach is just the Windows servers, but soon it will be all types of monitoring and automation, including Windows servers, Linux servers, and applications that live on those servers. They are the pieces that I'll be looking at.

Currently, without going into too many details, we are leveraging the product to perform self-healing. If there's an outage of some sort or maybe even a metric, if you know what metric to monitor, to tell you if something is about to fail. You can take action to prevent the failure. Instead of being reactive, we're being proactive. Even to the point of being proactive and realizing these are the metrics that tell me, “this system is about to become unhealthy”, and reacting to that rather than reacting to an actual outage.

I do a lot of coding outside and inside of UIM. The biggest, most annoying problem, if you will, is the ISE that's embedded in UIM. It is very limited in its scope and what it's capable of compared to even some of the more primitive ISEs that are on the market. Personally, I'd like to see more time spent on the ISE, whether that's going to be in their new product, which is Unified Management Portal.

I've heard from up the food chain that they're going to be changing it and it's going to be more integrated with UMP. But I'd still like to see more improvement on the ISE, especially from my perspective because I primarily work in automation. The ISE portion is very big in my space.

In PowerShell, for instance, their ISE is, in my opinion, pretty good for what it does. You can tab through all the options versus in UIM's ISE, in order to do that there's actually a pane on right hand side that you have to click through. Even then, what the actions that are listed there do is not described well enough.

UIM is pretty stable. Everything has its quirks. As far as the monitoring platform as a whole, I've worked with a lot of different programs and it's pretty stable. It's up there with the top.

I have yet to run into anything that it couldn't scale. We've scaled it massively since we've started using it.

Technical support is very responsive. They're quick to escalate an issue that they don't know how to solve themselves. Where other companies fail, I think, is getting a customer to somebody who actually knows how to fix the issue. Whereas with CA, it seems like every time I open a case, they're very quick to find out what the actual problem is and get somebody in contact with me that actually knows how to fix the issue. No matter whether that's somebody actually on the technical support team or if it's a senior principle consultant that's outside of the technical support team. It seems like they're always very responsive to get that done.

For the most part, initial setup was straightforward. It's very one-step-after-the-other to get the initial basic monitoring portion of it setup. Then, obviously, there's a lot more things that it can do after that. That takes a learning curve.

Choosing UIM wasn't my decision. That came from above my pay grade.

Last words of advice. It's a great tool. One way I painted myself into a corner was when I first started using it I thought that it only can do this this one certain way. With UIM, the one thing I've learned is there's hundreds of ways of doing it and they're all right. It's just a matter of which way gets you there the fastest I guess.