Don't miss out Virtual Happy Hour this Friday (April 26).

Try our conversational search powered by Generative AI!

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

Logging

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.

Optimizely comes with a logging API, which is an abstraction for writing log messages from the system. Logging is useful when you troubleshoot and locate application problems.

The logging API

Optimizely Commerce uses EPiServer.Logging, which 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.

The recommendation for custom logging in Optimizely is to use the logging API defined in .NET Core.

Related topic

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

Last updated: Jul 02, 2021

Recommended reading