Before beginning the OverOps installation process, it’s important to understand two key concepts, because both will impact the steps required to start using OverOps:
- The OverOps component architecture and logic
- The available deployment models
The OverOps solution is comprised of four logical components:
The Micro-Agent is a component that's installed alongside an environment and monitors your applications. The OverOps Micro-Agent attaches to a running application or environment (JVM or .Net Command Language Runtime), which can have hundreds or thousands of deployed agents:
- The Java Micro-Agent supports a wide range of JVMs and leading web containers
- The .NET Micro-Agent supports .NET Framework 2.0 to 4.8 and .NET Core 2.0, 2.1, and 2.2
The Collector is the endpoint to which the Micro-Agents report.. A lightweight server that receives the application code and variables captured by the Micro-Agents, the Collector offloads code analysis and processing from production nodes. The application code collected is then redacted and sent to the Continuous Reliability (CR) Server (aka Analysis or OverOps Server) for indexing and graph analysis. Captured variables and decompiled code are then encrypted and sent to the Variable Store (aka Storage Server). The OverOps Collector is designed to support hundreds of concurrent agents connecting from multiple environments (e.g., QA, production, etc.).
A high-availability cluster for code analysis and run-time anomaly detection, the Continuous Reliability (CR) server is available via SaaS or can be installed On-Premises in your data center or private cloud. the CR Server stores the data received from Collectors. This always-on “service” provides you with UI and backend services, as well as the Dashboard from which your users will work off.
The Variable Store is an always-on “service” that stores the snapshot information and symbol tables locally - redacted for PII and privately encrypted under your control. The storage-server is hosted on your premises and does not need to connect to the cloud, which means it can be completely separate from the public internet.
OverOps offers three installation options - SaaS, Hybrid, and On-Premises. The following matrix provides a quick summary of summary of the Deployment Model and Logical Components:
- 'Customer' refers to items that are installed and managed by the Customer.
- 'OverOps' refers to items that are fully managed by OverOps.
In SaaS mode, data collected from your VMs 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 Hybrid mode, data collected from your VMs is redacted locally 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 VMs in your environment. Learn More.
In On-Premises mode (Enterprise only), data collected from your VMs 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.
As part of our new On-Premises installation, we bundle Grafana, so if you're currently using an external Grafana instance, follow these instructions to learn how to switch to the bundled Grafana.
Please review the Software and Hardware prerequisites before installing OverOps. Depending on the deployment method you select, some of the hardware and software prerequisites will differ.
After completing the installation, you may want to check out the advanced installation information.
To learn more about the way the deployment models differ, check out the article How do the OverOps Deployment Options Differ?.
Updated 6 days ago