[EDU-5020] fix: adjust time-related metrics in Observe Docs (#1311)

* fix: adjust time metrics in Events - EN

* fix: adjust time metrics in Metrics

* fix: adjust time metrics in Data Stream - EN

* fix: adjust time metrics in Data Stream - PT

* fix: adjust time metrics in Metrics - PT

* fix: adjust time metrics in Events - PT

* Apply suggestions from code review

Co-authored-by: Guilherme Afonso Oliveira  <guilherme.oliveira@azion.com>

* Update src/content/docs/pt-br/pages/devtools/api-graphql/recursos/events-campos.mdx

---------

Co-authored-by: Guilherme Afonso Oliveira <guilherme.oliveira@azion.com>

src/content/docs/en/pages/devtools/api-graphql/features/events-fields.mdx

@@ -80,7 +80,7 @@ See each available field and their descriptions below.
 | edgeFunctionsInitiatorTypeList | List of initiators used in the function separated by `;`. Can be `1` (Edge Application) or `2` (Edge Firewall). |
 | edgeFunctionsList | List of edge functions that were invocated during the request, in order. The order begins from left to right, meaning functions on the left were invocated first. Example: `3324;43` |
 | edgeFunctionsSolutionId | Identifier of your edge function. Example: `1321` |
-| edgeFunctionsTime | Total execution time, in milliseconds, for the function during its processing. This field is the result of a sum. Example: `0.021` |
+| edgeFunctionsTime | Total execution time, in seconds, for the function during its processing. This field is the result of a sum. Example: `0.021` |
 | functionLanguage | Language used in the function. Example: `javascript` |
 | ts | Timestamp of when the event was created. Example: `2022-10-20T10:10:10` |
 | virtualHostId | Unique ID available on Azion Console. Set on virtual host configuration file. Example: `2410001a` |
@@ -104,7 +104,7 @@ See each available field and their descriptions below.
 | requestId | Unique request identifier. Example: `5f222ae5938482c32a822dbf15e19f0f` |
 | requestLength | Request length in bytes, including request line, headers, and body. This field is the result of a sum. Example: `167` |
 | requestMethod | HTTP request method. Example: `GET` or `POST` |
-| requestTime | Request processing time elapsed since the first bytes were read from the client with resolution in milliseconds. This field is the result of a sum. Example: `1.19` |
+| requestTime | Request processing time, in seconds, since the first bytes were read from the client. This field is the result of a sum. Example: `0.234` |
 | requestUri | URI of the request made by the end user, without the host and protocol information and with arguments. Example: `/v1?v=bo%20dim` |
 | remoteAddress | IP address of the origin that generated the request. Example: `127.0.0.1` |
 | remotePort | Port of the origin that generated the request. Example: `8080` |
@@ -123,7 +123,7 @@ See each available field and their descriptions below.
 | stacktrace | Provides the names of the Rules Engine from your edge application or your edge firewall that are run by the request. Example: `{\\\"edge_firewall\\\":[\\\"Global - Set WAF\\\"]}` |
 | status | HTTP status code of the request. Example: `200` |
 | streamName | ID set through virtual host configuration based on location directive. Set on virtual host configuration file. Example: `company_sector.sdp` |
-| tcpinfoRtt |	Round-Trip Time (RTT) in milliseconds measured by the edge for the user. Available on systems that support the TCP_INFO socket option. Example: `72052` |
+| tcpinfoRtt | Round-Trip Time (RTT) in microseconds measured by the edge for the user. Available on systems that support the TCP_INFO socket option. Example: `72052` |
 | ts | Timestamp of when the event was created. Example: `2022-10-20T10:10:10` |
 | upstreamAddr | Client’s IP address and port. Can also store multiple servers or server groups. Example: `192.168.1.1:80`. When the response is `127.0.0.1:1666`, the upstream is [Azion Cells Runtime](/en/documentation/runtime/overview/). |
 | upstreamAddrStr | List with all `upstreamAddr` responses. |
@@ -132,11 +132,11 @@ See each available field and their descriptions below.
 | upstreamBytesSent | Number of bytes sent to the origin. Example: `2733` |
 | upstreamBytesSentStr | List with all `upstreamBytesSent` responses. |
 | upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
-| upstreamConnectTime | Time it takes for the edge to establish a connection with the origin in milliseconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **`0` in case of KeepAlive and `-` in case of cache.** |
+| upstreamConnectTime | Time it takes for the edge to establish a connection with the origin, in seconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **Returns `0` for KeepAlive and `-` for cache** |
 | upstreamConnectTimeStr | List with all `upstreamConnectTime` responses. |
-| upstreamHeaderTime | Time it takes for the edge to receive the response header from the origin in milliseconds. Example: `0.345`. **In case of cache, the response is `-`**. |
+| upstreamHeaderTime | Time it takes for the edge to receive the response header from the origin, in seconds. Example: `0.345`. **In case of cache, the response is `-`** |
 | upstreamHeaderTimeStr | List with all `upstreamHeaderTime` responses. |
-| upstreamResponseTime | Time it takes for the edge to receive a default response from the origin in milliseconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`**. |
+| upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`** |
 | upstreamResponseTimeStr | List with all `upstreamResponseTime` responses. |
 | upstreamStatus | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `-`**. |
 | upstreamStatusStr | List with all `upstreamStatus` responses. |
@@ -179,7 +179,7 @@ See each available field and their descriptions below.
 | remoteAddr | IP address of the origin that generated the request. Example: `127.0.0.1` |
 | remotePort | Port of the origin that generated the request. Example: `8080` |
 | requestMethod | HTTP request method. Example: `GET` or `POST` |
-| requestTime | Request processing time elapsed since the first bytes were read from the client with resolution in milliseconds. This field is the result of a sum. Example: `1.19` |
+| requestTime | Request processing time, in seconds, since the first bytes were read from the client. This field is the result of a sum. Example: `0.234` |
 | requestUri | URI of the request made by the end user, without the host and protocol information and with arguments. Example: `/v1?v=bo%20dim` |
 | scheme | Request scheme. Example: `HTTP` or `HTTPS` |
 | sentHttpContentType | `Content-Type` header sent in the origin’s response. Example: `text/html; charset=UTF-8` |
@@ -192,7 +192,7 @@ See each available field and their descriptions below.
 | tcpInfoRtt | Round-Trip Time (RTT) measured by the edge for the user. Available on systems that support the TCP_INFO socket option. Example: `72052` |
 | ts | Timestamp of when the event was created. Example: `2022-10-20T10:10:10` |
 | upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
-| upstreamResponseTime | Time it takes for the edge to receive a default response from the origin in milliseconds, including headers and body. This field is the result of a sum. Example: `0.876`. **In case of cache, the response is `-`**. |
+| upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. This field is the result of a sum. Example: `0.876`. **In case of cache, the response is `-`** |
 | upstreamResponseTimeStr | List with all `upstreamResponseTime` responses. |
 | upstreamStatus | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `-`.** |
 | upstreamStatusStr | List with all `upstreamStatus` responses. |
@@ -216,7 +216,7 @@ See each available field and their descriptions below.
 | remotePort | Port of the origin that generated the request. Example: `8080` |
 | requestLength | Request length, including request line, headers, and body. This field is the result of a sum. Example: `167` |
 | requestMethod | HTTP request method. Example: `GET` or `POST` |
-| requestTime | Request processing time elapsed since the first bytes were read from the client with resolution in milliseconds. This field is the result of a sum. Example: `1.19` |
+| requestTime | Request processing time, in seconds, since the first bytes were read from the client. This field is the result of a sum. Example: `0.234` |
 | requestUri | URI of the request made by the end user, without the host and protocol information and with arguments. Example: `/v1?v=bo%20dim` |
 | scheme | Request scheme. Example: `HTTP` or `HTTPS` |
 | sentHttpContentType | `Content-Type` header sent in the origin’s response. Example: `text/html; charset=UTF-8` |
@@ -228,9 +228,9 @@ See each available field and their descriptions below.
 | upstreamBytesReceived | Number of bytes received by the origin’s edge if the content isn’t cached. Example: `8304` |
 | upstreamBytesReceivedStr | List with all `upstreamBytesReceived` responses. |
 | upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
-| upstreamConnectTime | Time it takes for the edge to establish a connection with the origin in milliseconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **`0` in case of KeepAlive and `-` in case of cache.** |
-| upstreamHeaderTime | Time it takes for the edge to receive the response header from the origin in milliseconds. Example: `0.345`. **In case of cache, the response is `-`**. |
-| upstreamResponseTime | Time it takes for the edge to receive a default response from the origin in milliseconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`**. |
+| upstreamConnectTime | Time it takes for the edge to establish a connection with the origin, in seconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **Returns `0` for KeepAlive and `-` for cache** |
+| upstreamHeaderTime | Time it takes for the edge to receive the response header from the origin, in seconds. Example: `0.345`. **In case of cache, the response is `-`** |
+| upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`** |
 | upstreamStatus | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `-`**. |
 
 ---
@@ -306,7 +306,7 @@ The following datasets were discontinued. It's recommended to use the [new datas
 | remotePort | Port of the origin that generated the request. Example: `8080` |
 | requestLength | Request length, including request line, headers, and body. This field is the result of a sum. Example: `167` |
 | requestMethod | HTTP request method. Example: `GET` or `POST` |
-| requestTime | Request processing time elapsed since the first bytes were read from the client with resolution in milliseconds. This field is the result of a sum. Example: `1.19` |
+| requestTime | Request processing time, in seconds, since the first bytes were read from the client. This field is the result of a sum. Example: `0.234` |
 | requestUri | URI of the request made by the end user, without the host and protocol information and with arguments. Example: `/v1?v=bo%20dim` |
 | scheme | Request scheme. Example: `HTTP` or `HTTPS` |
 | sentHttpContentType | `Content-Type` header sent in the origin’s response. Example: `text/html; charset=UTF-8` |
@@ -318,9 +318,9 @@ The following datasets were discontinued. It's recommended to use the [new datas
 | upstreamBytesReceived | Number of bytes received by the origin’s edge if the content isn’t cached. Example: `8304` |
 | upstreamBytesReceivedStr | List with all `upstreamBytesReceived` responses. |
 | upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
-| upstreamConnectTime | Time it takes for the edge to establish a connection with the origin in milliseconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **`0` in case of KeepAlive and `-` in case of cache.** |
-| upstreamHeaderTime | Time it takes for the edge to receive the response header from the origin in milliseconds. Example: `0.345`. **In case of cache, the response is `-`**. |
-| upstreamResponseTime | Time it takes for the edge to receive a default response from the origin in milliseconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`**. |
+| upstreamConnectTime | Time it takes for the edge to establish a connection with the origin, in seconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **Returns `0` for KeepAlive and `-` for cache** |
+| upstreamHeaderTime | Time it takes for the edge to receive the response header from the origin, in seconds. Example: `0.345`. **In case of cache, the response is `-`** |
+| upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`** |
 | upstreamStatus | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `-`**. |
 
 ---