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.

I haven't used OverOps before I joined this company. Fixing production issues had never been easy. I highly recommend to use this product for Java services.

As a software developer, I don't monitor OverOps regularly. But, when we detect any error or bug from our logs, we can easily access the "event" that OverOps provides link in logs. It's absolutely convenient and the information provides OverOps is amazing. The snapshot contains all variable values and stack traces so that developers can easily see what's wrong in code or data.

Overops groups similar events. Sometimes it's hard to find the exact "problem" even with a link provided in the log. And I see some lags when we browse events by selecting date/time range and servers. It may be because of the size of our system, but it could be better. I only have OverOps experiences with Java microservices, I am not sure how it supports other frameworks. (e.g. Node.js or Golang )

Just CD for now, CI maybe in the future

Easy to use, nice support, new cool things coming.

Bitter expensive yet, maybe get a little cheaper in the future.

Great tool which has helped our software developers in debugging any issue in very short time. Its greatest features are the dashboard which shows the trend of exceptions in your system and its capability to show stack trace and the variable values preserved. Integrating any new application is also very easy.

I think the configuration of alerts could be simpler.

Its seamless, there cant be a better solution that this to keep system healthy.

It helps debug production issue in seconds, always keeps a eye on system, system becomes much more healthier and cleaner.

Sometimes the alerts links does not works, apart from that i dont see anything.

Code Issued reporting after code deployment

Good enough,it was easy to intregate and good

Good

The product is easy to use while capturing the threads and showcasing the variables from the incidents on debug view. It's also good at capturing snapshots and counts, VM info and logs when possible. - It gives a complete box for debugging and finding the cause for medium-low complex items. - Timestamp and VM are very useful - The issues are upfront before anything goes south

- The logs captured are sometimes inaccurate and also do not have a complete stack trace - The logs are not captured on many instances - there are false alarm captures, where the thread is still alive and not captured - The variable view is a pain to use on the right-hand side, can have a better way like in Eclipse etc - Cannot reference variables - source trigger is unknown/unstructured sometimes - Good for only low medium level debugging, VM logs and Adv level exceptions are not easy to be debugged here

We are always aware if the current release will fall due to real time notifications by overops. Devs just gets notified in slack and we get the details as to why accurately.

We like how it can be integrated to slack. We can attend to all of the issues real time.

Sometimes loading the link for the issues takes time. I think this is normal but I believe can always be improved.

We have Overops both in production and development environment and it's doing its job well.

some intermittent issues are very hard to trace where most pro engineers will somehow reliant with notifications from overops.

If there is, it's always on the loading times when opening the logs. There's always a better way of making the load times faster.

I never miss any alerts whenever I'm on call. All alerts are timely raised and it prevents the system from failing. Best at its job. Easy to use.

Nothing specific. Solves all my purpose.

Easy, quick setup. And the value it brings to development teams in putting secure software into production.

Some things like reusing pipelines could be easier to setup.

Integration with our current process was very smooth to be performed.

Some details in the cloud pricing (cost calculator module) can be improved.

Overops (formerly Takipi) is a great tool that has been a fantastic asset to our debugging capabilities. Super easy to set up, and we've noticed no issues with the minimal overhead introduced. There are many ties where we've been able to solve a problem without having to try to reproduce it just because we had Overops installed.

Easy to use, very focused use case and extremely helpful information.

A bit pricey for a small company with a server per customer to monitor. Probably ok if you have one server for many customers.

i have a great experience with OverOps . we able to slove alot production issue very fast with help of this tool

this tool show us all error of our application at one place .. what is root cause of the issue and where the error coming these all we can check at overops

a little bit ui and mail system show be on daliy based .

Great

This is very user friendly and ease to use.

No proper filters to be saved.More options should be there to save filters

Implementing Blue/Green and other deployments is very intuitive, without much setup or management.

The Infrastructure as Code in Harness could be better implemented, but using the UI is very intuitive.

Real time monitoring, ability to find rootcause much quicker

At times when an issue reoccurs, the error gets logged, but data would be from previous occurrence. Same error, outdated data at times

For issues that may be difficult to reproduce but aren’t yet able to be deployed to Production, OverOps allows our team to find such operational faults via daily/weekly reports that can alert us to previously missed occurrence scenarios, which allows us to address these faults and patch them before code goes to production.

It’s inconvenient that for an enterprise user to sign in, at least in the case of our setup, you need to find a dedicated SSO URL that’s not able to be navigated to from the same page link that we commonly click (via Slack plugin) to go to the fault occurrence log in the first place. The “regular”/non-enterprise login interface is available but this can’t be used for our form of account. This makes accessing the tool a little more cumbersome than other services thus making it a little less convenient to access at a random moments’ notice than a tool like Splunk that has SSO login built in to the same login interface.

Directly get the link on the logs that why the exception occurred

Sometimes it gets very complicated to follow the exact path.

The Debugger mode data for production calls

Sometimes it takes more loading time. Refreshing helps

As a CI/CD product- Harness is pretty solid. The setup process is really easy and once you know to use most of its features- it's a pretty powerful product.

Config as Code is pretty great, especially due to the bi-directional sync with a Git repo. Also the verification step in a workflow could be really useful.

Not having the full GitOps functionality, specifically the reconciliation loop is something that is really missing from the product and would be very beneficial to have.