![]() If you have not sent any traces yet, your API key is displayed at the top of the instructions page for your new application. Check that your firewall is not blocking Raygun.If you're using a browser, look for a 200 response in the network tab of the browser's developer tools. Check that the machine running the Raygun Agent can access the Raygun API at, either using your browser or the cURL command.If the application you are profiling is on a separate machine from the agent, check that traffic is allowed on port 2790. It should be running as a service on your machine called "Raygun Agent". Check that the Raygun Agent is running.Here are some things you can try in order to resolve these problems: If any traffic lights are red, you will receive a message describing the problem. Profiler 圆4 test: 64-bit Profiler found at D:\home\Raygun\Profiler\1.0.\*\圆4\RaygunProfiler.dll. Profiler x86 test: 32-bit Profiler found at D:\home\Raygun\Profiler\1.0.\*\x86\RaygunProfiler.dll. Running rgc.exe -status will produce a result that should look similar to this:Īgent test: Connected to the Raygun Agent v1.0.\*.0 on port 2790.ĪPI test: Connected to the Raygun API at. Ensure that all status checks are showing green.Īlternatively you can run these same status checks using the CLI tool. The basic status checks will automatically run and will display a traffic light for each check. Run some basic status checks by loading the Raygun Profiler Configuration tool and switching to the "Help" tab (it can be found at %ProgramFiles(x86)%\Raygun\RaygunAgent\RaygunConfigurationUtil.exe or by searching "Raygun" in the start menu). What if everything is set up, but there are no traces in the Raygun UI? Try following the steps below to resolve common issues with receiving traces. If this issue persists, please reach out to our engineering support team via the contact page, or click contact us in the app. We recommend setting up code filtering for a selection of high count method calls and seeing if this improves the CPU usage. The high CPU usage you're experiencing is likely caused by a high method call count. APM products will always have an overhead, but our goal is to ensure it's the lowest overhead possible. When restarting the application there is an overhead that could cause the CPU to spike, but this high usage shouldn't persist. $agentpath = "$\rgc.exe" -ArgumentList "-register " -WindowStyle hidden Then download the Raygun Agent zip file to that directory. Download and extract the agentĬreate a directory to install the Raygun Agent to (change this to what works best for you). The Raygun Agent has not been built self-contained as we assume you already have the. To configure the agent and your application please check the setup instructions for your application.įollow these steps to install the Raygun Agent on a Windows Server using. When the installer completes, the agent will be running. When installing with the MSI installer the Raygun Agent is configured as a Windows Service set to auto-start. Windows 32-bit - Installer for the 32-bit profiler only and agent. Windows 64-bit - Installer for the 32-bit and 64-bit profiler and agent. Run the installer follow the on-screen prompts to complete installation. Download and installĭownload the MSI installer to your server. The Raygun APM Agent can be scripted to install silently, see the scripted installation instructions. The Raygun Agent can be run as a Docker container, see Docker instructions for more information.įollow these steps to install the Raygun Agent on Windows Server 2012 or above using the MSI installer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |