The tool is completely integrated with other devop tools, making easy to work and deploy what you need and if someone goes wrong he will told you too.

The tool is upgrading and developing more features day after day and some functions isn’t finished yet

From shopping to inception it's been an absolute blast. Lucky, [SENSITIVE CONTENT] have helped every step of the way to transition to the dumpster fire of Jenkins we had, to the new hotness for our CI/CD.

1) It's not Jenkins, 2) ease of use and setup 3) empowerment for developers to be self service 4) pipeline and workflow malleability 5) no plugins to maintain 6)not jenkins

Only con is their can be some feature requests to be done (non product impacting) but, they jump right on those. It's pretty cool to grow with harness. That's literally the only thing I can think of.

The customer support is generally very good. The concept is outstanding. Being able to record runtime state in production for post-mortem debugging is utterly amazing.

There are a number of critical application issues described below, but the chief con of Overops is the price. This is *at least* an order of magnitude more than the value that Overops provides, and is a kick in the teeth for surely most startup-level organisations, particularly ones like ours that helped them grow their business. There were at least 3 occasions in 2+ years of use that Overops (previously Takipi) released updates to their agent (which runs in our production JVM) that caused the whole jvm to segfault. This is a pretty poor track record (and it's more than a little ironic that this happens with a *software quality tool*). In all that time we never succeeded in getting a noise-free or complete exception notification channel between Overops and our Slack installation. It would fail to notify about most errors, and routinely report errors we had attempted to filter out. This persisted despite numerous sessions with app engineers.

Overops is easy to use and understand. If configured correctly, it identifies the errors and problems that engineers should find most important. The UI is straight forward as well.

As an SRE, it helps me to be able to see what errors are being thrown from any particular application. I help manage a stack of at least a hundred microservices, so it is impossible for me to have an in-depth understanding of every single one. If Overops detects an error, it immediately shows me exactly where in the source code this error has occurred, allowing me to communicate clearly to the team responsible for the application as to where they need improvement.

The deployment process for this software was challenging. We had to engineer a lot of custom solutions to keep it running. For example, we used a hybrid approach (some infrastructure in our cloud, some in Overops') and we had to use a handful of lambdas to facilitate the storage and installation of the Overops collector agent and monitoring agent. If all of this could be encapsulated in a single Cloudformation or Terraform document, it could be deployed easier.

A great tool. We implemented it to save the development time on building out a pipeline using other tools like Jenkins. We managed to get a production ready pipeline up and running within a month. Support from Harness is excellent and they are always there to help when required.

The out of the box functionality does as exactly as it says on the tin. No need to worry about how to implement a deployment method for the infrastructure you are running on. Harness simply lists the deployment methods and the infrastructure type you are deploying to and it just works.

Some of the behind the scenes configuration is slightly confusing (e.g. Harness delegate profiles) but once set-up correctly it works like a charm. Adding bespoke scripting to pipelines can be tricky with selecting the correct configuration options to run smoothly. When things go wrong, the debugging could be improved.