IBM DevOps Code ClearCase vs. Microsoft System Center vs. Sensu, by Sumo Logic

IBM Rational ClearCase might be better suited for a smaller / simpler code base. Larger code bases really slow it down... but then again there are better alternatives out there for source control

Incentivized

For companies with more than 10 Windows devices and needing to standardize the OS, AV, access, share resources, and install software. SCCM is the way to go. This software is unnecessary if the business is all remote users and not in an office-type setting. There are cloud offerings or none to accomplish what a business needs.

Incentivized

• Well suited for raising pagers when you have count-based metrics.
• Well suited for threshold-based metrics.
• Not well suited for tracking events over the day, since graphs and other visualizations are missing.

Incentivized

• Rational ClearCase is excellent for handling versioning and branching. No other tool I've used has the depth that ClearCase has when it comes to handling complex branching scenarios and identifying where certain versions of particular files are within a particular configuration.
• Rational ClearCase handles parallel development of many dependent applications really well.
• The use of ClearCase Views to switch between projects and configurations is extremely convenient as opposed to the local workstation model of the competitors.

Incentivized

• Allows the grouping of devices by user.
• Allows controlling updates being deployed to user devices.
• Allows for the repurposing of machines by being able to load new or updated software on machines that already are in the system.
• Allows us the ability to wipe a machine clean and restore it back to the configuration that was assigned the machine.

Incentivized

• Unique concept as a "monitoring router" that can tie services together.
• Backward-compatible with Nagios environments.
• More of a DevOps focus than Nagios.

Incentivized

• Extremely buggy.
• Sometimes the repository gets locked for no reason.
• Slow.

Incentivized

• Needs web based storefront for requesting new software
• Needs ability to manage the packaging work flow better
• Sometimes is slow to download and there is no indication the entire catalog is being loaded, resulting in confused users not being able to find common software in the available list.

Incentivized

• Cannot be solely used for tracking metrics over time.
• Not a very good UI.

Incentivized

It is not user-friendly for the most part. With IT infrastructure, sometimes it cannot handle excess requests. Every few months, you will need an upgrade in terms of server resources to keep up with incoming alerts and requests. This does not happen all of the time, but it does happen when there are too many requests.

Incentivized

If I had to dislike something about the system it would be how much it changes once you upgrade. This could be more of a problem of mine since I get used to one way and don't like it when it changes so much. I am enjoying the newest update, but it is a mess when you are actually going through the upgrades.

Incentivized

Sensu's customer support was always willing to work with us but never really seemed to learn much from our experiences. I think they get a lot of customers with DevOps IT teams that are willing to put in a lot of elbow grease to get the most of Sensu's architecture. However, despite explaining my continued disappointment with their documentation and the overall flow of the product, I never got much more than a "sorry" and a notice that their documentation was open source if I wanted to contribute to it. The problem, of course, is that you can't document what you don't understand. I'm a former technical writer, so I know that better than most.

Incentivized

If development is centrallized to one location and your company releases hundreds of customized versions of your software per year, then ClearCase is the best tool for managing the complexity of multiple versions of customized software. If your company has globally distributed development, then I'd recommend Team Foundation Server over ClearCase. If your organization uses Agile Methodologies, then I'd recommend TFS with GIT.

Incentivized

We previously used a mix of FOG and Clonezilla to image machines. The biggest issues with these products is that changing one piece of the image required you to rebuild the entire image itself. These pieces of software also did not allow you to manage applications and Windows Updates, causing IT to have to constantly touch machines after they were imaged and update or manage them with a much more hands on approach.

Incentivized

Have used New Relic and Sematext Cloud for APM and for tracking over days and visualizing the issues. But those are very expensive as compared to Sensu.

Incentivized

• Managed code versioning for many years.
• Only one person can edit code at a time - slows processing down.
• IBM is an expensive product to support.

Incentivized

• We have been able to automate our patch management, firmware and other security concerns.
• We have a standardized "image" ensuring our setup is consistent across the enterprise. This alone has saved us in time to support and time to understand how to use our desktops.

Incentivized

• Standing up the Sensu Go server took very little effort.
• Setting up and maintaining the build processes and deployment logic for Sensu assets and checks was somewhat exhausting and resulted in lower adoption among non-DevOps IT.
• The limited web interface resulted in lower adoption among non-DevOps IT.

Incentivized