![]() The following is a list of log levels (priorities) from lowest to highest severity. By setting the log level appropriately on each server, you have the ability to capture the amount of logging needed. But on a production server, you might only be interested in errors. In this case, you would lower the log level so you get as much information from the system as possible. Log level is also called priority.įor example, on a testing server you may be looking for any opportunity to tune performance. This log level limits the messages that are written to the log. If you are not using FXM, this log will be empty.Įach log has a log level assigned to it. Fxm - Activity from Federated Experience Manager.Publishing - Activity from publishing performed by Sitecore servers. ![]() Crawling - Activity from crawling performed by Sitecore search providers.Search - Activity from searches performed using Sitecore search providers.If you are not using WebDAV, this log will be empty. Log - All-purpose, general Sitecore log.Standard Logsīy default Sitecore uses the following logs: Only Sitecore components can be configured using Sitecore patch files. Configuration settings for log4net are defined in Web.config under configuration/log4net.ĭo not put log4net settings in a Sitecore patch file. Sitecore uses Apache log4net for logging. Logging is an important way to ensure that the people responsible for maintaining a Sitecore system are able to identify and fix problems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |