Skip to main content
Archived

Workspaces Failure E-mail Notification

Related products:FME Flow
  • December 28, 2016
  • 2 replies
  • 67 views

Hello FME Community:

My suggestion is to provide the ability to send one e-mail notification listing all failed workspaces on daily bases. This will help admin to pick up what failed with a quick glance at a single e-mail message.

Example: jobs A,B,C,D, and E are scheduled to run daily

If jobs A,C, and E fail --> send a single e-mail stating that jobs A, C, and E failed.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

david_r
Celebrity
  • January 3, 2017

This is relatively simple to implement using a scheduled workspace and querying the REST API with an HTTPCaller, e.g.

/fmerest/v2/transformations/jobs/completed?accept=json&detail=high&limit=-1&offset=-1

Then filter out those jobs where "status" = FME_FAILURE etc.

Documentation: https://docs.safe.com/fme/html/FME_REST/v2/apidoc/index.html#


rylanatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • February 14, 2018
I think this is an excellent suggestion by @david_r. It is likely possible to achieve this by configuring a workspace and have itself scheduled to run daily – make sure you set to notify if this fails! Would this address your concerns / idea, @mnabhani?

 

 

*Please also note that there now is Version 3 of the FME Server REST API. I would recommend using the endpoint documented here: https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/transformations/list_get_19

 

 

As an added bonus, you could write out the 'offset' to a lightweight database (e.g. SpatiaLite) to reduce the number of completed job records you read in – i.e. if that starts to incur significant overhead for a busy FME Server!