You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Bill Graham (JIRA)" <ji...@apache.org> on 2010/04/26 20:12:31 UTC
[jira] Created: (CHUKWA-479) Support HTTP trigger actions
Support HTTP trigger actions
----------------------------
Key: CHUKWA-479
URL: https://issues.apache.org/jira/browse/CHUKWA-479
Project: Hadoop Chukwa
Issue Type: New Feature
Reporter: Bill Graham
Assignee: Bill Graham
Now that there is a framework for triggering actions (which is in use by the "post Demux success" action), create a trigger action that can make an HTTP request when invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-479) Support HTTP trigger actions
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Graham updated CHUKWA-479:
-------------------------------
Status: Patch Available (was: Open)
Release Note: Support for firing HTTP requests upon a given trigger event.
> Support HTTP trigger actions
> ----------------------------
>
> Key: CHUKWA-479
> URL: https://issues.apache.org/jira/browse/CHUKWA-479
> Project: Hadoop Chukwa
> Issue Type: New Feature
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: CHUKWA-479.1.patch
>
>
> Now that there is a framework for triggering actions (which is in use by the "post Demux success" action), create a trigger action that can make an HTTP request when invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-479) Support HTTP trigger actions
Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ari Rabkin updated CHUKWA-479:
------------------------------
Status: Resolved (was: Patch Available)
Resolution: Fixed
Looks ok and I just committed this.
> Support HTTP trigger actions
> ----------------------------
>
> Key: CHUKWA-479
> URL: https://issues.apache.org/jira/browse/CHUKWA-479
> Project: Hadoop Chukwa
> Issue Type: New Feature
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: CHUKWA-479.1.patch
>
>
> Now that there is a framework for triggering actions (which is in use by the "post Demux success" action), create a trigger action that can make an HTTP request when invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CHUKWA-479) Support HTTP trigger actions
Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862277#action_12862277 ]
Ari Rabkin commented on CHUKWA-479:
-----------------------------------
Thanks. :)
> Support HTTP trigger actions
> ----------------------------
>
> Key: CHUKWA-479
> URL: https://issues.apache.org/jira/browse/CHUKWA-479
> Project: Hadoop Chukwa
> Issue Type: New Feature
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: CHUKWA-479.1.patch
>
>
> Now that there is a framework for triggering actions (which is in use by the "post Demux success" action), create a trigger action that can make an HTTP request when invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-479) Support HTTP trigger actions
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Graham updated CHUKWA-479:
-------------------------------
Attachment: CHUKWA-479.1.patch
Attaching CHUKWA-479.1.patch, which contains the {{HttpTriggerAction}} class. Paraphrasing the javadocs:
The general format of this classes configs is {{chukwa.trigger.[eventName].http.[N].[paramName]}} where {{eventName}} is the name of the event the request values are bound to (see {{TriggerEvent}}), {{N}} is a counter for each request configured (starting at 1) and {{paramName}} is the request parameter being set.
Using the "post demux success" trigger event as an example, the first request to be fired would use the following configurations
* {{chukwa.trigger.post.demux.success.http.1.url}} - The HTTP url to invoke.
* {{chukwa.trigger.post.demux.success.http.1.method}} - The HTTP method (optional, default=GET).
* {{chukwa.trigger.post.demux.success.http.1.headers}} - A comma-delimited set of HTTP headers (in {{[headerName]:[headerValue]}} form) to include (optional).
* {{chukwa.trigger.post.demux.success.http.1.body}} - The text HTTP body to include (optional).
* {{chukwa.trigger.post.demux.success.http.1.connect.timeout}} - The HTTP connection timeout setting in milliseconds (optional, default=5000ms).
* {{chukwa.trigger.post.demux.success.http.1.read.timeout}} - The HTTP read timeout setting in milliseconds (optional, default=5000ms).
I do not have a unit test for this class, since it relies on an external web server, but I've been running it successfully for a week or so.
> Support HTTP trigger actions
> ----------------------------
>
> Key: CHUKWA-479
> URL: https://issues.apache.org/jira/browse/CHUKWA-479
> Project: Hadoop Chukwa
> Issue Type: New Feature
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: CHUKWA-479.1.patch
>
>
> Now that there is a framework for triggering actions (which is in use by the "post Demux success" action), create a trigger action that can make an HTTP request when invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.