OverOps can be deployed in your system either as a purely SaaS solution, as a full On-Premises solution, or as an On-Premises Data solution.
In SaaS mode, data collected from your JVMs is redacted for PII and encrypted locally using your private encryption key before it's sent to the OverOps Cloud to be stored for later viewing and analysis by users. Learn More.
In On-Premises Data mode, data collected from your JVMs is locally redacted for PII and encrypted using your private encryption key before it's stored in a server that resides behind your firewall. The central analysis engine is only used to aggregate metrics and correlate events between different JVMs in your environment. Learn More.
In On-Premises mode (Enterprise only), data collected from your JVMs is locally redacted for PII and encrypted using your private encryption key before it's stored locally on-premises behind your firewall. When viewing an error analysis, information is retrieved directly into the user’s web browser from the on premise storage server without leaving your firewall and domain. Learn More.
The main difference between these solutions is the physical location of the data that's stored.
Two solution components are the primary data repositories in a OverOps solution: (1) the Variable Store (aka Storage Server) that's used for root cause analysis, and (2) the Continuous Reliability (CR) Server (aka Analysis or OverOps Server) that's used for analytics. Together, these components house four types of information that are stored by the OverOps solution:
The Variable Store component houses specific application error information at a point in time, or “snapshots”. This data is sensitive in nature, and is always encrypted at-rest and in-motion.
This data includes stack traces, decompiled code, recorded variables, debug/trace log entries, and environment state.
The CR Server component houses the remaining information listed below. No source code or variable state data is stored here.
- Names for application, server, deployment or version number, class, method, and event type are stored here along with the event message, first and last seen, and Jira number.
- Analytics include error counts and volumes, failure rates, invocations made, average and total response times, along with various system metrics like CPU utilization, thread counts, memory heap, etc.
- Metadata generated for the OverOps interface such as view names, service IDs, event IDs, labels and notes.
- Metadata used for various OverOps functions such as settings for alerts, redactions, publish metrics, code filters, reliability dashboards, and team/user management.
In the On-Premises solution, all data is stored on your servers and behind your firewall.
In SaaS mode, the OverOps Variable Store and CR Server are hosted in the OverOps Cloud powered by AWS. This means all the sensitive data is redacted for PII and encrypted locally using your private encryption key before it, along with analytics information, is sent to the OverOps Cloud.
In the On-Premises Data mode, the OverOps Variable Store is hosted on a server behind your firewall, and the CR Server is hosted in the OverOps Cloud powered by AWS. This means the sensitive data collected from your VM application is redacted for PII and encrypted locally using your private encryption key, and then stored on a server that resides behind your firewall. The analytics information that's non-sensitive in nature is sent to the OverOps Cloud powered by AWS.
In the On-Premises Data mode, when a user views the Root Cause Analysis, or “snapshot”, the user’s web browser that runs inside a private network domain, retrieves and decrypts the data directly from the OverOps Variable Store inside your firewall and domain. Only authorized users from your organization and network who are granted access to app.overops.com and to the private encryption key can access snapshot data. OverOps personnel do not have access to this data.
The local, On-Premises Variable Store does not connect to, or get accessed from the cloud, and can be completely separate from the public Internet.
Updated over 3 years ago