Patch Publishing Logging Level

Following up on yesterday’s post, you can patch your logging to increase the level of logging in Sitecore:

<log4net>
<logger name="Sitecore.Diagnostics.Publishing">
<level>
<x:attribute name="value">DEBUG</x:attribute>
</level>
</logger>
</log4net>

Could be useful in diagnosing publishing problems.

Advertisements
Patch Publishing Logging Level

Publish to ‘web’|#Exception: System.Reflection.TargetInvocationException

Issue: after updating a UAT server I was getting the following error in the “item:deleted” event after trying to publish anything… Continue reading “Publish to ‘web’|#Exception: System.Reflection.TargetInvocationException”

Publish to ‘web’|#Exception: System.Reflection.TargetInvocationException

Hooking into Sitecore’s Logging

Sitecore uses Log4Net for it’s logging framework, so it comes with a whole slew of different ‘appenders’, suitable for logging to various repositories. That’s nice, but what if there’s a target you want to use that doesn’t exist?

Well, you can override the SitecoreLogFileAppender and write your own output:

What else could you do with this? Well, writing to App Insights seems like a good bet.

Hooking into Sitecore’s Logging

Minifying JS – Skip removing line numbers?

I’m a big fan of App Insights, and I’m loving it’s increasing integration with Visual Studio. To me, it’s just great.

However, I did find myself laughing a bit at this. App Insights was recording JavaScript errors from a (third party’s) .JS file.

appinsights

This is showing an error on Line 93. The thing is, the file has been minified – and all the code in the file is on line 93.

Hmm. All this would save is a couple of hundred bytes over the wire. I’m just not sure it’s worth it for most of the projects I work on. I think having the new-lines still in (albeit otherwise minified).

To be honest, we’d save more space by stripping out the 92 lines of Licensing information above the code. I’m not sure that that shouldn’t reside in a text file, and just have a comment referencing the licence information.

Minifying JS – Skip removing line numbers?

App Insights Visual Studio Integration is Fantastic

So, I do love App Insights, but I just realised that it’s even better than I’d thought. They’ve integrated it more closely with Visual Studio.

In the code you can see things at the top of each method – how many references it has, who last edited it, how long ago it was edited,, etc.

Well now you can also see the exceptions that were recorded by App Insights for that method in the last 24 hours:

appinsights-in-visual-studio

Fantastic!

(And all those are expected exceptions. If anyone works out a way of doing a Response.Redirect() without a ThreadAbortException and still killing the page processing, let me know)

App Insights Visual Studio Integration is Fantastic

Make Sitecore record the class writing to the logs

I’m a big fan of writing into your logs the class and method that is currently executing – it makes fault finding so much easier. Typically I’d do this with reflection – but it turns out that you can do this with a small change to Sitecore’s configurationContinue reading “Make Sitecore record the class writing to the logs”

Make Sitecore record the class writing to the logs