From 1036206455218a4722079b749e628ca96825418d Mon Sep 17 00:00:00 2001 From: "a.sreekumar" Date: Wed, 28 Jul 2021 17:21:35 +0100 Subject: Improve APEX logging for irrelevant events When multiple policies are expecting event on the same topic/endpoint, a lot of event parsing failure log messages are generated unnecessarily. With this change, only a 1 line message will be printed if an event cannot be parsed, and the detailed messages will be available at debug level. Change-Id: If1e7460ef5ed86fd470396f1e2ed8cc3c8af70c4 Issue-ID: POLICY-3499 Signed-off-by: a.sreekumar --- .../onap/policy/apex/service/engine/main/ApexEventUnmarshaller.java | 3 +++ 1 file changed, 3 insertions(+) (limited to 'services/services-engine/src/main/java') diff --git a/services/services-engine/src/main/java/org/onap/policy/apex/service/engine/main/ApexEventUnmarshaller.java b/services/services-engine/src/main/java/org/onap/policy/apex/service/engine/main/ApexEventUnmarshaller.java index f49115b38..4e62f5c0f 100644 --- a/services/services-engine/src/main/java/org/onap/policy/apex/service/engine/main/ApexEventUnmarshaller.java +++ b/services/services-engine/src/main/java/org/onap/policy/apex/service/engine/main/ApexEventUnmarshaller.java @@ -264,6 +264,9 @@ public class ApexEventUnmarshaller implements ApexEventReceiver, Runnable { } catch (ApexException e) { if (!iterator.hasNext()) { final String errorMessage = "Error while converting event into an ApexEvent for " + name; + if (!LOGGER.isDebugEnabled()) { + LOGGER.warn("{}. Detailed logs are available at debug level.", errorMessage); + } throw new ApexEventException(errorMessage, e); } } -- cgit 1.2.3-korg