Fixed several issues
They are:
an invalid category breaking the agent
Error logging not giving sufficient information in some cases
added an integration test script for the onaap side
Change-Id: I0580b52ceed5dd3aa5c5a800ebdb2cf9f24b8050
Signed-off-by: William Kurkian <wkurkian@cisco.com>
diff --git a/src/main/java/controller/Application.java b/src/main/java/controller/Application.java
index 23566dd..ce6ef9d 100644
--- a/src/main/java/controller/Application.java
+++ b/src/main/java/controller/Application.java
@@ -60,6 +60,7 @@
consumer.runConsumer();
} catch (Exception e) {
logger.error("Error in Kafka Alarm thread", e);
+ logger.error(e.toString());
}
}
@@ -74,7 +75,8 @@
VolthaKafkaConsumer consumer = new VolthaKafkaConsumer(KafkaConsumerType.KPIS);
consumer.runConsumer();
} catch (Exception e) {
- logger.error("Error Kafka, KPI thread", e);
+ logger.error("Error in Kafka KPI thread", e);
+ logger.error(e.toString());
}
}
diff --git a/src/main/java/ves/VesAgent.java b/src/main/java/ves/VesAgent.java
index ac42115..7b6be8e 100644
--- a/src/main/java/ves/VesAgent.java
+++ b/src/main/java/ves/VesAgent.java
@@ -102,7 +102,7 @@
String resourceId = message.getResourceId();
EVEL_SEVERITIES vesSeverity = mapSeverity(severity);
- EVEL_SOURCE_TYPES vesType = mapType(type);
+ EVEL_SOURCE_TYPES vesType = getSourceType();
EvelFault flt = new EvelFault(
"Fault_VOLTHA_" + eventType,
ldeviceId + ":" + ts,
@@ -116,6 +116,7 @@
flt.evel_fault_addl_info_add("state", state);
flt.evel_fault_addl_info_add("co_id", Config.getCoId());
flt.evel_fault_addl_info_add("pod_id", Config.getPodId());
+ flt.evel_fault_addl_info_add("type", type);
flt.evel_fault_addl_info_add("resourceId", resourceId);
flt.evel_fault_category_set(category);
@@ -153,7 +154,7 @@
}
}
- private static EVEL_SOURCE_TYPES mapType(String type) {
- return EVEL_SOURCE_TYPES.valueOf("EVEL_SOURCE_" + type.toUpperCase());
+ private static EVEL_SOURCE_TYPES getSourceType() {
+ return EVEL_SOURCE_TYPES.valueOf("EVEL_SOURCE_OLT");
}
}