Skip to main content

Logger with UmbracoLog

Umbraco logger is powerful tool and It can be extended to use in your Umbraco application to log anything that you want to do, instead of using another logger to do the task.
     /// <summary>  
     /// Logger to log Error/Debug/Warning to Umbraco log table  
     /// </summary>  
     public class Logger  
     {  
       public enum LogLevels  
       {  
         DEBUG = 1,  
         WARNING = 2,  
         ERROR = 3,  
         NONE = 100  
       }  
       public static LogLevels CurrentLevel  
       {  
         get;  
         set;  
       }  
       private static string StrLoggedInUserId;  
       public static void SetStrLoggedInUserId()  
       {  
         if (StrLoggedInUserId == null || StrLoggedInUserId == "NA")  
         {  
           if (HttpContext.Current != null)  
           {  
             HttpCookie cookie = HttpContext.Current.Request.Cookies[FormsAuthentication.FormsCookieName];  
             if (cookie != null)  
             {  
               FormsAuthenticationTicket ticket = FormsAuthentication.Decrypt(cookie.Value);  
               StrLoggedInUserId = ticket.Name;  
               return;  
             }  
           }  
           if (string.IsNullOrEmpty(StrLoggedInUserId))  
           {  
             StrLoggedInUserId = "NA";  
           }  
         }  
       }  
       private static string StrSessionId  
       {  
         get  
         {  
           return HttpContext.Current.Session != null ? HttpContext.Current.Session.SessionID : "NA";  
         }  
       }   
       public static void Debug(string message)  
       {  
         SetStrLoggedInUserId();  
         if ((int)CurrentLevel <= (int)LogLevels.DEBUG)  
         {  
           umbraco.BusinessLogic.Log.Add(umbraco.BusinessLogic.LogTypes.Debug, -1, StrLoggedInUserId + " : " + StrSessionId + " : " + message);  
         }  
       }  
       public static void Error(string message)  
       {  
         SetStrLoggedInUserId();  
         if ((int)CurrentLevel <= (int)LogLevels.ERROR)  
         {  
           umbraco.BusinessLogic.Log.Add(umbraco.BusinessLogic.LogTypes.Error, -1, StrLoggedInUserId + " : " + StrSessionId + " : " + message);  
         }  
       }  
       public static void Exception(Exception e)  
       {  
         SetStrLoggedInUserId();  
         if ((int)CurrentLevel <= (int)LogLevels.ERROR)  
         {  
           string logstring = e.Message;  
           logstring += Environment.NewLine;  
           logstring += e.StackTrace != null ? e.StackTrace : "";  
           logstring += Environment.NewLine;  
           logstring += e.InnerException != null ? e.InnerException.Message : "";  
           logstring += Environment.NewLine;  
           logstring += e.InnerException != null && e.InnerException.StackTrace != null ? e.InnerException.StackTrace : "";  
           umbraco.BusinessLogic.Log.Add(umbraco.BusinessLogic.LogTypes.Custom, -1, StrLoggedInUserId + " : " + StrSessionId + " : " + logstring);  
         }  
       }  
       public static void Login(string message)  
       {  
         SetStrLoggedInUserId();  
         if ((int)CurrentLevel <= (int)LogLevels.DEBUG)  
         {  
           umbraco.BusinessLogic.Log.Add(umbraco.BusinessLogic.LogTypes.Login, -1, StrLoggedInUserId + "~" + StrSessionId + "~" + message);  
         }  
       }  
       public static void ErrorLogin(string message)  
       {  
         SetStrLoggedInUserId();  
         if ((int)CurrentLevel <= (int)LogLevels.ERROR)  
         {  
           umbraco.BusinessLogic.Log.Add(umbraco.BusinessLogic.LogTypes.LoginFailure, -1, StrLoggedInUserId + "~" + StrSessionId + "~" + message);  
         }  
       }  
       public static void Logout(string message)  
       {  
         SetStrLoggedInUserId();  
         if ((int)CurrentLevel <= (int)LogLevels.DEBUG)  
         {  
           umbraco.BusinessLogic.Log.Add(umbraco.BusinessLogic.LogTypes.Logout, -1, StrLoggedInUserId + "~" + StrSessionId + "~" + message);  
         }  
       }  
     }  

Comments

Popular posts from this blog

DD4TFormRouteHandler (posting a form as tridion page url)

ASP.NET routing enables us to use URLs that are not physical files, In DD4T we have the default page route definition. In which all page request redirct to Page controller and process the page. DD4TFormRouteHandler is a custom route handler responsible for mapping incoming browser requests to particular MVC controller actions, this works along with  DD4TFormHelper  (that generate the route information for the form) Posting a form in DD4T is not complicated, you can create the mvc form as a normal controller and action, then post it via AJAX. But, when we need to do post the form as normal page, It would need a tweak as the controller/action is not a page existed in tridion. This can be achieved by implementing a custom Mvc RoutHandler and reroute the posted form to the encrypted action and controller. It works as below daigram. So, how to do this. to render out the form we have BeginDD4TForm html helper as below that generate the form with encrypted route values....

Navigation in DD4T

There always been a question on What is the best approach for building navigation with DD4T and ASP.NET MVC? Answer is: There is TridionSiteMapProvider as part of the DD4T.Mvc project, which can be used out of the box. The  DD4T.Examples.Templates project also have a example on how Sitemap can be generated from the template ( TBB ) Many organization will have different kinds of navigation structure, It can be from very simple structure or it can be a heavily complex in nature. In this article you can see how the default SitemapProvider can be used and how we could customize to achieve complex Navigations like Megamenu or similar using TridionSiteMapProvider. Setting up the default TridionSiteMapProvider The only configuration you would need to do in web.config is set the your default sitemap provider is as below. <system.web> <siteMap defaultProvider= "TridionSiteMapProvider" enabled= "true" > <providers> <clear/> ...

Understanding MCP Server: Model Context Protocol in AI Systems

Introduction In the rapidly evolving field of artificial intelligence, efficient communication between AI models and applications has become increasingly critical. The Model Context Protocol (MCP) and MCP Servers represent a significant advancement in how AI systems interact with data and services. This blog post breaks down what MCP Server is, how it works, and why it matters for modern AI applications. What is Model Context Protocol (MCP)? Model Context Protocol (MCP) is a standardized communication framework designed specifically for AI model interactions. It defines how AI models receive input data, process information, and return results in a consistent, structured manner. Think of MCP as the "language" that allows AI systems to effectively communicate with applications, databases, and other services. What is an MCP Server? An MCP Server acts as the central coordination point in an AI system architecture that implements the Model Context Protocol...