<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: job status notification in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284801#M58423</link>
    <description>It depends on what somebody has to do when a job fails. Sending an email is a good idea. It could also a good idea to start a job next to the failed job to restore the previous state or avoid further processing. 
&lt;BR /&gt;The most useful information between jobs are the return code (or exist code or error code == always the same). Return code == 0 means everything is fine and all others means there is something wrong or not fully OK. 
&lt;BR /&gt;I would suggest differentiate between: 
&lt;BR /&gt;* those problems wich can be solved by a rerun of the job (e.g. a resource for the job is not ready like databases or file servers) and 
&lt;BR /&gt;* those problems which are caused by wrong input data and 
&lt;BR /&gt;* those problems which are caused by an programming error of the job.</description>
    <pubDate>Tue, 31 Dec 2013 09:55:35 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2013-12-31T09:55:35Z</dc:date>
    <item>
      <title>job status notification</title>
      <link>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284799#M58421</link>
      <description>Hello,&lt;BR /&gt;what is the typical practice followed to notify job failures? Is it to include tlogcatcher linked to a tsend email in every job? or to link a tsendemail to every component or  can it be setup in execution plan ? or are there any other ways to do it.&lt;BR /&gt;THanks.</description>
      <pubDate>Tue, 31 Dec 2013 03:32:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284799#M58421</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2013-12-31T03:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: job status notification</title>
      <link>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284800#M58422</link>
      <description>Hi, &lt;BR /&gt;Are you looking for &lt;A href="https://help.talend.com/search/all?query=Error+report+view&amp;amp;content-lang=en" target="_blank" rel="nofollow noopener noreferrer"&gt;TalendHelpCenter:Error report view&lt;/A&gt; and &lt;A href="https://help.talend.com/search/all?query=Recovering+job+execution&amp;amp;content-lang=en" target="_blank" rel="nofollow noopener noreferrer"&gt;Recovering job execution&lt;/A&gt;?&lt;BR /&gt;Best regards&lt;BR /&gt;Sabrina</description>
      <pubDate>Tue, 31 Dec 2013 05:14:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284800#M58422</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-12-31T05:14:09Z</dc:date>
    </item>
    <item>
      <title>Re: job status notification</title>
      <link>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284801#M58423</link>
      <description>It depends on what somebody has to do when a job fails. Sending an email is a good idea. It could also a good idea to start a job next to the failed job to restore the previous state or avoid further processing. 
&lt;BR /&gt;The most useful information between jobs are the return code (or exist code or error code == always the same). Return code == 0 means everything is fine and all others means there is something wrong or not fully OK. 
&lt;BR /&gt;I would suggest differentiate between: 
&lt;BR /&gt;* those problems wich can be solved by a rerun of the job (e.g. a resource for the job is not ready like databases or file servers) and 
&lt;BR /&gt;* those problems which are caused by wrong input data and 
&lt;BR /&gt;* those problems which are caused by an programming error of the job.</description>
      <pubDate>Tue, 31 Dec 2013 09:55:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284801#M58423</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-12-31T09:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: job status notification</title>
      <link>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284802#M58424</link>
      <description>Thats a good suggestion to categorize errors by Jlolling. But i am wondering about industry standards followed to notify production support team of the job failures. Are the TAC generated notifications as informative as a job with logcatcher - sendemail components? are jobs with logcatcher more resource intensive?</description>
      <pubDate>Tue, 31 Dec 2013 13:16:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284802#M58424</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2013-12-31T13:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: job status notification</title>
      <link>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284803#M58425</link>
      <description>You could also try the - unfortunately outdated tSNMP component. It is a common way to track the reliability of software components via SNMP to things like Nagios or Icinga.
&lt;BR /&gt;You could also send emails to a trouble ticket system like OTRS. In this case you get a ticket and you can define who will be notified next.</description>
      <pubDate>Tue, 31 Dec 2013 13:55:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284803#M58425</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-12-31T13:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: job status notification</title>
      <link>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284804#M58426</link>
      <description>hi,&lt;BR /&gt;if you are using TAC , you have Notification that allows to send email to subscriber on task failed (or other events)&lt;BR /&gt;regards&lt;BR /&gt;laurent</description>
      <pubDate>Tue, 31 Dec 2013 14:44:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/job-status-notification/m-p/2284804#M58426</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-12-31T14:44:41Z</dc:date>
    </item>
  </channel>
</rss>

