Skip to main content

Online Windows Azure Diagnostics


Azure Diagnostics is extremely powerful when setup correctly and being fully utilised. That said, quite a bit of burden is still left with us developers to pull out the juicy bits and present that as information that can potentially be consumed and mean something to the other, often not quite so technical, stake holders. Maybe more importantly from a developer standpoint is being able to fault find a collection of services when something does go wrong or is about to go wrong. 

A useful tool which I have used with Windows Azure and comes in very handy for diagnosing and monitoring is Stackify. It is online which immediately gets a thumbs up from me but the good part is that it supports all the Azure Diagnostics in near to real time.

You can see below that it is showing some useful stats from some Web and Worker roles. 



There are a number of different views that can be selected such as the one shown below.






Going beyond the stats which are absolutely invaluable when trouble shooting problems, there are a whole host of other features and views which make this rather like a Swiss army dev ops tool as show below.

Process List





Schedule Jobs





Start and stop Services






Browse and download Files and Folders





Like me, you have probably written some similar features into your own set of utilities in the past. 
There are other features as well which are worth checking out.  


The Setup

Setup is very straight forward.
  • Create an account with Stackify, login and download the zip archive for Azure (see fig 1 above) 
  • Extract the files to your Web or Worker Role project
  •  Set 'Always Copy to Output Directory' to ensure they get deployed from properties
  • Set the Build action to 'None' from properties
  • Add a startup task to your ServiceDefinition.csdef as shown below:


<Startup>
 <Task commandLine="Install.cmd" executionContext="elevated" taskType="background">
  <Environment>   <Variable name="ACTIVATIONKEY" value="<Replace with your Activation Key>" />
  </Environment>
 </Task>
</Startup>


  • Replace the value for the 'ACTIVATIONKEY' with your new activation key obtained from creating your new Stackify account.

This can be seen below from my project:



Now go ahead and perform a deployment as usual.

As soon as your services have been deployed and started, you will be able to see an item for each instance inside Stackify and drill down into the features. Now you can check the current status of a deployment and perform some pretty cool stuff just with your IPad. Not Bad...

One thing to note is that some of the other features focus on developer productivity! Your project manager will love it!!! :)

Checkout some other musings via my blazor.net and azure blog here carlrandall.net

Popular posts from this blog

Azure Devops - Pull Request Merge Conflicts

Before a Git pull request can complete, any conflicts with the target branch must be resolved. Out of the box, at the time of writing this article, Azure DevOps requires this to be resolved locally. Following best practices to not allow direct commits to our release/master branches further exasperates the problem as we need to effectively clone the branch or go with a rebase approach, both of which break the natural flow of resolving the conflicts as part of the pull request. With this extension, from the Microsoft DevLabs team via the Marketplace, you can resolve these conflicts online, as part of the pull request process, instead of being forced to break flow and resolve locally. Online Experience After adding the extension the new conflicts tab is visible which enables conflict resolution in the familiar side by side review page as shown below: Really nice extension, which should make resolving merge conflicts a much more straightforward part of the DevOps

Adding mobile support for MVC4 Web Applications

A few years ago, mobile web sites were more of an after-thought for many developers unless you were involved in developing apps specifically targeted for mobile devices. I was surprised to read on wiki that it was only March 2010 when Apple began taking pre-orders for the iPad. What a different landscape we have seen since. Desktops, Tablet and Mobile support are now a major design goal for any site that needs a broad reach and this is only set to increase.   This article will demonstrate how MVC4 , almost out of the box allows us to deliver views that cater for specific mobile devices and keep the code base shared as much as possible, creating mobile friendly web applications. Read complete article... Also checkout some other musings via my blazor.net and azure blog here  carlrandall.net

Azure DevOps Authorisation

Managing whether an identity has access to a given  service, feature, function, object, or method in Azure DevOps comes down to authorisation. Fortunately, by default, the DevOps permissions are set in such a way to enable you to focus on the job at hand, DevOps. Loosely translated this means 'don't get in my way'. My experience is that the Azure DevOps team have done a good job at this, enabling you to crack on developing, building, testing and releasing without much hindrance. Working with relaxed permissions is great when you are the owner and possibly either a one man band or small team but as soon as we need to consider larger teams, varying roles with approvals and degrees of access, authorisation becomes a real concern. I was recently involved in a project utilising offshore developers where trust was a concern and a number of specific teams handling specific roles needed to come together to approve a set of pipelines.  This article is a pick of findings a