1. Home
  2. Product Guides
  3. APM
  4. Troubleshooting
  5. Linux

Linux

When restarting the application, there is an overhead that could cause the CPU to spike, but this high usage shouldn't persist. APM products will always have an overhead, but our goal is to ensure it's the lowest overhead possible. The high CPU usage you're experiencing is likely caused by a high method call count. We recommend setting up code filtering for a selection of high count method calls and seeing if this improves the CPU usage.

If this issue persists, please reach out to our engineering support team via the contact page, or click contact us in the app.

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.

Run some basic status checks by using the CLI tool.

Running ./rgc -status will produce a result that should look similar to:

Running Raygun Agent status checks...
Agent status: Registered
Agent test: Connected to the Raygun Agent v1.0.0.0 on port 2790.
API test: Connected to the Raygun API at https://api2.raygun.com.
TLS test: TLS 1.2 is supported on this machine.
API key test: API key ***lIOlZs5L4Y31PwiC2UZiWA*** is valid

If any checks fail, you will receive a message describing the problem. Here are some actions you can perform to resolve problems:

  • Depending on your installation, list the running services or processes to check that the agent is running.
  • If the application you are profiling is on a separate machine from the agent, check that traffic is allowed on port 2790.
  • Check that the machine running the Raygun Agent can access the Raygun API at https://api2.raygun.com/healthcheck, either using your browser or the cURL command. If you're using a browser, look for a 200 response in the network tab of the browser's developer tools.
  • Check that your firewall is not blocking Raygun.
  • Check that the API key is correct. If you haven't sent any traces yet, your API key is displayed at the top of the instructions page for your new application. Otherwise, you can find the key under "Application settings" in the menu on the Raygun dashboard. Ensure that this is the same key that you used when you installed the agent.

If you are still not receiving traces, you will need to send us a diagnostic session as described below:

  • The log files for the Raygun Agent are located under /usr/share/Raygun/AgentLogs/.

  • To enable detailed logging for the Raygun Agent, add a configuration setting to the appsettings.json file in the directory where you installed the agent.

  • It should look like the following: (other loglevel options are Warning, Info, Verbose, Debug).

{
  "Logging": {
    "LogLevel": {
      "Default": "Debug",
      "Microsoft": "Warning",
      "Microsoft.Hosting.Lifetime": "Information"
    }
  },
  "Agent": {
    "LogLevel": "Debug"
  }
}

Running a diagnostics session will capture the following information and will help us to troubleshoot issues you're having:

  • Snapshot of log files
  • Snapshot of agent settings
  • Agent log files with log level of debug automatically set
  • Trace package and source files generated during the session
  • A trace of data sent from the profiler to the agent

Start a diagnostics session, which is uploaded to Raygun when complete

rgc -auto-diagnostic 300

For more information on diagnostic command options, see the CLI documentation.

If you're still experiencing issues or have any questions, please contact us.

Please provide as much information as possible, for example:

  • The diagnostic session identifier
  • Hosting type - cloud, on premise, Azure App Service etc
  • OS Version, 32 or 64 bit
  • Web Server (i.e., IIS or Node) version
  • Framework type (i.e., .NET Framework, .NET, node.js, or Rails)
  • Framework version
  • For .NET under IIS - InProcess or OutOfProcess hosting type

On this page: