How to track logs and analytics by release

Tracking changes in analytics and logs between versions/releases can be very informative.  Code changes may affect how many people leave a page or form mid-way, or exceptions may suddenly sky rocket.  When you’re releasing multiple times a day, figuring out what exceptions or analytics pertain to which release can get a little tricky/time-consuming.  Enter buildinfo.config.

Documentation for this can be found here.

Configuration

Configuration for this is easy.  Simply unload your project and edit the .csproj (or .vbproj, if that’s your thing) file and add this:

 <PropertyGroup>
     <GenerateBuildInfoConfigFile>true</GenerateBuildInfoConfigFile> 
     <IncludeServerNameInBuildInfo>true</IncludeServerNameInBuildInfo>
 </PropertyGroup>

Once this is added, you’ll see .buildinfo.config dumped out into your bin directory on build.

Creating a buildinfo.config only on Release builds

Some teams may only care to create a buildinfo.config file on Release builds as lower environment logging isn’t as important.  In that event, the updated script would look like this:

 <PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release|AnyCPU'">
     <GenerateBuildInfoConfigFile>true</GenerateBuildInfoConfigFile> 
     <IncludeServerNameInBuildInfo>true</IncludeServerNameInBuildInfo>
 </PropertyGroup>

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a website or blog at WordPress.com

Up ↑

%d bloggers like this: