Skip to main content
Solved

How to interpret FME log message?

  • May 17, 2018
  • 4 replies
  • 22 views

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.

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.

4 replies

david_r
Celebrity
  • 8394 replies
  • 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+60
  • Celebrity
  • 3703 replies
  • 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.

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
  • 8394 replies
  • May 17, 2018
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
  • Author
  • 10 replies
  • 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.

Thanks! You post solves my problem.