Relic Solution: The .NET Agent is Not Reporting: A Troubleshooting Guide

This is a troubleshooting guide designed to walk you through the most common issues that can cause an installed .NET agent (Framework or Core) to fail to report to your New Relic account. If you’ve installed the NET agent on your server and don’t see data from your applications in your account or if you have a previously installed agent that is no longer reporting, follow this guide to find out why.

:grey_exclamation: For those of you who are here because you have a .NET Framework agent that was functioning normally, then suddenly stopped reporting, begin by checking for a profiler conflict. That’s the most common reason a functioning agent would suddenly stop. If that’s not it, come back here and continue below.

1. Make sure you’re using the right .NET agent.

(Don’t skip this, you might be surprised)

2. Check if the agent is creating logs for your application

After checking for logs, you should be in one of these three situations.

Make sure you’re in the third situation (“Both a profiler log and agent log are present”) before you move on. The .NET agent won’t report data to your account in any other scenario.

  • No logs for your application at all - This means that either the agent is not installed correctly, you’re not using the correct agent, or your application is not compatible with the .NET agent. To troubleshoot, select your agent below.

  • A Profiler log for your application is present, but not the agent log - This means that the agent is installed correctly (it is successfully attaching itself to your application), but either the agent is configured not to monitor the application, an error is preventing it from monitoring the application, or the agent needs custom instrumentation to be able to monitor your application.

  • Both a profiler log and agent log are present - The agent is installed correctly and actively attempting to monitor your application. If you’re in this boat, read on.

3. Check if the agent is connecting to New Relic’s servers

I highly suggest that you work from newly-generated logs (empty out the logs directory and generate new ones) so you’re sure you’re dealing with up-to-date information.

Now, open up your application’s agent log (newrelic_agent_*.log) in your favorite text editor. We’re going to do some searching.

Search your agent log from the bottom up for the following string

NewRelic INFO: Agent fully connected

If you find a line with that string in it, you know your agent is connecting to the New Relic servers just fine. If you don’t see that line, look for any possible error messages in the file. It’s likely you have either network connectivity issues or a syntax error in a configuration file. Get those worked out before you move on. If you have a connectivity or configuration error and can’t figure out how to resolve it, let us know here in the Explorers Hub, or reach out to New Relic support.

4. Where is the agent sending my data

Now that we know the agent is connecting to New Relic, let’s check to make sure it’s sending the data it collects to the place you’re expecting to see it. Search the agent log again, this time for the string

NewRelic INFO: Reporting to:

If you find this line, you’ll quickly notice that it also contains the URL where your application’s data will show in the New Relic UI. Make note of this URL.

Now, search one more time for the string:

NewRelic INFO: Your New Relic Application Name(s):

The info in that line represents the name or names the agent is reporting its data to (if there are multiple names, they’ll be separated by a colon :). This name will directly correlate to the URL you found in the last step. If there are multiple names on that line, the URL will correspond to the first name in the list. Make note of this name.

Lastly, visit the URL that you found in the logs and compare the name of the application (in the upper left-hand corner of the UI) to the name you got from the log file and see if they match.

With all that info in hand, you should find yourself in one of the following situations:

  1. The agent is reporting to the wrong New Relic account. - Make sure your agent is configured to use the right license key.

  2. The application name in the log matches the name of the application in the UI, but it’s not the place/name the agent is expected to report to. - Make sure you’ve configured the application name so that the agent reports its data to the expected place.

  3. The name of the application in the UI is different than the name the agent is reporting in the logs. - You most likely have a display alias set in the UI for your application.

  4. The agent is reporting to the right place, but you don’t see any data in the UI - This means one of two things; either there’s no traffic for the agent to report (generate some traffic to check this), or the application needs custom instrumentation. Most console/service applications will require custom instrumentation.

  5. Everything looks good, I’m fine - Awesome! Go outside and enjoy the day.

Happy monitoring!

13 Likes