I used to create my own logging mechanisms for my Windows Azure Cloud Services. For a while this was the perfect solution to my requirements. But It had a down side, it required cleanup routines and a bit of maintenance.
In the recent months I changed my mind about Windows Azure Diagnostics and if you’re not too adventurous and don’t need your logs available every 30 seconds, I strongly recommend using them. They’ve come such a long way since the first versions that I’m now willing to wait the full minute for my application logs to get persisted to table storage.
The issues I had with Windows Azure Diagnostics were because of my ignorance and half because of irritating issues that used to exist.
- I didn’t know how to efficiently read from Windows Azure Diagnostics
- Changing Windows Azure Diagnostics configurations used to mean a new release (code changes and deployment)