I was really impressed by Nick Durkin’s (OverOps) very focused and very clear webinar about how new OverOps technology is helping resolve Java issues in production environments with record efficiency.

If you use Java on your servers, it is well worth investing 30 minutes of your time to explore this new idea.

Here is a summary of what’s on offer:

• OverOps has been developed to complement and solve problems that existing APM and log monitoring tools miss - so you could consider it a great way to supercharge the tools you already have. You would be in good company as OverOps have grown their customer based 300% in the past year and look set for impressive growth.
• It records a deeply forensic history of every exception thrown in your production environment as well as 250 lines of debug code that led up to the problem (even if you aren’t actually writing debug logs to disk in production), as well as the associated code and variable state – so now there is no need to have developers recreate a problem in order to be able to fix it, which is HUGE!
• It’s the most comprehensive way we’ve ever come across of handling caught and uncaught exceptions – you can even set up alerts to notify you of specific types of errors, and link those to other tools such as Jira, Slack, HipChat, Pagerduty and more.
• If you wish to automatically raise tickets when certain errors occur or occur in particular sections of your code, that is provided as well.
• So “what’s the catch” I hear to ask – well we were sceptical too – surely grabbing all that valuable Java exception data is bound to risk high CPU overhead? Well the good news continues in that area as well as OverOps guarantees no more than 3% CPU overhead and being a native OS agent rather than relying on the JVM even avoid impacting garbage collection.

Here is a recording of Nick Durkin’s webinar which I highly recommend watching.

OverOps will be released for .NET as well soon – please click here to be kept updated.