Docs for new metrics (shutdown, qcmp, etc)

Documentation for new metrics introduced in googleforgames#1047

docs/src/deployment/admin.md

@@ -103,7 +103,11 @@ Quilkin exposes the following metrics on heap allocations, which are useful for
 
  * `quilkin_extant_allocation_count` (Gauge)
 
-    The current number of extant allocations"
+    The current number of extant allocations
+
+* `quilkin_shutdown_initiated`
+
+    Shutdown process has been started
 
 ### /debug/pprof/profile
 

docs/src/services/proxy/metrics.md

@@ -49,7 +49,7 @@ The proxy exposes the following general metrics:
 
 * `quilkin_bytes_total{event, asn, ip_prefix}`
 
-   The total number of bytes sent or recieved
+   The total number of bytes sent or received
   * The `event` label is either:
     * `read`: when the proxy receives data from a downstream connection on the listening port.
     * `write`: when the proxy sends data to a downstream connection via the listening port.
@@ -69,6 +69,14 @@ The proxy exposes the following general metrics:
 
   The total number of errors encountered while reading a packet from the upstream endpoint.
 
+* `quilkin_game_traffic_tasks`
+
+  The amount of game traffic tasks that have spawned
+
+* `quilkin_game_traffic_task_closed`
+
+  The amount of game traffic tasks that have shutdown
+
 ## Session Metrics
 
 The proxy exposes the following metrics around sessions:

docs/src/services/proxy/qcmp.md

@@ -102,3 +102,17 @@ request to the QCMP port.
 
 The returned data is a JSON object with each key being the ICAO code for the
 datacentre, and the value being the latency in nanoseconds.
+
+## Metrics
+
+* `quilkin_phoenix_requests`
+
+  The amount of phoenix (latency) requests
+
+* `quilkin_phoenix_task_closed`
+
+  Whether the phoenix latency measurement task has shutdown
+
+* `quilkin_phoenix_server_errors`
+
+  The amount of errors attempting to spawn the phoenix HTTP server