Dotnet Web API NewRelic Integration

-

Today I was having a bit more of a play with integrating NewRelic with a dotnet web API, and figured I’d document my findings. It’s worth taking a look at the NewRelic docs if you haven’t seen them already.

It’s worth noting I’d put a quick post together about this last year, but that approach was entirely in Docker, whereas today’s approach is a bit more polished and uses the NewRelic nuget packages.

Nuget

Add the NewRelic nuget packages to your API:

<PackageReference Include="NewRelic.Agent" Version="8.25.214"  />
<PackageReference Include="NewRelic.Agent.Api" Version="8.25.214"  />

newrelic.config

This has mostly been taken from docs.newrelic.com. You can ignore additional exceptions and http status codes here.

I’ve taken the license key out of here, and instead set those in environment variables below, as this config will be committed to source control.

<?xml version="1.0"?>
<!-- Copyright (c) 2008-2019 New Relic, Inc.  All rights reserved. -->
<!-- For more information see: https://newrelic.com/docs/dotnet/dotnet-agent-configuration -->
<configuration xmlns="urn:newrelic-config" agentEnabled="true">
    <log level="info"/>
    <transactionTracer enabled="true" transactionThreshold="apdex_f" stackTraceThreshold="500" recordSql="obfuscated" explainEnabled="false" explainThreshold="500"/>
    <crossApplicationTracer enabled="true"/>
    <errorCollector enabled="true">
        <ignoreErrors>
            <exception>System.IO.FileNotFoundException</exception>
            <exception>System.Threading.ThreadAbortException</exception>
        </ignoreErrors>
        <ignoreStatusCodes>
            <code>401</code>
            <code>404</code>
        </ignoreStatusCodes>
    </errorCollector>
    <browserMonitoring autoInstrument="true" />
    <attributes enabled="true">
    </attributes>
    <threadProfiling>
      <ignoreMethod>System.Threading.WaitHandle:InternalWaitOne</ignoreMethod>
      <ignoreMethod>System.Threading.WaitHandle:WaitAny</ignoreMethod>
    </threadProfiling>
</configuration>

Environment Variables

Set environment variables for the NewRelic runner. You can do this straight in the Dockerfile, but being as we’re including a license key here, it’s probably best to store these values somewhere more secure. I went with our locked down kubernetes manifest.

- name: "CORECLR_ENABLE_PROFILING"  
  value: "1"  
- name: "CORECLR_PROFILER"  
  value: "{36032161-FFC0-4B61-B559-F6C5D41BAE5A}"
- name: "CORECLR_NEWRELIC_HOME"  
  value: "/app/newrelic"    
- name: "CORECLR_PROFILER_PATH"  
  value: "/app/newrelic/libNewRelicProfiler.so"  
- name: "NEW_RELIC_LICENSE_KEY"  
  value: "{YOUR KEY HERE}"  
- name: "NEW_RELIC_APP_NAME"  
  value: "{YOUR API NAME HERE}"

Worth noting I got these variables from here and here.

Dockerfile

Copy the newrelic.config file into your final docker image

FROM mcr.microsoft.com/dotnet/core/sdk:3.1-alpine3.11 AS build
   WORKDIR /src
   ...
   # this is here just for context
   RUN dotnet build -c Release --no-restore
   RUN dotnet publish ./Your.Api/Your.Api.csproj -c Release -o  /app/publish --no-restore --no-build

FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-alpine3.11 AS final
   WORKDIR /app
   ...
   # this is the line you need to include!
   COPY ./newrelic.config .
   COPY --from=build /app/publish .
   ...

Ignore Requests In Code

If you need to ignore certain requests, such as calls to your /status endpoint that are perhaps being made by monitoring software, you can just add this to your controller method:

[HttpGet]
public StatusCodeResult Get()
{
   NewRelic.Api.Agent.NewRelic.IgnoreTransaction();
   return Ok();
}

Popular posts from this blog

Taking a memory dump of a w3wp process

-
Taking a memory dump of a w3wp process Taking a memory dump of an IIS worker process in a live system can be problematic, as IIS will kill the process if it has been suspended for more than 60 seconds. Only use these steps if your application is on a high availability cluster, else you’ll take your app down! copy sysinternals procdump.exe and pssuspend.exe to target machine create powershell file with: $iispid = Get-Process svchost | ? { $_ . modules . ModuleName -eq "iisw3adm.dll" } | Select - First 1 - ExpandProperty Id $workerpid = Get-Process w3wp | Sort ws - Descending | Select - First 1 - ExpandProperty Id & ".\pssuspend.exe" $iispid Write-Output "Creating memory dump for w3wp PID $workerpid " & ".\procdump.exe" - ma $workerpid & ".\pssuspend.exe" $iispid - r (taken from stackoverflow ) 3) check the w3wp process has reached the high level of RAM usage that you’re intending to
Read more

GitLab Badges

-
Image
GitLab has built in functionality to allow you to add badges, to provide an at-a-glance status of your app's quality.  In order to set project badges up, you need to be a maintainer of the project so that you can access the settings. Pipeline Status This shows whether your master branch pipeline has passed or failed.  The badge is super easy to set up.  In GitLab go to Settings > General > Badges > Add Badge, and enter this: Name:  Pipeline Link:  https://gitlab.com/%{project_path}/commits/%{default_branch} Badge: https://gitlab.com/%{project_path}/badges/%{default_branch}/pipeline.svg These links should be right for any project, as they're using variables. Coverage % Code coverage is a little more involved, as it relies on you having already configured code coverage in your app.  For the app I've been working on, which is a dotnet application, I opted to use the opensource MiniCover .  This is configured to writes a code coverage report to the
Read more

sp_blitzIndex

-
Some more notes after watching Brent’s How I Use the First Responder Kit: sp BlitzIndex . This sproc will analyse every index across all databases in your sql server and return a prioritised list of potential issues. EXEC sp_blitzIndex @GetAllDatabases = 1 The MoreInfo column is interesting. If you copy the SQL out and run it, it will give you more information on the indexing issue in question. E.g: EXEC dbo . sp_BlitzIndex @DatabaseName = 'YourDatabase' , @SchemaName = 'dbo' , @TableName = 'tFoo' ; If you run this, the top result set it a list of indexes that are on the target table. It shows how many seeks and scans each index has had, the size of the index, etc. Note the URL column for more information on each issue category. Missing indexes are shown in the 2nd result set. The 3rd result set shows the table definition, which is nice to have without having to mess with the SSMS UI.
Read more