Oracle Enterprise Manager vs. Sensu, by Sumo Logic

OEM is very well suited for all Oracle products, especially Oracle databases and Exadata machines; even not Oracle hardware, it is very good and displaying high level details. OEM is not well suited for older hardware vendors like AIX, HP-UX, DEC/Digital, Microsoft (sql server). This is a big negative as most large companies have a heterogeneous environment with many different vendor hardware and (database) software products.

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

• Database status. Being able to see which databases are up/down, at a glance, allows us to quickly react to issues.
• Reporting. We report on last backups, daily status, a host of metrics, and compliance levels of all our databases. With reporting we come into the office with a set of "status" reports and we know instantly if a database has issues.
• Metrics. We have a number of KPI's and SLA's we need to meet. Metrics applied to the databases allow us to stay on top of those requirements as well as fix common issues without a DBA needing to log in to assess the issue.

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

• We also use OEM to monitor SQL Server. However, OEM only provided limited features for SQL Server. It would be nice if we can schedule backup jobs for SQL Server in OEM.
• The ability to run SQL queries. You can't run queries in OEM. I have to go to SQL Developer or SQL PLUS to run. queries.

Incentivized

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

Incentivized

Navigation is clean and neat.

Incentivized

I still rate OEM as a must-have tool for central management of Oracle fleet. The pros and cons of the product is prominent. Meanwhile, I also acknowledge that OEM was design about a decade ago. At that time, it did not have the landscape we have today, such as cloud, DEVOPS, machine learning, etc. I hope in future releases, the design will incorporate those features.

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

Toad for Oracle is more suited for individual users who have a strong focus on database development, and it is not as comprehensive as Oracle Enterprise Manager. While it is quite decent in logical database layer tasks, such as schema objects and SQL, it lacks visibility into host level and I/O layer performance stats.

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

I work with OEM SCP team. They are great.

Incentivized

• When we were using Oracle GoldenGate, it made our life easy in terms of visually seeing the configuration and identifying issues easily
• It also makes ASM management very easy instead of doing it in the command line
• Creating policies and implementing certain standard configurations across all the databases is easy

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