The .NET Micro-Agent does not run with other agents, so any functions related to these agents won’t be available.
This article addresses different .NET troubleshooting issues. Additional information about installation troubleshooting can be found in the Installation Troubleshooting article.
Verify that you’re using one of the following supported .NET frameworks:
.NET Framework 2.0 to 4.8
.NET Core 2.0, 2.1, 2.2
Verify that Your .NET Application is running on a 64-bit application. The .NET Micro-Agent only supports 64-bit applications and operating systems.
During the installation process, you’ll be asked to provide the directory path to PDB file(s) on the application host. If these files don’t exist, make sure they’re copied to the path when the application is deployed.
You’re also asked to provide the directory path to the Source files(s) on the Collector host.If these files don’t exist, make sure they’re copied to the path when the application is deployed.
For OverOps to fully diagnose errors and exceptions, we require your source code as well as the PDB. The PDB is critical for extracting variable names and is a crucial part of the Micro-Agent’s work.
Typically the PDB resides with the .exe and .dll files. If that’s not the case, you’ll need to provide the path to the PDB. In the agent.properties file or environment variables, set the takipi.symbols.path property to the PDB on the Micro-Agent machine.
The Source code needs to be located on the machine where the Collector is running. The location of the source file is set in the Micro-Agent machine’s agent.properties file or environment variables by setting the takipi.sources.path property to the location of the source file on the Collector machine.
Open Services, find the service called Takipi Service or Takipi, open the services property, and in the General tab, disable automatic startup for this service.
The .NET Micro-Agent is attached to your IIS application by default when the Micro-Agent installation completes.
If you’re using a standalone application), you’ll need to set the following environment variables manually for the CLR to load the Micro-Agent:
For .NET Core use the following environment variables:
OverOps on .NET enables you to install either a Window or a Linux Collector with the .NET Micro-Agent. Follow the instructions in this article to install the Linux Collector. Then, download the MSI installer from the link below (the link always points to the latest MSI installer) to install the .NET Micro-Agent: https://s3.amazonaws.com/app-takipi-com/deployx/dotnet/deploy/win/Takipi.msi
There are different kinds of VMs that Azure supplies:
- Azure Virtual Machines, which are full VMs for you to access and manage.
- Azure App Services - which are sort of “Managed VMs” - everything is configured and provisioned for you, but you still have different ways to access the machine, and it has persistent memory like a normal VM.
- Full Windows Containers, which are not currently supported in OverOps. Azure App Services and Azure Windows Containers are two different services.
For .Net Core, there currently only support for running on Windows in VM and not in containers. Containers currently play a fairly limited role in .NET Core adoption but will be fully supported in a future version.
The OverOps Collector supports multi-applications pointing to it.
For PDBs, you’ll need to configure the path to them (symbols) on the Micro-Agent machine’s agent.properties file. Set the
takipi.symbols.path property to the location of your PDB.
The source needs to be located on the machine where the Collector is running. The location of the source file is set in the Micro-Agent machine’s agent.properties file by setting the
takipi.sources.path property to the location of the source file on the Collector machine.
Refer to this article for more details: .NET Agent Properties