Question about ArcGIS Server logging time elapsed
99
0
Thursday
by
I've been administering ArcGIS Servers for a long time and have often looked at the "view logs" tab to find services that are having problems. I'm now questioning some of things I've been taking for granted, specifically in the "Time elapsed" column.
1) Is "Time elapsed" in seconds or milliseconds?
I have always assumed it is in seconds because most of the entries are 0.xyzxy going out to 5 decimal places. So, if I see 0.55621 I assume that is about half a second (556 milliseconds). If I see 77.0 then that is 77 seconds and a problem that needs to be investigated. Today I looked at the documentation to confirm it, because I was seeing some very high numbers, like in the several hundreds range (466.0 for example). The documentation says it is in milliseconds, which would mean that 0.55621 is actually 1/2 of a millisecond? And 446.0 is nothing to worry about because it is less than half a second?
Work with server logs—ArcGIS Server | Documentation for ArcGIS Enterprise
I have always assumed it is in seconds because most of the entries are 0.xyzxy going out to 5 decimal places. So, if I see 0.55621 I assume that is about half a second (556 milliseconds). If I see 77.0 then that is 77 seconds and a problem that needs to be investigated. Today I looked at the documentation to confirm it, because I was seeing some very high numbers, like in the several hundreds range (466.0 for example). The documentation says it is in milliseconds, which would mean that 0.55621 is actually 1/2 of a millisecond? And 446.0 is nothing to worry about because it is less than half a second?
Work with server logs—ArcGIS Server | Documentation for ArcGIS Enterprise
2) "Time elapsed" is treated as a text field?
Following the login in #1, I have always thought I could sort descending on Time Elapsed to find the longest transactions and use that to identify potential issues. Today I realized it is sorting it as if were not numbers, but text? How, then, can we identify the longest running transactions to target problem services??
Following the login in #1, I have always thought I could sort descending on Time Elapsed to find the longest transactions and use that to identify potential issues. Today I realized it is sorting it as if were not numbers, but text? How, then, can we identify the longest running transactions to target problem services??
Any insight, clarification or workarounds would be appreciated.
