Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Navigation [hide]
[expand]
- Architecture
- DotNET Client API
- Client class
- Inheritance and interfaces
- Indexing
- Getting documents
- Deleting documents
- File attachments
- Searching
- Auto Boosting
- Best Bets
- Sorting
- Boosting with filters
- Boosting with weights
- Facets
- Filtering
- Strings
- Numerical
- DateTime
- Boolean
- Enum
- Filter and FilterHits
- Complex objects
- Custom filtering methods
- Free text search
- Geo Search
- Highlighting
- Including documents matching a filter
- More Like/Related
- Multiple searches in one request
- Searching over multiple types
- Pagination
- Languages
- Projections
- Related Queries
- Synonyms
- Unified search
- Caching
- Nested queries
- Connectors
- Customizing serialization
- Integration
- Episerver Commerce-Find integration
- Episerver 7.5+
- Access rights
- Customized search block styling guide
- Filters
- GetContentResult and GetFilesResult
- Indexing content in a content area
- Indexing
- Logging
- Querying examples
- Related content and dependencies
- Scheduled job for indexing
- Episerver 7/7.5 CMS
- Access rights
- Filters
- GetContentResult and GetFilesResult
- Indexing content in a content area
- Indexing
- Logging
- Querying examples
- Related content and dependencies
- Scheduled job for indexing
- Episerver CMS 6 R2
- Access rights CMS 6 R2
- GetPagesResult and GetFilesResult
- Indexing CMS 6 R2
- Logging CMS 6 R2
- Querying examples CMS 6 R2
- Related pages and dependencies
- Scheduled job for indexing CMS 6 R2
- Shell module
- Search statistics
Area:
Optimizely Search & Navigation
ARCHIVED This content is retired and no longer maintained. See the latest version here.
Logging
To investigate and resolve issues it is always good to turn on logging for your application. This topic describes logging for an integration of Episerver Find with Episerver 7/7.5 CMS.
How it works
The Logging API shipped with Episerver is an abstraction for writing log messages from the system, and the API is used internally by the Episerver assemblies for all logging.
When creating new CMS sites using the Visual Studio integration, the package EPiServer.Logging.Log4Net is installed by default, which is the log4net implementation of the API. Episerver Find also uses the log4net framework.
Activating logging
To activate logging, add an appender and a logger in the EPiServerLog.config, located by default in the web root of your Episerver application, for the EPiServer.Find namespace.
XML
<appender name="FindRollingLogFileAppender" type="log4net.Appender.RollingFileAppender">
<file value="find.log" />
<appendToFile value="true" />
<datePattern value=".yyyyMMdd.'log'" />
<rollingStyle value="Date" />
<filter type="log4net.Filter.LevelRangeFilter">
<acceptOnMatch value="true" />
<levelMin value="INFO" />
<levelMax value="FATAL" />
</filter>
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date %level [%thread] %type.%method - %message%n" />
</layout>
</appender>
<logger name="EPiServer.Find">
<appender-ref ref="FindRollingLogFileAppender" />
</logger>If your application does not have an EPiServerLog.config, then create one in the web root folder of your application and add the logger and appender there.
XML
<?xml version="1.0" encoding="utf-8"?>
<log4net>
<appender name="FindRollingLogFileAppender" type="log4net.Appender.RollingFileAppender">
<file value="find.log" />
<appendToFile value="true" />
<datePattern value=".yyyyMMdd.'log'" />
<rollingStyle value="Date" />
<filter type="log4net.Filter.LevelRangeFilter">
<acceptOnMatch value="true" />
<levelMin value="INFO" />
<levelMax value="FATAL" />
</filter>
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date %level [%thread] %type.%method - %message%n" />
</layout>
</appender>
<logger name="EPiServer.Find">
<appender-ref ref="FindRollingLogFileAppender" />
</logger>
</log4net>Related topic
Last updated: Nov 16, 2015
