Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

Area: Optimizely CMS
Applies to versions: 12 and higher
Other versions:
ARCHIVED This content is retired and no longer maintained. See the version selector for other versions of this topic.


Recommended reading 
Note: This documentation is for the preview version of the upcoming release of CMS 12/Commerce 14/Search & Navigation 14. Features included here might not be complete, and might be changed before becoming available in the public release. This documentation is provided for evaluation purposes only.

The Logging API shipped with Optimizely (EPiServer.Logging namespace) is an abstraction for writing log messages from the system. It merely works as a façade for the logging framework in .NET Core (Microsoft.Extensions.Logging). To manage the configuration and output of the logger, refer to the API of the implementing framework, see Logging in .NET Core.

You should use the logging API defined in .NET Core. Optimizely CMS uses the same API, so CMS and custom logs are written to the same configured output.

Backwards compatibility

If you upgrade an existing project that uses the API defined in EPiServer.Logging, that will still work because it acts as a façade over the API defined in Microsoft.Extensions.Logging . However, for new projects, you should log directly using the Microsoft.Extensions.Logging API.

Do you find this information helpful? Please log in to provide feedback.

Last updated: Jul 02, 2021

Recommended reading