Thanks Eric, I'm glad I emailed before writing code. I can see how data loaders get triggered, but I don't see one that makes an HTTP request like I'm proposing. Are you suggesting I implement a new DataLoader that doesn't actually load data, but makes an HTTP request instead?
On Fri, Apr 16, 2010 at 7:30 PM, Eric Yang <ey...@yahoo-inc.com> wrote: > Hi Bill, > > This already exist in Chukwa. Take a look in DataLoaderFactory.java and > SocketDataLoader.java, they are triggered after demux jobs. Hence, you can > use PostProcessManager as triggers, and configure it through > chukwa-demux-conf.xml, chukwa.post.demux.data.loader. Hope this helps. > > Regards, > Eric > > > On 4/16/10 4:39 PM, "Bill Graham" <billgra...@gmail.com> wrote: > > Hi, > > I'd like to add a feature to the DemuxManager where you can configure an > HTTP request to be fired after a Demux run. It would be similar to what's > currently there for Nagios alerts, only this would be HTTP (the Nagios alert > is a raw TCP socket call). You'd configure the host, port, (POST|GET) and > uri for this first pass. > > Some metadata about the job would also go along for the ride. Maybe things > like status code and job name. > > The use case is to trigger a dependent job to run elsewhere upon > completion. The same functionality could potentially be ported to some of > the other chukwa processor jobs if the need arose. > > Thoughts? > > thanks, > Bill > >
