We have integrated OP5 into our our process flows and automated a lot of actions into it. Due to the full rest api, we are able to deliver extra features and integrations to our customers and internal teams.

If you already have a monitoring product of the Nagios flavour, you can keep all you config during migration to OP5. Because of the full rest API you can integrate is easily into your process flows (ticketing system etc). OP5 has a great support team with a lot of detailed knowledge of the product.

In very large setups the behaviour can sometimes be different and need tweaking. Work is still being done to the web interface to make it more user and mobile friendly.

Kept my previous knowledge and work on Nagios, quickly moving into a totally modern, easy to use and powerful monitoring environment. Most useful tools are totally customizable dashboards and business services to quickly correlate and pinpoint any critical event.

Keep any previous Nagios-based monitoring you've worked on importing it into a real Enterprise tool.

Would work towards better automatic tools to handle networking devices. Layer 2-3 automapping features would make a real difference.

Easy to get started from scratch (and getting better with new auto discovery feature on it's way) Easy to add new functionality from open source community

Some components are not integrated as well as others (e.g. nagvis for visualisation and synergy for business services) No out of the box support for modern authentication methods (although this is something they are/will be working on)

good insight for our end-customers, consultancy hours for our company

The ability to add "big numbers" widgets in OP5 monitor is a good idea: functionality stripped to the bare minimum (but so effective). The API is outstanding (and cool that adding object using XLS(X) sheets are also supported). Finally a Nagios-based product that makes high availabilty and scaling-out easy and admin-friendly: these aspects are built-in "peers" and "pollers" and should be considered in every high-level design.

The Web GUI (NaCoMa) is easy to understand and stable but not always intuitive in relation to copying/cloning or adding/changing template services.