Re: Where to in codebase to add external IP to Airflow emails? TaskInstance? Some global place?

Hi Russell, The least intrusive method is to write your own "on_failure_callback" mechanism, not use the failure emails and then replicate the email handling code there with the ipgetter code. I'd then turn this into some common utility code and look into using "default_args" to have this set as

Re: Where to in codebase to add external IP to Airflow emails? TaskInstance? Some global place?

bump? Russell Jurney @rjurney russell.jur...@gmail.com LI FB datasyndrome.com On Tue, Jul 18, 2017 at 4:36 PM, Russell Jurney wrote: > I created a JIRA to track this issue: https://issues.apache. >

Re: Where to in codebase to add external IP to Airflow emails? TaskInstance? Some global place?

I created a JIRA to track this issue: https://issues.apache.org/jira/browse/AIRFLOW-1425 Russell Jurney @rjurney russell.jur...@gmail.com LI FB datasyndrome.com On Tue, Jul 18, 2017 at 4:33 PM, Russel

Where to in codebase to add external IP to Airflow emails? TaskInstance? Some global place?

I need my Airflow emails to contain the external IP address of the machine, as determined by ipgetter.myip(). In terms of how it behaves this seems to work, as it times out after 2 seconds and returns null string if it doesn't get a reply. I can see where I can add this in TaskInstance, a field se