Skip to main content
Solved

How to interpret FME log message?


Forum|alt.badge.img+2

I have a piece of FME log message: 2018-05-16 13:20:18| 0.1| 0.0|INFORM|FME Configuration: Reader Keyword is `MULTI_READER'

 

I can guess all of the pieces except for 0.0 and 0.1. Does anyone have a clue?

Best answer by david_r

Taken from the FME Desktop training manual:

Log timestamps indicate the absolute date and time for each step of the translation process. They also show the time taken by FME to process the previous stage and the cumulative time taken to reach that point in the translation.

Unfortunately, the text has the order of the timings slightly backwards, it's like this:

  • In your example, 0.1 is the cumulative time taken to reach that point in the translation, and
  • 0 is the time taken by FME to process the previous stage

It's easier to understand the relationship between the two values if you have a complete log file to look at.

View original
Did this help you find an answer to your question?

4 replies

david_r
Celebrity
  • Best Answer
  • May 17, 2018

Taken from the FME Desktop training manual:

Log timestamps indicate the absolute date and time for each step of the translation process. They also show the time taken by FME to process the previous stage and the cumulative time taken to reach that point in the translation.

Unfortunately, the text has the order of the timings slightly backwards, it's like this:

  • In your example, 0.1 is the cumulative time taken to reach that point in the translation, and
  • 0 is the time taken by FME to process the previous stage

It's easier to understand the relationship between the two values if you have a complete log file to look at.


redgeographics
Celebrity
Forum|alt.badge.img+49
david_r wrote:

Taken from the FME Desktop training manual:

Log timestamps indicate the absolute date and time for each step of the translation process. They also show the time taken by FME to process the previous stage and the cumulative time taken to reach that point in the translation.

Unfortunately, the text has the order of the timings slightly backwards, it's like this:

  • In your example, 0.1 is the cumulative time taken to reach that point in the translation, and
  • 0 is the time taken by FME to process the previous stage

It's easier to understand the relationship between the two values if you have a complete log file to look at.

I'd like to add that those log timings don't go any more detailed than 0.1 second, in reality it might be much faster.

 

 


david_r
Celebrity
  • May 17, 2018
redgeographics wrote:
I'd like to add that those log timings don't go any more detailed than 0.1 second, in reality it might be much faster.

 

 

Yes, good catch. If you start looking into details you'll see that there's some internal rounding going on before a value gets sent to the log.

Forum|alt.badge.img+2
david_r wrote:

Taken from the FME Desktop training manual:

Log timestamps indicate the absolute date and time for each step of the translation process. They also show the time taken by FME to process the previous stage and the cumulative time taken to reach that point in the translation.

Unfortunately, the text has the order of the timings slightly backwards, it's like this:

  • In your example, 0.1 is the cumulative time taken to reach that point in the translation, and
  • 0 is the time taken by FME to process the previous stage

It's easier to understand the relationship between the two values if you have a complete log file to look at.

Thanks! You post solves my problem.

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings