Better exception handling in the analyzer
Give the ability to continue creating a PEL with FFDC if there is an
exception in the analysis portion of the analyzer.
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I2de281a7c974cfc80779a861a12cb2b9c99e0491
diff --git a/analyzer/service_data.cpp b/analyzer/service_data.cpp
index 2a7d5f5..28ef329 100644
--- a/analyzer/service_data.cpp
+++ b/analyzer/service_data.cpp
@@ -166,9 +166,20 @@
// A map to determine the priority order. All of the medium priorities,
// including the medium group priorities, are all the same level.
+ // clang-format off
static const std::map<std::string, unsigned int> m = {
- {"H", 3}, {"M", 2}, {"A", 2}, {"B", 2}, {"C", 2}, {"L", 1},
+ {callout::getString(callout::Priority::HIGH), 3},
+ {callout::getString(callout::Priority::MED), 2},
+ {callout::getString(callout::Priority::MED_A), 2},
+ {callout::getString(callout::Priority::MED_B), 2},
+ {callout::getString(callout::Priority::MED_C), 2},
+ {callout::getString(callout::Priority::LOW), 1},
};
+ // clang-format on
+
+ // The new callout must contain a valid priority.
+ assert(i_callout.contains("Priority") &&
+ m.contains(i_callout.at("Priority")));
bool addCallout = true;