Description of problem: Currently, when customer gets e-mails related to cluster level alerts (primarily all the services running under cluster in nagios space ) the message reads like this, which is confusing the customers.


***************current e-mails********************
e.g.1

***** Nagios *****

Notification Type: PROBLEM

Service: Cluster Utilization
Host: Eskan
Address: Eskan
State: CRITICAL

Date/Time: Tue Sept 30 21:27:04 AST 2014

Additional Info:

(null)
 
-----------------------------------------------------
e.g.2

***** Nagios *****

Notification Type: PROBLEM

Service: Volume Self-Heal - data
Host: Eskan
Address: Eskan
State: WARNING

Date/Time: Tue Sept 30 21:29:34 AST 2014

Additional Info:

(null)

**********************************************

How reproducible: Everytime


Steps to Reproduce:
1. This can happen for multiple services running under cluster (volume status, volume-unitilization, cluster-unitilization, geo-rep, self-heal, etc... ) . Lets take the case of volume status. If you stop one volume under the cluster, it will change the status to CRITICAL.
2. If e-mail notification is configured, it will send the alert to the mentioned e-mail
3. And the content of the e-mail is similar to shown above

Actual results: 
***** Nagios *****

Notification Type: PROBLEM

Service: Volume Self-Heal - data
Host: Eskan
Address: Eskan
State: WARNING

Date/Time: Tue Sept 30 21:29:34 AST 2014

Additional Info:

(null)
*******************


Expected results:
***** Nagios *****

Notification Type: PROBLEM

Service: Volume Self-Heal - data
Cluster Name: Eskan
State: WARNING

Date/Time: Tue Sept 30 21:29:34 AST 2014

Additional Info: 
(null)
********************


Additional info: In the above example, the (null) shown for additional info, should not be null. That is being tracked in a separate bug.

The fix is name the Replace the "Host:" to "Cluster Name:" and remove the "Address:<address>" completely from the e-mail