How about an FME Option in Appearance for log error font including colour - way simpler than scripting per workspace.

Here's a suggestion using the fmeobjects log file callback and some global variables.

In the startup python script:

from fmeobjects import *
 
# Global dictionary used to stor important log messages
global fme_log_messages
fme_log_messages = {FME_WARN: m], FME_ERROR: Â], FME_FATAL: Â]}
 
# Global integer to keep track of current log line number
global fme_log_message_count
fme_log_message_count = 0
 
def catch_log_messages(severity, message):
    global fme_log_message_count
    global fme_log_messages
    fme_log_message_count += 1
    if severity in (FME_WARN, FME_ERROR, FME_FATAL) and message:
        fme_log_messages severity].append('%8d : %s' % (fme_log_message_count, message))
 
FMELogFile().setCallBack(catch_log_messages)

In the shutdown python script:

from __future__ import print_function
 
global fme_log_messages
no_messages = c' ' * 15 + 'None']
 
print('=' * 80)
print(' Line number   Log message')
print('-' * 80)
print('WARNINGS')
for warning in fme_log_messagesnFME_WARN] or no_messages:
    print(warning)
    
print('ERRORS')
for error in fme_log_messagesmFME_ERROR] or no_messages:
    print(error)
    
print('FATAL ERRORS')
for fatal in fme_log_messagesfFME_FATAL] or no_messages:
    print(fatal)
 
print('=' * 80)

At the end of the translation the shutdown script will output a synopsis of all the warnings, errors and fatal errors with line numbers (referencing the written log), e.g.:

 

Notice that the synopsis is output using the python 'print' function and that the text is therefore NOT included in the log file, it is only sent to the translation log console window. This is by design, but the script can of course be extended to also write to the log file, if necessary.

If there are no warnings etc, it looks like this:

 

Tested with Python 2.7 and 3.5.

Template file: fmelogsummarywriter.fmwt

 

Hey all!

 

 

@rollo It is indeed the fact that I cant (or hardly can) tell red from black. If I would scroll carefully line by line I could find the red lines (it is like searching the 90% grey value line in all 100% black lines)

@carmijo not in all cases the words 'error' or 'warning' are used when something is going wrong so searching for those words is not a guarantee of finding all red parts. Like in this example:

@bruceharold that would be the best solution I think.

I'm new to Python as well and based my script on  @david_r 's code from this post: https://knowledge.safe.com/questions/24394/how-to-write-a-python-script-to-log-fme-error-to-t.html

I have it using ctypes to bring up a dialog box.

Successful - Displays total features written.

Failure - Displays failed message

Startup Script

from fmeobjects import *
global my_fme_messages


my_fme_messages = s]
 
def LogSkimmer(severity, text):
    if severity in (FME_FATAL, FME_ERROR):
        my_fme_messages.append(text)
 
FMELogFile().setCallBack(LogSkimmer)

Shutdown Script

import fme
import fmeobjects
import ctypes
import winsound


global my_fme_messages
runtime = fme.elapsedRunTime / 60
status = fme.status
totalfeatureswritten = fme.totalFeaturesWritten


# Translation failed message. Filters only relevant messages
if status is False:
    for msg in my_fme_messages:
        if 'logfile' not in msg:
            winsound.PlaySound('SystemExit', winsound.SND_ASYNC) # plays windows sound
            ctypes.windll.user32.MessageBoxA(0, 'FME translation failed' + msg, 'Error', 0)
            
      
# Translation successful message. Custom message    
if status is True:
    ctypes.windll.user32.MessageBoxA(0, 'FME translation was successful. Total features written: ' + str(totalfeatureswritten), 'Successful', 0)
    winsound.PlaySound('SystemExit', winsound.SND_ASYNC) # plays windows sound

Here's a suggestion using the fmeobjects log file callback and some global variables.

In the startup python script:

from fmeobjects import *
 
# Global dictionary used to stor important log messages
global fme_log_messages
fme_log_messages = {FME_WARN: m], FME_ERROR: Â], FME_FATAL: Â]}
 
# Global integer to keep track of current log line number
global fme_log_message_count
fme_log_message_count = 0
 
def catch_log_messages(severity, message):
    global fme_log_message_count
    global fme_log_messages
    fme_log_message_count += 1
    if severity in (FME_WARN, FME_ERROR, FME_FATAL) and message:
        fme_log_messages severity].append('%8d : %s' % (fme_log_message_count, message))
 
FMELogFile().setCallBack(catch_log_messages)

In the shutdown python script:

from __future__ import print_function
 
global fme_log_messages
no_messages = c' ' * 15 + 'None']
 
print('=' * 80)
print(' Line number   Log message')
print('-' * 80)
print('WARNINGS')
for warning in fme_log_messagesnFME_WARN] or no_messages:
    print(warning)
    
print('ERRORS')
for error in fme_log_messagesmFME_ERROR] or no_messages:
    print(error)
    
print('FATAL ERRORS')
for fatal in fme_log_messagesfFME_FATAL] or no_messages:
    print(fatal)
 
print('=' * 80)

At the end of the translation the shutdown script will output a synopsis of all the warnings, errors and fatal errors with line numbers (referencing the written log), e.g.:

 

Notice that the synopsis is output using the python 'print' function and that the text is therefore NOT included in the log file, it is only sent to the translation log console window. This is by design, but the script can of course be extended to also write to the log file, if necessary.

If there are no warnings etc, it looks like this:

 

Tested with Python 2.7 and 3.5.

Template file: fmelogsummarywriter.fmwt

Hi David, Thanks for this code, it works well, however when I run the template, I get a warning.

Warning: not all FMESessions that were created were destroyed before shutdown. This may cause instability.

 

Do other people get this error?

Is this a concern if running on server?

Is there a known fix?

 

Many Thanks

 

 

Hi  David, Thanks for this code, it works well, however when I run the template, I get a warning.

Warning: not all FMESessions that were created were destroyed before shutdown. This may cause instability.

 

Do other people get this error?

      Is this a concern if running on server?

          Is there a known fix?

 

Many Thanks