// // ============LICENSE_START======================================================= // Copyright (C) 2016-2018 Ericsson. All rights reserved. // ================================================================================ // This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE // Full license text at https://creativecommons.org/licenses/by/4.0/legalcode // // SPDX-License-Identifier: CC-BY-4.0 // ============LICENSE_END========================================================= // // @author Sven van der Meer (sven.van.der.meer@ericsson.com) // == Example Configuration for Logging Logic The following example shows a configuration that logs policy logic to standard out (__info__) and a file (__debug__) All other APEX components are logging to a file (__debug__) and standard out (__error__). This configuration an be used in a pre-production phase with the APEX engine still running in a separate terminal to monitor policy execution. This logback configuration is in the APEX installation as `etc/logback-logic.xml` [source%nowrap,xml] ---- Apex %d %contextName [%t] %level %logger{36} - %msg%n ${VAR_LOG}/apex.log %d %-5relative [procId=${processId}] [%thread] %-5level%logger{26} - %msg %n %ex{full} policy: %msg\n ----