You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2017/03/06 16:14:33 UTC
[jira] [Updated] (AMBARI-20291) Script-Based Alert Dispatchers
support passing more parameters to script
[ https://issues.apache.org/jira/browse/AMBARI-20291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-20291:
-------------------------------------
Summary: Script-Based Alert Dispatchers support passing more parameters to script (was: Script-Based Alert Dispathers support passing more parameters to script)
> Script-Based Alert Dispatchers support passing more parameters to script
> ------------------------------------------------------------------------
>
> Key: AMBARI-20291
> URL: https://issues.apache.org/jira/browse/AMBARI-20291
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: trunk
> Reporter: Yao Lei
> Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-20291_2.patch
>
>
> Script-Based Alert Dispatcher now pass five parameters to script,including alert definition name, definition label,service name, alert state, and alert text.
> But if script can receive other two parameters from dispather,it will be better.
> 1.hostname.
> Because hostname the alert for is not always included in alert text,although it may be null like aggregate alerts.
> With it we can more quick to find the related host that occured alert.
> 2.alert timestamp.
> We may need to know the alert occurrence time ( state change time) more exactly. After the alert happened,it will spend some time to schedule the script to run.
> Without it,we can only regard the script start time as the alert occurrence time.
> We now use this feature to send alert information to mobile phone and suggest also passing hostname and alert timestamp.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)