GAE / J magazine format failure

Question

Here is an example GAE Console log entry:

http://i.stack.imgur.com/M2iJX.png for the readable high-resolution version.

I would like to provide a breakdown of the fields displayed both in the summary (summary) view and in the enlarged (detailed) view. I will fill in the fields that I know their meaning, and I will be grateful for the help with dixip the rest. This message will be updated after receiving new information.

Thanks,
Maksim.

---

Open problems:

• How to read a timestamp? [...- prod / 0-0-39. 346862139187007139 ]
• Why does the resume say that the request took 343 ms, but says 344ms in detail?
• If the request spends 123 ms on the processor and 30 ms on API calls, where did the rest of the time go? Why is the total request time 343/344 ms?

Answer 1

Summary

• 12-14 : date of request. 12 - month (December), 14 - day of the month (Tuesday).
• 05:21 AM : Request time, PST offset. 05 is the hour. 21 is a minute.
• 57.593 : request time, PST offset. 57 - the second. 593 is the millisecond.
• / match / ... : HTTP request path
• 200 : HTTP return code. (200 = OK)
• 343ms : total time (in milliseconds) needed to calculate and return a response to the user
• 123cpu_ms : time (in milliseconds) spent on CPU calculation is calculated
• 30api_cpu_ms : the time (in milliseconds) of the request is spent on API calls (Datastore get and co ...)
• 1kb : size (in kilobytes) of the response sent to the user
• Mozilla / 5.0 (X11; U; Linux x86_64; ru-US) AppleWebKit / 534.7 (KHTML, e.g. Gecko) Chrome / 7.0.517.44 Safari / 534.7, gzip (gfe) : User Agent notes that gzip (gfe) is added by the interface AppEngine

More details

• IP yellow masked out : IP address of the client initiating the request
• HTTP Referrer : note that it is empty in this request because it is a direct click
• [14 / Dec / 2010: 05: 21: 57 -0800] : Date, including metric offset specification.
• "GET / match / ... HTTP / 1.1" : HTTP GET URI.
• 200 : HTTP return code. (200 = OK)
• 1036 : size (in bytes) of the response sent to the user
• Mozilla / 5.0 (X11; U; Linux x86_64; ru-US) AppleWebKit / 534.7 (KHTML, e.g. Gecko) Chrome / 7.0.517.44 Safari / 534.7, gzip (gfe) : User Agent notes that gzip (gfe) is added by the interface AppEngine
• ms = 344 : the total time (in milliseconds) was required to calculate and return a response to the user
• cpu_ms = 123 : time (in milliseconds) to trace the request for CPU calculation
• api_cpu_ms = 30 : the time (in milliseconds) of the request is spent on API calls (Datastore get and co ...)
• cpm_usd = 0.003648 : the amount (in $$) that will cost 1000 requests, like this one. ref

journal entry

• 12-14 : The date of this particular application selected the log entry. 12 - month (December), 14 - day of the month (Tuesday).
• 05:21 AM : the time of this particular application emitted a log entry, PST offset.
• 57.833 : request time, PST offset. 57 - the second. 833 is a millisecond.
• [...- prod / 0-0-39.346862139187007139] . The identifier of the current version of the application that emitted this log message. Note. ...- prod is the name of the application. 0-0-39 is the expanded name of the version (app.yaml). .346862139187007139 - time? (in what format?) when this version was deployed to the application cloud.
• stdout The channel on which the application selected this log message. It can be either stdout or stderr.
• INFO .... Matcher -... Id 208 is consistent. : application level exit. It can be done via System.out.print or (as in this case) using the logging framework, logback

Answer 2

Not 57.593 seconds .milliseconds? And cpm_usd is an estimate that 1000 queries similar to this query will cost in US dollars.