F5 Distributed Cloud Network Connect is a solution used to more easily and securely network across public clouds, hybrid clouds, and edge sites via an agile SaaS-based service. Users can rapidly connect instances deployed across multiple cloud regions and/or different cloud providers using Distributed Cloud Network Connect and its automated provisioning, integrated service stack, and end-to-end visibility. Cloud instances will be connected in minutes and always visible for rapid troubleshooting.
N/A
Oracle Enterprise Manager
Score 7.0 out of 10
N/A
Oracle’s Enterprise Manager is an on-premises monitoring and management tool. The console is designed primarily to manage other Oracle products, it but can integrate to manage non-Oracle components as well.
F5 Distributed Cloud Network Connect provides Intent-Based Policies and Unified Operations which is equal for all customers . Complexity is eliminated and common services and rules are provided across clouds and on-premises settings with the help of an integrated service stack and automated deployment. There is nothing specific scenario where we found that it is not suitable for current environment.
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.
Monitoring Templates: There are out of box monitoring templates for each target types, you can customize them or use them as it is.
Administrative Groups: This is a relatively new feature in OEM Cloud Control. This lets you create and manage your targets and monitoring templates smarter and with less re-work.
DB Monitoring: There are so many cool DB monitoring features and visual graphics, that it can be used by both DBA and functional people to see what's going on in the database.
The support model needs a quite a bit of work. I personally have experienced an outage on the platform. due to mis-configureation Although the outage was due to engineer error it took over 2 hours before we were able to speak to an engineer
Proxy v2 protocol to allow our organization to capture and view the source IP address
Bugs. Every version we upgrade to has a number of bugs. Some stop us from rolling to production OEM (we have a sandbox OEM), some are simply annoying. If I could improve on one thing, it would be for better QA from oracle before releasing each version.
Flash. I'm told that they are moving from Flash to Jet in version 13.3 and beyond (we are on 13.2 currently). That change cannot come soon enough. The OEM pages load SO slowly due to Flash.
Hierarchy Groups. OEM allows five Hierarchy groups. A Hierarchy group allows a top down metric/rule roll out. However, they limit you to five. I'd like to see them open that up, so that we can have any number of custom groups.
It's great! It does everything and anything you would want it to do. It can monitor things which doesn't comes out of the box by adding plug ins to it, for example, you can even monitor Oracle GoldenGate Replication by adding a plug-in to OEM Cloud Control.
Overall, F5 Distributed Cloud Network Connect is responsive and has many features. There is minor clunkiness in how certain scroll bars are layered. This may cause some adverse experience when trying to manage this product through a zoomed browser. Page loading and refresh timers were all very much responsive. There is a good amount of feedback from the interface as well.
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.
This software as a service (SaaS) links, divides, and protects network traffic over one or more edge sites, data centers, and public clouds. It offers the adaptability needed to operate across many transit choices, such as the F5 Global Network, private corporate networks, and cloud provider linkages. Additionally, faster time to resolution and more effective issue management are achieved by end-to-end monitoring and troubleshooting.
Being an Oracle shop using Oracle Database and MySQL, management console from Oracle was a better choice than IBM or Microsoft even though we do use Microsoft Azure and storage/servers from IBM (on-prem).
We are a 7x24 shop. Oracle Enterprise Manager Cloud Control helps us meet that objective by proactively warning us before issues cause down time. Things like disk space, archive log issues or temporary table space issues.
Spreading the use of this tool outside of the DBA group has allowed us to not hire additional personnel for those teams. Over time, as folks have retired from our operations team, we are not replacing them. Instead we have used OEM Cloud Control to automate tasks.
We also now have the tools to measure up-time by using specific measurements inside of OEM. This allows us to report real numbers to management.
