Once you send your first event.

Question

darron opened this issue 9 years ago · 3 comments

Then STDIN isn't empty going forward. So it will still fire WAY more often than you want.

Need to check and see if this node has seen that particular LTime yet. If it hasn't - run again. If it has - don't do the thing.

Will maybe store the last known and highest LTtime in:

sifter/event-name/hostname

Answer 1 · 2015-11-12T06:49:31.000Z

Partially there as of this evening. Need to properly parse JSON Array values and it will work.

Answer 2 · 2015-11-12T20:21:20.000Z

It's "working" with this one hack in place:

Has helped to make sure it doesn't create many, many more processes than it should - but broken with more than 1 event in the payload.

Answer 3 · 2015-11-12T20:23:56.000Z

And LTime is being stored: