reference.rst 7.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230
  1. .. _monitor_reference:
  2. Data Reference
  3. ==============
  4. The following is a list of all the attributes of a request that are captured by
  5. the monitor extension.
  6. General
  7. -------
  8. .. list-table::
  9. :widths: 20 65 15
  10. :header-rows: 1
  11. * - Attribute
  12. - Description
  13. - Type
  14. * - ID
  15. - Numeric identifier of the request. Every request is assigned an identifier upon
  16. its creation.
  17. - Numeric
  18. * - Status
  19. - Status of the request. See :ref:`notes <status>` below.
  20. - String
  21. * - Category
  22. - The type of request being made, for example an OGC service request, a REST call, etc...
  23. See :ref:`notes <category>` below.
  24. - String
  25. * - Start time
  26. - The time of the start of the request.
  27. - Timestamp
  28. * - End time
  29. - The time of the completion of the request.
  30. - Timestamp
  31. * - Total time
  32. - The total time spent handling the request, measured in milliseconds, equal to
  33. the end time - start time.
  34. - Numeric
  35. * - Error message
  36. - The exception message if the request failed or resulted in an error.
  37. - String
  38. * - Error
  39. - The raw exception if the message failed or resulted in an error.
  40. - Text blob
  41. .. _status:
  42. Status
  43. ^^^^^^
  44. The status of a request changes over it's life cycle and may have one of the
  45. following values:
  46. * ``WAITING`` - The request has been received by the server, but is queued and not yet
  47. being actively handled.
  48. * ``RUNNING`` - The request is in the process of being handled by the server.
  49. * ``FINISHED`` - The request has been completed and finished normally.
  50. * ``FAILED`` - The request has been completed but resulted in an error.
  51. * ``CANCELLED`` - The request was cancelled before it could complete.
  52. * ``INTERRUPTED`` - The request was interrupted before it could complete.
  53. .. _category:
  54. Category
  55. ^^^^^^^^
  56. Requests are grouped into categories that describe the nature or type of the request. The
  57. following are the list of all categories:
  58. * ``OWS`` - The request is an OGC service request.
  59. * ``REST`` - The request is a REST service request.
  60. * ``OTHER`` - All other requests.
  61. HTTP
  62. ----
  63. The following attributes are all HTTP related.
  64. .. list-table::
  65. :widths: 20 65 15
  66. :header-rows: 1
  67. * - Attribute
  68. - Description
  69. - Type
  70. * - HTTP method
  71. - The HTTP method, one of ``GET``, ``POST``, ``PUT``, or ``DELETE``
  72. - String
  73. * - Remote address
  74. - The IP address of the client from which the request originated.
  75. - String
  76. * - Remote host
  77. - The hostname corresponding to the remote address, obtained via reverse DNS lookup.
  78. - String
  79. * - Host
  80. - The hostname of the server handling the request, from the point of view of the client.
  81. - String
  82. * - Internal host
  83. - The hostname of the server handling request, from the point of view of the local network.
  84. Availability depends on host and network configuration.
  85. - String
  86. * - Path
  87. - The path component of the request URL, for example: "/wms", "/rest/workspaces.xml", etc...
  88. - String
  89. * - Query string
  90. - The query string component of the request URL. Typically only present when the HTTP method is GET.
  91. - String
  92. * - Body
  93. - The body content of the request. Typically only present when the HTTP method is PUT or POST.
  94. - Binary blob
  95. * - Body content length
  96. - The total number of bytes comprising the body of the request. Typically only present when the
  97. HTTP method is PUT or POST.
  98. - Numeric
  99. * - Body content type
  100. - The mime type of the body content of the request, for example: "application/json",
  101. "text/xml; subtype=gml/3.2", etc... Typically only present when the HTTP method is PUT or POST.
  102. - String
  103. * - Response status
  104. - The HTTP response code, for example: 200, 401, etc...
  105. - Numeric
  106. * - Response length
  107. - The total number of bytes comprising the response to the request.
  108. - Numeric
  109. * - Response content type
  110. - The mime type of the response to the request.
  111. - String
  112. * - Remote user
  113. - The username specified parsed of the request. Only available when request included credentials
  114. for authentication.
  115. - String
  116. * - Remote user agent
  117. - The value of the ``User-Agent`` HTTP header.
  118. - String
  119. * - Http referrer
  120. - The value of the ``Referer`` HTTP header.
  121. - String
  122. OWS/OGC
  123. -------
  124. The following attributes are OGC service specific.
  125. .. list-table::
  126. :widths: 20 65 15
  127. :header-rows: 1
  128. * - Attribute
  129. - Description
  130. - Type
  131. * - Service
  132. - The OGC service identifier, for example: "WMS", "WFS", etc...
  133. - String
  134. * - Operation
  135. - The OGC operation name, for example: "GetMap", "GetFeature", etc...
  136. - String
  137. * - Sub operation
  138. - The ogc sub operation (if it applies). For instance when the operation is a WFS Transaction
  139. the sub operation may be one of "Insert", "Update", etc...
  140. - String
  141. * - OWS/OGC Version
  142. - The OGC service version, for example with WFS the version may be "1.0.0", "1.1.0", etc...
  143. - String
  144. * - Resources
  145. - Names of resources (layers, processes, etc...) specified as part of the request.
  146. - List of String
  147. * - Resources processing times in milliseconds.
  148. - Rendering times for resources. Rendering is performed by two concurrent threads, one reading and preprocessing data and styles towards a Java2D compatible
  149. format, the other painting the results of the first on the canvas. When the first thread starts reading the next layer, the second thread is likely still painting features from the layer before it, thus, times in this list are overlapping with each other, and the sum will be greater than the actual wall rendering time.
  150. - List of Numeric
  151. * - Labels Processing Time
  152. - Processing time in milliseconds for the labels of all resources listed.
  153. - Numeric
  154. * - Bounding box
  155. - The bounding box specified as part of the request. In some cases this is not possible to
  156. obtain this reliable, an example being a complex WFS query with a nested "BBOX" filter.
  157. - List of Numeric
  158. GeoIP
  159. -----
  160. The following attributes are specific to GeoIP look ups and are not captured out of the box. See
  161. :ref:`monitor_geoip` for more details.
  162. .. list-table::
  163. :widths: 20 65 15
  164. :header-rows: 1
  165. * - Attribute
  166. - Description
  167. - Type
  168. * - Remote country
  169. - Name of the country of the client from which the request originated.
  170. - String
  171. * - Remote city
  172. - Name of the city from which the request originated.
  173. - String
  174. * - Remote lat
  175. - The latitude from which the request originated.
  176. - Numeric
  177. * - Remote lon
  178. - The longitude from which the request originated.
  179. - Numeric
  180. GWC
  181. ---
  182. The following attributes are specific to tile cached requests.
  183. .. list-table::
  184. :widths: 20 65 15
  185. :header-rows: 1
  186. * - Attribute
  187. - Description
  188. - Type
  189. * - CacheResult
  190. - "HIT" or "MISS" (can be empty if GWC was not involved)
  191. - String
  192. * - MissReason
  193. - A description of why the cache was not used. Available only on requests hitting a cached layer on direct WMS integration,
  194. applies to cases where the request was not forwarded to GWC, for example "no parameter filter exists for FEATUREID",
  195. "request does not align to grid(s) "EPSG:4326" or "not a tile layer". Will be missing for
  196. any request not hitting the direct integration (e.g., direct WMTS requests, for example)
  197. - String