Introduction to OverOps

OverOps analyzes code running across your environments to identify critical errors and anomalies and deliver complete root cause. It allows you to trace errors across the source code, determine the variables state, and debug level log statements for any error across the entire call stack. The data can be displayed in three different views, Code View, Log View, and JVM View.

OverOps provides real-time discovery of all exceptions (detected and undetected), logged warnings, logged errors, and HTTP errors. Errors can be grouped by microservice, server, application or deployment, to drill down to the root cause of each event through the Automated Root Cause (ARC) screen, and to create Custom views and alerts focusing on your team's most urgent errors.

Installing OverOps takes minutes in SaaS , Hybrid or full On-Premises environments, and requires no changes to the code or the build. Every new code release or microservice is automatically monitored for new errors, and the relevant developer is notified through the selected channels (Slack, Hipchat , PagerDuty, Jira and more), when critical errors arise.

OverOps offers multiple layers of security to protect the privacy of the collected source code, the variables and data relating to your application, including PII Redaction, private encryption, flexible deployment options and data storage, user and access point control, and secure data transport. OverOps functions as a micro-agent operating between the JVM and processor, which allows it to run with very low CPU overhead both in staging and in production environments.

Introduction to OverOps

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.