Foglight vs. SUSE Rancher

Strengths [Foglight]

• Monitoring, Alerting and Management of on-prem virtualization and physical servers
• Historical trending and baselining are excellent and being able to compare a problem period against the same sets of data for a period when there was no issue is especially helpful as part of troubleshooting.
• Ease of use for end users is appreciated

Weaknesses [of Foglight]

• Creation and management of custom monitors is a developer level activity requiring Groovy skillset
• Less useful for management of an environment where there is a large amount of custom implementations
• Commitment to longevity of cartridges/packs for specific subsystems
• Ability to create custom schedules/alerts/escalations is only available via a 3rd party product (from a former Quest developer) and is not particularly easy to manage/manipulate
• Lack of API accessibility for external integrations to other analytics (splunk, etc.)

Incentivized

SUSE Rancher as a management tool becomes useful on a larger scale. Small deployments not so much. If someone also requires Kubernetes capacity or storage, Rancher is an excellent choice. Also, without Kubernetes' skills, it is unlikely that Rancher deployment is going to be a success. Then again if someone else is managing your Kubernetes capacity, setting up the software's capacity will yield greater control. Rancher is not a very integrated solution similar to others in the market.

Incentivized

• Database monitoring
• Database management suite
• Customization (both monitors and dashboards)

Incentivized

• Public and private cloud infrastructure providers based on K8s CAPI
• REST API that can be used to integrate company services with Rancher
• GUI that is easy to learn and use in daily operations
• Builtin GitOps automation solution based on Fleet project
• It is fully open source

• There are not many problems with this product
• Limited ability to use Foglight itself to solve problems it identifies

Incentivized

• No possibility to snapshot Projects. You can snapshot and restore the whole Kubernetes cluster, but not a Project or Namespace. For this, you have to use external tools.
• You cannot detach the Rancher-created Kubernetes clusters from Rancher management.

Overall it deserves an 8 out of 10. The platform is very easy to use as long as the UI is stable. We have had a few buggy versions in the past. However the CLI is excellent and the platform is simple to manage and maintain. It is easy to deploy and offer for company wide use which increases utilization and ROI.

Incentivized

The documentation is quite complete and there is a very active community that is willing to collaborate and answer questions for those who are just starting out.

Incentivized

We started using SUSE Rancher in the early days and spent a large amount of time getting to know and love it. This was before the days of some of the likes of Amazon Web Services who may now provide a cheaper but less feature-rich alternative to SUSE Rancher, however we have yet to explore this.

Incentivized

The investment for small environments is quite significant. There has to be a compelling case to enhance the areas where SUSE Rancher brings in value to make such a financial leap. There is also a free version to test the value propositions, which will help support the user's buying decisions. More clusters, more volume, more tasks and more complexity in the environment equals more value that Rancher can provide.

Incentivized

• Foglight has a positive impact on my company by being a complete monitoring platform that specializes in risk assessment, user diagnosis and management, and server monitoring ensuring a secure business infrastructure through predictive analytics, query analysis, anomaly detection, behavior tracking, troubleshooting, automated discovery, and more.

Incentivized

• Shortens "Time-to-Market" factor for new business applications or implementing new functionalities. From 1 to 50 microservices-based business applications in 6 years.
• 24/7 availability, generates more money. There are many infrastructure components that are regularly powered-off for maintenance or upgrade, bur we rarely are turning off our downstream Kubernetes clusters where our business applications lives.
• Single Point of Contact with platform maintenance and development Team, eases implementation of new business applications