1. Two factor authentication and data encryption - When you install OverOps, you privately generate a 256-bit AES encryption key that is kept behind your firewall. All code and variable data collected by OverOps is encrypted before it leaves your machine. Data is only sent to and stored by OverOps in its privately encrypted form. Decryption of error data from your servers only happens behind your firewall using your private key.
    #
  2. User controls - The team management console gives you control over which team members have access to the service. You can also control the IP addresses from which they are allowed to access the service.
  3. Error data collection - OverOps only collects code and variable data that is directly related to an error which occurred within your application. While OverOps collects analytics for 100% of all errors in your application, debugging data is only collected for a configured number of samples.
  4. Code analysis - When you load new bytecode into your JVM (identified by its unique binary signature), it is locally converted into an abstract graph which cannot be reverse engineered or executed. This is the only code-related information that is used by the OverOps hosted analysis engine to correlate events and orchestrate data collection across your cluster.
  5. Personally identifiable information filtering - OverOps automatically employs a set of customizable filters to redact personally identifiable and business-sensitive information before it leaves your local production machine. You can fully control the variable patterns, classes, and fields for which information is never collected.
    #
  6. Firewall friendly - The OverOps collector process only communicates with the hosted analysis engine using outbound HTTPS port 443 to a set of fixed IP addresses. OverOps does not require opening a port in your firewall for incoming communications.

On-premises storage

Control where collected error variable and code data is stored, either in the cloud or on-premises.

In the on-premises configuration, code and variable information collected for errors on your machines is transmitted by the local collector process to a server which resides behind your firewall. This server does not communicate with, nor does it require network access to, the OverOps hosted analysis engine, which is only responsible for correlating events across nodes and alerting on errors.

Whenever you are alerted about a new error or open an existing one from your dashboard, code and variable information for that error is pulled directly from the on-premises server without ever leaving your domain.

Other questions? We're here to help. Use the live chat or email us at hello@overops.com

Installs in minutes

Runs as a simple Java agent.

No code or build changes.

Linux, OS X, and Win. Java 6-8.

User already exists Log in

Java / Scala