Download OverOps

An application, which is generated during the compilation phase. OverOps uses this file to extract variable names. When compiling and running on the same machine, the default location will be near the generated EXE. For OverOps to fully diagnose your errors and exceptions, it needs to have access to the PDB files. If you don't specify the path, the ARC screens will only provide partial and inaccurate information.Installing on IISWhen installing the .NET Micro-Agent for IIS, because of the way IIS runs, you'll need to implement one of the following options to ensure that OverOps can access the PDB files for your application:Option 1. Use the PDBs that exist in the IIS publish folder, for example: C:\inetpub\wwwroot\MyApplicationOption 2. Verify the PDB folder Read permissions for the following users: IUSR and IIS_IUSRS5.4 The Dump files option is selected by default; if you clear it, OverOps will not receive information about any problems encountered by the .NET Micro-Agent.6. Click Next to continue. You can now click Install to begin the installation, or select advanced options by clicking Advanced.Specify an alternative path to the Java installation path (for the Collector) and then click Next. Proxy settings: If required, enter your proxy settings and then click Next. To verify that the proxy settings are correct, click Test connection.Alternative installation path: If you chose to install OverOps in a location other than the default (C:/Takipi), enter the installation path here and then click Install to begin the installation process. When the installation completes, click Finish.Click here to download and run the OverOps MSI installer.From an administrative command line run:msiexec.exe /i [path\to\Takipi.msi] SK="[installation key]" COLLECTOR_HOST=[IP of collector] COLLECTOR_PORT=6060 SUPPORT_DOT_NET=1 SOURCES_DIR=[Path_to_source_directory] PDB_DIR=[Path_to_PDB_directory] ENABLE_DUMPS=1🚧When only installing the AGENT make sure argument INSTALL_COLLECTOR is set to 0.❗️If Overops is already installed you cannot reinstall (msiexec.exe /i) overops with different

This article walks you through the process of installing OverOps on your laptop or local PC .NET application using Windows. Remember to verify that you have these software and hardware requirements in place before beginning.PrerequisitesYou'll need an installation key for this procedure. The key is provided by OverOps for each of your environments.If your environment requires the use of an HTTP or HTTPS proxy to access external web sites, make sure you have your HTTPS proxy settings on-hand, since this is information you'll need to provide as part of the installation wizard.Install the .NET Micro-Agent and CollectorDownload the latest MSI installer for the .NET Agent/Collector - download link.Note that the OverOps MSI deploys the relevant files (.dll, libs, db) under the OverOps directory (C:\Takipi by default). In addition, the MSI sets environment variables for the CLR used by the IIS to load the Micro-Agent.In the Welcome screen, click Next to run the installer.Enter your installation key (aka secret key), which you can find in your welcome email or in app.overops.com in the Manage Environments window.Select the "Install agent and collector" option and click Next to continue. In the next screen, set the source and PDB location:5.1. If you want your sources to be attached automatically to the Automated Root Cause (ARC) screen, enter your source location. Providing the source file location enables OverOps to attach your sources automatically when resolving an event.5.2 Make sure that the 'Install .NET agent' option is selected.5.3 Enter the Program Database (PDB) path to the Micro-Agent (see note below for a detailed explanation).📘Why is the PDB File Path Necessary?The PDB is a file for storing debugging information about an application, which is generated during the compilation phase. OverOps uses this file to extract variable names. When compiling and running on the same machine, the default

Provided by OverOps for each of your environments.If your environment requires the use of an HTTP or HTTPS proxy to access external web sites, make sure you have your HTTPS proxy settings on-hand, since this is information you'll need to provide as part of the installation wizard.Download the latest MSI installer for the .NET Agent/Collector - download link.Note that the OverOps MSI deploys the relevant files (.dll, libs, db) under the OverOps directory (C:\Takipi by default). In addition, the MSI sets environment variables for the CLR used by the IIS to load the Micro-Agent.In the Welcome screen, click Next to run the installer.Enter your installation key (aka secret key), which you can find in your welcome email or in app.overops.com in the Manage Environments window.Select the "Install agent and collector" option and click Next to continue. In the next screen, set the source and PDB location:5.1. If you want your sources to be attached automatically to the Automated Root Cause (ARC) screen, enter your source location. Providing the source file location enables OverOps to attach your sources automatically when resolving an event.5.2 Make sure that the 'Install .NET agent' option is selected.5.3 Enter the Program Database (PDB) path to the Micro-Agent (see note below for a detailed explanation).📘Why is the PDB File Path Necessary?The PDB is a file for storing debugging information about an application, which is generated during the compilation phase. OverOps uses this file to extract variable names. When compiling and running on the same machine, the default location will be near the generated EXE. For OverOps to fully diagnose your errors and exceptions, it needs to have access to the PDB files. If you don't specify the path, the ARC screens will only provide partial and inaccurate information.The PDB is a file for storing debugging information about

IntroductionAfter initial setup and connecting to the environments/applications that you wish to monitor, OverOps starts analyzing the code. This procedure is unique to the initial setup.During the analysis, OverOps displays the following message:Analyzing code is a complex process that involves the OverOps Micro-Agent on the customers server and the OverOps cloud. During the initial analysis, the OverOps service may consume more CPU than usual, but it’s designed to have minimal effect on application performance. Once this process is finished, service returns to regular function.Duration of the Initial AnalysisThe duration of the analysis process varies, depending on the size of the bytecode, quality of the Internet connection, and complexity of the setup, but takes no longer than 30 minutes.During the analysis, any exception thrown in the application will be displayed in the OverOps Dashboard, as 'Processing':❗️Do not** stop OverOps or restart the server during the analysis as this may cause exception data to be lost.Completed AnalysisOnce the analysis is completed, the event thrown during the analysis are fully processed, and you can click on them to open the exception analysis:New exceptions are fully processed within 30 seconds or less.At new code deployment, OverOps analyzes only the parts of the code that were changed." data-testid="RDMD">After initial setup and connecting to the environments/applications that you wish to monitor, OverOps starts analyzing the code. This procedure is unique to the initial setup.During the analysis, OverOps displays the following message:Analyzing code is a complex process that involves the OverOps Micro-Agent on the customers server and

Installation instructionsClick here to download and run the OverOps MSI installer.From an administrative command line run:msiexec.exe /i [path\to\Takipi.msi] SK="[installation key]" COLLECTOR_HOST=[IP of collector] COLLECTOR_PORT=6060 SUPPORT_DOT_NET=1 SOURCES_DIR=[Path_to_source_directory] PDB_DIR=[Path_to_PDB_directory] ENABLE_DUMPS=1🚧When only installing the AGENT make sure argument INSTALL_COLLECTOR is set to 0.❗️If Overops is already installed you cannot reinstall (msiexec.exe /i) overops with different parameters again. Argument Description Default SK Mandatory - Environment Key N/A INSTALL_COLLECTOR Optional - Install Collector 1=Yes, 0=No will install the agent only! 1 COLLECTOR_HOST Optional - Domain name or IP address of the Collector blank COLLECTOR_PORT Optional - Port number on which collector is listening. Typical default is 6060. blank SUPPORT_DOT_NET Optional - Install .net micro Agent libraries 1=Yes, 0=No 0 SOURCES_DIR Mandatory with DOT_NET support - Path to Source Directory blank PDB_DIR Mandatory with DOT_NET support - Path to PDB Directory blank ENABLE_DUMPS OPTIONAL with DOT_NET support - allows dumps file collection by Overops 1=YES, 0=NO 1 .content-body .magic-block-html { margin-bottom: 5em; margin-left: 31px;} .content-body .magic-block-textarea h3, .content-body .magic-block-api-header h3 { font-weight: 400; color: #333; font-size: 17px;} p { display: block; -webkit-margin-before: 1em; -webkit-margin-after: 1em; -webkit-margin-start: 0px; -webkit-margin-end: 0px;}body { margin: 0; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;} .cTable { border: 3px solid #eee; border-radius: 5px; overflow: auto; width: 100%;} .cth { background-color: #f9f9f9; border-bottom: 2px solid #eee; text-align: left; padding: 5px 15px; vertical-align: top; font-size: 14px;}Attach the Micro-Agent to Your ApplicationFollow the steps to attach the .NET Micro-Agent. After the connection is established, the application status will show that OverOps is active. Verify that your application throws exceptions." data-testid="RDMD">This article walks you through the process of installing OverOps on your laptop or local PC .NET application using Windows. Remember to verify that you have these software and hardware requirements in place before beginning.You'll need an installation key for this procedure. The key is

The OverOps cloud. During the initial analysis, the OverOps service may consume more CPU than usual, but it’s designed to have minimal effect on application performance. Once this process is finished, service returns to regular function.The duration of the analysis process varies, depending on the size of the bytecode, quality of the Internet connection, and complexity of the setup, but takes no longer than 30 minutes.During the analysis, any exception thrown in the application will be displayed in the OverOps Dashboard, as 'Processing':❗️Do not** stop OverOps or restart the server during the analysis as this may cause exception data to be lost.Once the analysis is completed, the event thrown during the analysis are fully processed, and you can click on them to open the exception analysis:New exceptions are fully processed within 30 seconds or less.At new code deployment, OverOps analyzes only the parts of the code that were changed.Updated over 5 years ago Table of ContentsIntroductionDuration of the Initial AnalysisCompleted Analysis