Foglight vs. JFrog Container Registry

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

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

Incentivized

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

Incentivized

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