Add controller logger configurations

Logger configurations have been added for each feature that
installs a controller. The convention that the controller
logging feature looks for in a controller logback config
file is "logback-include-.*.xml".

Issue-ID: POLICY-1427
Change-Id: Ic37686bf6c1063ba5162fdd494b7465c3a82da01
Signed-off-by: Daniel Cruz <dc443y@att.com>

1 files changed, 56 insertions, 0 deletions

diff --git a/controlloop/common/feature-controlloop-amsterdam/src/main/feature/config/logback-include-amsterdam.xml b/controlloop/common/feature-controlloop-amsterdam/src/main/feature/config/logback-include-amsterdam.xml
new file mode 100644
index 000000000..780fbdb3a
--- /dev/null
+++ b/controlloop/common/feature-controlloop-amsterdam/src/main/feature/config/logback-include-amsterdam.xml
@@ -0,0 +1,56 @@
+<!--
+  ============LICENSE_START=======================================================
+  feature-controlloop-amsterdam
+  ================================================================================
+  Copyright (C) 2019 AT&T Intellectual Property. All rights reserved.
+  ================================================================================
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+  
+       http://www.apache.org/licenses/LICENSE-2.0
+  
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+  ============LICENSE_END=========================================================
+  -->
+
+<!--
+  The logger configurations in this file are for each individual controller
+  to have their own network logger for topic traffic. This is an extension of
+  logback.xml or logback-eelf.xml.
+
+  NOTE: Each logger MUST contain the same name as the control loop's controller.  
+-->
+<included>
+
+    <property name="logDir" value="${POLICY_LOGS}" />
+    <property name="amsterdamLog" value="amsterdam-network" />
+    <property name="networkPattern" value="[%d{yyyy-MM-dd'T'HH:mm:ss.SSS+00:00, UTC}|%t]%m%n" />
+
+    <!-- Amsterdam Network Logging Properties -->
+    <appender name="AmsterdamOut" class="ch.qos.logback.core.rolling.RollingFileAppender">
+        <file>${logDir}/${amsterdamLog}.log</file>
+        <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
+            <fileNamePattern>${logDir}/${amsterdamLog}.%d{yyyy-MM-dd}.%i.log.zip</fileNamePattern>
+            <maxFileSize>50MB</maxFileSize>
+            <maxHistory>30</maxHistory>
+            <totalSizeCap>10GB</totalSizeCap>
+        </rollingPolicy>
+        <encoder>
+            <pattern>${networkPattern}</pattern>
+        </encoder>
+    </appender>
+
+    <appender name="AsyncAmsterdamOut" class="ch.qos.logback.classic.AsyncAppender">
+        <appender-ref ref="AmsterdamOut" />
+    </appender>
+
+    <logger name="amsterdam" level="INFO" additivity="false">
+        <appender-ref ref="AsyncAmsterdamOut" />
+    </logger>
+
+</included>
\ No newline at end of file