Hot answers tagged

19

This looks like it's part of the Device Detection feature within the Sitecore.CES configuration. It's fair that you would want device detection yet not have the GeoIP feature of it enabled. Have you tried renaming the following two configuration files to disable them and see if that works? App_Config/Include/CES/Sitecore.CES.GeoIp.config App_Config/...


16

Ensure that the following setting in the Sitecore.Analytics.config file is set to false <setting name="Analytics.PerformLookup" value="false" />


16

Accessing Sitecore XP logs and diagnostics information on Azure Web Apps differs from the on-premise approach. This article explains how to collect basic Sitecore diagnostics information, such as logs and configuration data, for a Sitecore XP solution deployed to Azure Web Apps. To access enhanced logging data of a Sitecore XP instance deployed to Azure Web ...


15

You can use a RollingFileAppender instead of the default Sitecore one and configure it to roll by date. You can find samples in the log4net config examples section of the documentation. Specifically with Sitecore, change the appender(s) to the following: <appender name="LogFileAppender" type="log4net.Appender.RollingFileAppender, Sitecore.Logging"> ...


15

The underlying logging framework that Sitecore uses is Apache Log4Net, and this has not changed for a very long time (since early 6.x). Even the version used is the same, 1.2.11 I believe. The pattern used for logging messages is also exactly the same between the versions: <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%...


12

In log4net you can use a filter on the level in your appender like this: <threshold value="DEBUG"/> <filter type="log4net.Filter.LevelRangeFilter"> <levelMin value="DEBUG" /> <levelMax value="INFO" /> </filter> Not sure whether the syntax in Sitecore will be the same as I didn't test it. The threshold value specifies that ...


11

The DefaultScavengeStrategy is responsible for scavenging (freeing up) memory from your caches when your application is maxing out on its memory resources, as determined by the configured cache size limits. The warning that you are seeing indicates that memory usage was maxing out for the specified cache, based on your configured maximum cache sizes, and so ...


10

So for Sitecore - a global error handler in the global.asax will not work properly. The better way to do it is to override the code that calls each rendering and handle the errors there. ExecuteRenderer With a simple override of ExecuteRenderer we can easily catch all exceptions: public class ExecuteRenderer : Sitecore.Mvc.Pipelines.Response....


10

One thing to be aware of, is that in Sitecore's Site Provider, order of sites is incredibly important. If for some reason, your order has become unordered.. and the scheduler site shows up in the list BEFORE other site definitions, then Sitecore will land on the scheduler site as the Site for the current Context. Sitecore's Site Provider processes sites ...


10

How it works Have a look at the App_Config/Sitecore/Azure/Sitecore.Cloud.ApplicationInsights.config which gets deployed to all CM/CD/PRC/REP roles. You will see that all the built-in log4net appenders get patched to append via the Application Insights LevelTraceAppender. You may also notice that sitecore still logs to the file system on Azure PaaS, which ...


9

Actually, recommended practice would be to use a Namespace as your logger, as opposed to new object() or anything else. Just using "YourLoggerName" would not be flexible enough to allow admins to fine tune log handling inside your module. As you rightly point out, this will not work in a static class. But this will: Sitecore.Diagnostics.Log.Error("Message"...


9

It's not the problem with the Log.Warn being called in a httpRequestBegin processor or from a normal page. It's just your browser caching the redirect. First time you do a call to a page which should be redirected, you will see the log entry starting from: Map 301 redirected... in your log files. Second time you do the same request in your browser, it ...


8

Configuring a dedicated Content Management server Normally, pure CM servers should not read and write interactions and contacts in the collection database. See this official documentation page for more information: Configure a content management server The easiest fix for you would be to disable the Sitecore.Analytics.Tracking.Database.config. In any case,...


8

Yes. You need a new <appender>. First you need to set up a table to receive the logging information: CREATE TABLE [dbo].[Log] ( [Id] [int] IDENTITY (1, 1) NOT NULL, [Date] [datetime] NOT NULL, [Thread] [varchar] (255) NOT NULL, [Level] [varchar] (50) NOT NULL, [Logger] [varchar] (255) NOT NULL, [Message] [varchar] (4000) NOT ...


8

I think this URL speaks to your issue: https://kb.sitecore.net/articles/404548 Among the other suggestions there, try to reload the perf counters: Start an administrator command prompt. Run unlodctr .NETFramework. Run lodctr %WINDIR%\Microsoft.NET\Framework\\CORPerfMonSymbols.ini where is the directory of the .NET Framework version which contains the ...


8

When working with the Global.asax file, even though the question is inheriting from Sitecore.ContentSearch.SolrProvider.NinjectIntegration.NinjectApplication, if you keep digging down, eventually you'll find that also inherits from the HttpApplication class. Ordinarily, this class exists in the System.Web namespace. However, when choosing protected as your ...


8

If you do not want to disable cache size limits (which in our situation can cause memory issues when building large indexes on Azure WebApps), you can use the following Sitecore setting to change the "web[isLanguageFallbackValid]" and "master[isLanguageFallbackValid]" sizes: <sitecore> <settings> <setting name="Caching.SmallCacheSize" ...


7

Sounds like you need Sitecore Sidekick Audit Logger - its a package you can install and provides much more detailed audit logging than the standard log files. You can search the log: Search by item: and in the results you can see the details of the changes: Should give you most of what you need. EDIT: Installation Instructions Added The easiest way to ...


7

Two possible problems that could cause this i can think of: You are referencing log4net.dll instead of Sitecore.Logging.dll, You need to reference Sitecore.Logging.dll in your project for Sitecore custom logger to work You custom log4net configurations lives outside <sitecore> node, Make sure it is located within that node: ...


6

With this solution, it will create a new log file call audit.{date}.log and log any change the users make to the content. To achieve this, the pipeline subscribes the audit class to the item:creating, saving, deleting, copying, moving, renamed, sortorderchanged, templatechanged and itemProcessed events. Each time one of these events is triggered, a new log ...


6

First, start by adding multiple appender to your app.config: <appender name="site1" type="log4net.Appender.RollingFileAppender"> <file value="site1.txt" /> <appendToFile value="true" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%date %message%newline" /> ...


5

As Sitecore logging is just a wrapper on top of log4net, you should create an appender (and maybe logger) in your code (assuming that the "processor" you mention is some custom code). I found this solution on stackoverflow, but didn't test it myself. It is using the log4net api to create a FileAppender and set its properties. After creating the appender, you ...


5

I don't think that it make any difference which Sitecore version you are using. It just analyze logs (which are simply .txt files). I am constantly using it on 8.1 and 8.2. No problems found. I suppose authors forgot to update Requirements section.


5

First of all, you should disable List Manager on the processing server. The search messages in logs are likely caused by the Sitecore.ListManagement.Analytics.UnlockContactListsAgent class. It looks for locked contact lists every 10 seconds (configured in the Sitecore.ListManagement.config file) and tries to unlock them as soon as the real (indexed) ...


5

Sitecore logging system is wrapper under log4net. It is even configured not under <sitecore> node in web.config. To use Sitecore log files you should have 3 things: Configured <log4net> section in web.config file. (If your service layer is hosted from same folder as Sitecore then nothing should be changed. Otherwise you can copy log4net section ...


5

Sitecore supports client-side event logging using JSNLog. Sitecore client logging uses JSNLog which has been wrapped to allow Sitecore to configure it via a patch and to make use of the existing Log4net logging. There is an OOTB configuration file called Sitecore.JSNLog.config on app_config/include/Sitecore. To enable client-side logging you need to add ...


4

There is a very good article on https://community.sitecore.net/developers/f/8/t/531 which deals with the same issue. I actually followed it up last year and it solved the issue that you are having as well.


4

You can start by creating a table for logging, Preferably in your own separate Database, Then you can update your Log4Net configurations to use the SQL appender, Alex Shyba article shows how you can do that, Basically you will need the following: Create Your own Table for logging inside your own Database, Let say SitecoreSystem CREATE TABLE [dbo].[Log] ( ...


4

You cannot. When Sitecore executes any job, it runs <job> pipeline defined in Sitecore.config (or web.config in older versions). This pipeline has SignalStart and SignalEnd processors, but the only thing they do is logging the information that job started or finished: public static void SignalStart(JobArgs args) { Job job = args.Job; job.Status....


4

You are correct in that you can patch in log4net settings in recent Sitecore releases. But your patch file is unrelated to your error, as Zach already pointed out. My guess; given that the missing config lies right above log4net - you removed this by mistake earlier. Sitecore.config needs to look like this. <watchers> <media> <...


Only top voted, non community-wiki answers of a minimum length are eligible