[EAGLE-848] eagle should log proper error instead of dying

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: v0.5.0
• Fix Version/s: v0.5.0
• Component/s: Core::Alert Engine
• Assignee: Jay Sen
• Reporter: Jay Sen
• Created: 02/Jan/17 23:49
• Updated: 13/Feb/17 23:30
• Resolved: 13/Feb/17 23:30

Description

on several occasions, I found eagle server dies because the exception is not handled, we should gather here such places, and put up proper exception handling to log the error that tells users of why exactly something didnt work.
here is 1 example to begin with.

eagle-server died because the topic mentioned to start application didnt exist in zookeeper.

! Causing: java.lang.RuntimeException: java.lang.RuntimeException: org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /brokers/topics/hadoop_jmx_metric/partitions

it would be even better to provide dropdown list of suggestion to choose topic from.