Real-Time Metrics GraphQL API Fields

Each GraphQL API dataset has specific fields that can be used when querying for data from that specific dataset. These fields are also used for the Real-Time Metrics interface on Azion Console.

See each available field and their descriptions next.


httpMetrics (Edge Applications, WAF)

Section titled httpMetrics (Edge Applications, WAF)
FieldDescription
bytesSentNumber of bytes sent to a client. This field is the result of a sum. Example: 191
configurationIdUnique Azion configuration identifier set on virtual host configuration file. Example: 1595368520
geolocCountryNameCountry name resolution based on client IP. Example: Canada
geolocRegionNameRegion/state name resolution based on client IP. Example: Parana
hostHost information sent on the request line. Stores: host name from the request line, or host name from the “Host” request header field, or the server name matching a request. Example: hello.myhost.net
proxyStatusHTTP error status code or origin when no response is obtained from the upstream. Example: 500. In case of cache, the response is -.
remoteAddressClassClass of the IP address of the origin that generated the request. Example: 44.192.0.0/11
requestLengthRequest length in bytes, including request line, headers, and body. This field is the result of a sum. Example: 167
requestMethodHTTP request method. Example: GET or POST.
requestTimeRequest 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
requestsTotal amount of requests in the aggregation being used. This field is the result of a sum. Example: 11
schemeRequest scheme. Example: HTTP or HTTPS.
sentHttpXOriginalImageSize“X-Original-Image-Size” header sent in the origin’s response. Used by IMS to inform original image size. This field is the result of a sum. Example: 987390
serverProtocolVersion of the request protocol. Example: HTTP/1.1, HTTP/2.0, HTTP/3.0
sourceLocPopLocation and PoP of the edge that received the request. Example: lax-bso
statusHTTP status code of the request. Example: 200
tsTimestamp of when the event was created. Example: 2022-10-20T10:10:10
upstreamBytesReceivedNumber of bytes received by the origin’s edge if the content isn’t cached. This field is the result of a sum. Example: 8304
upstreamCacheStatusStatus of the local edge cache. Can be: MISS, BYPASS, EXPIRED, STALE, UPDATING, REVALIDATED, HIT, or -
upstreamResponseTimeTime 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 -.
upstreamStatusHTTP 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 -.
wafBlockInforms whether the WAF blocked the action or not. 0 when action wasn’t blocked and 1 when action was blocked. When in Learning Mode, it won’t be blocked regardless of the return.
wafLearningInforms if WAF is in Learning mode. Returns 0 if it isn’t and 1 if it’s.

When a field is a result of any kind of calculation, such as a sum, they’re considered as calculated fields.

Calculated fieldDescription
bandwidthImagesProcessedSavedDataThe saved data bandwidth in bytes achieved with Images Processor through Azion services. Example: 1026730813
bandwidthMissedDataThe missed data bandwidth in bytes rate achieved through Azion services. Example: 3.76
bandwidthOffloadPercentage of the bandwidth that was offloaded through Azion services. Example: 85.23
bandwidthSavedDataThe saved data bandwidth rate in bytes achieved through Azion services. Example: 0.21
bandwidthTotalThe bandwidth rate in bytes achieved through Azion services. Example: 4.21
dataTransferredInSum of the request length in bytes. If the data wasn’t a cache hit, the request length is summed once more. Example: 1202
dataTransferredOutSum of the bytes sent. If the data wasn’t a cache hit, the upstream bytes sent is summed. Example: 6460
dataTransferredTotalValue of Data Transferred In + Data Transferred Out in bytes. Example: 766
edgeRequestsTotalTotal amount of all requests in the edge application. Example: 23
edgeRequestsTotalPerSecondTotal amount of requests per second in the edge application. Example: 0.00026
httpRequestsTotalTotal amount of requests using the HTTP protocol. Example: 10
httpsRequestsTotalTotal amount of requests using the HTTPS protocol. Example: 120
missedDataTotal amount of data that was missing and fetched from the origin. Example: 384
missedRequestsTotal amount of requests missed by using Azion services. Example: 5
missedRequestsPerSecondTotal amount of requests missed per second by using Azion services. Example: 0.00034
offloadPercentage of client data delivered by Azion, saving data. Example: 9.71
requestsHttpMethodGetTotal amount of requests with the HTTP method GET. Example: 18
requestsHttpMethodHeadTotal amount of requests with HTTP method HEAD. Example: 2
requestsHttpMethodOthersTotal amount of requests with others HTTP methods. Example: 3
requestsHttpMethodPostTotal amount of requests with the HTTP method POST. Example: 6
requestsOffloadedPercentage of client requests delivered by Azion. Example: 50
requestsPerSecondOffloadedPercentage of the requests per second that were offloaded through Azion services. Example: 10
requestsStatusCode200Total amount of requests with the HTTP 200 status code. Example: 45
requestsStatusCode204Total amount of requests with the HTTP 204 status code. Example: 20
requestsStatusCode206Total amount of requests with the HTTP 206 status code. Example: 30
requestsStatusCode2xxTotal amount of requests with other 2XX HTTP status codes. Example: 60
requestsStatusCode301Total amount of requests with the HTTP 301 status code. Example: 10
requestsStatusCode302Total amount of requests with the HTTP 302 status code. Example: 12
requestsStatusCode304Total amount of requests with the HTTP 304 status code. Example: 5
requestsStatusCode3xxTotal amount of requests with other 3XX HTTP status codes. Example: 30
requestsStatusCode400Total amount of requests with the HTTP 400 status code. Example: 24
requestsStatusCode403Total amount of requests with the HTTP 403 status code. Example: 14
requestsStatusCode404Total amount of requests with the HTTP 404 status code. Example: 35
requestsStatusCode4xxTotal amount of requests with other 4XX HTTP status codes. Example: 50
requestsStatusCode500Total amount of requests with the HTTP 500 status code. Example: 6
requestsStatusCode502Total amount of requests with the HTTP 502 status code. Example: 18
requestsStatusCode503Total amount of requests with the HTTP 503 status code. Example: 40
requestsStatusCode5xxTotal amount of requests with other 5XX HTTP status codes. Example: 100
savedDataTotal amount of data that was saved by using Azion services. Example: 8300
savedRequestsTotal amount of requests saved by using Azion services. Example: 18
savedRequestsPerSecondTotal amount of requests saved per second by using Azion services. Example: 11
wafRequestsAllowedTotal amount of requests allowed by WAF. Example: 10
wafRequestsBlockedTotal amount of requests blocked by WAF. Example: 4
wafRequestsOthersAttacksTotal amount of requests with Others attacks, not considering XSS, RFI, and SQL Injection threats. Example: 2
wafRequestsRfiAttacksTotal amount of requests with Remote File Inclusion (RFI) attack. Example: 5
wafRequestsSqlAttacksTotal amount of requests with SQL Injection attack. Example: 3
wafRequestsThreatWhen WAF is in learning mode, total number of requests identified as threats processed but not blocked by WAF. Example: 10
wafRequestsXssAttacksTotal amount of requests with Cross-site scripting (XSS) attack. Example: 1

tieredCacheMetrics (Tiered Cache)

Section titled tieredCacheMetrics (Tiered Cache)
FieldDescription
bytesSentNumber of bytes sent to a client. This field is the result of a sum. Example: 191
configurationIdUnique Azion configuration identifier set on virtual host configuration file. Example: 1595368520
hostHost information sent on the request line. Stores: host name from the request line, or host name from the “Host” request header field, or the server name matching a request. Example: hello.myhost.net
proxyStatusHTTP error status code or origin when no response is obtained from the upstream. Example: 520. In case of cache, the response is -.
remoteAddressClassClass of the IP address of the origin that generated the request. Example: 44.192.0.0/11
requestLengthRequest length in bytes, including request line, headers, and body. This field is the result of a sum. Example: 167
requestMethodHTTP request method. Example: GET or POST.
requestTimeRequest 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
requestsTotal amount of requests in the aggregation being used. This field is the result of a sum. Example: 11
schemeRequest scheme. Example: HTTP or HTTPS.
sourceLocPopLocation and PoP of the server that received the request. Example: lax-bso
statusHTTP status code of the request. Example: 200
tsTimestamp the event was created. Example: 2022-10-20T10:10:10
upstreamBytesReceivedNumber of bytes received by the origin’s edge if the content isn’t cached. This field is the result of a sum. Example: 8304
upstreamCacheStatusStatus of the local edge cache. Can be: MISS, BYPASS, EXPIRED, STALE, UPDATING, REVALIDATED, HIT, or -
upstreamResponseTimeTime 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 -.
upstreamStatusHTTP 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 -.

When a field is a result of any kind of calculation, such as a sum, they’re considered as calculated fields.

Calculated fieldDescription
dataTransferredInSum of the request length in bytes. If the data wasn’t a cache hit, the request length is summed once more. Example: 1202
dataTransferredOutSum of the bytes sent. If the data wasn’t a cache hit, the upstream bytes sent is summed. Example: 6460
dataTransferredTotalValue of Data Transferred In + Data Transferred Out in bytes. Example: 766
offloadPercentage of client data delivered by Azion, saving data. Example: 9.71

edgeFunctionsMetrics (Edge Functions)

Section titled edgeFunctionsMetrics (Edge Functions)
FieldDescription
computeTimeTotal execution time, in milliseconds, for the function during its processing. This field is the result of a sum. Example: 0
configurationIdUnique Azion configuration identifier set on virtual host configuration file. Example: 1595368520
edgeFunctionIdIdentification of your Edge Function. Example: 1321
edgeFunctionInstanceIdIdentification of your Edge Function Instance. Example: 10590
edgeFunctionsInstanceIdListList of edge functions instances that were invocated during the request. Example: 10728
functionLanguageLanguage used in the function. Example: javascript
initiatorTypeInitiator used in the function. Can be 1 (Edge Application) or 2 (Edge Firewall).
invocationsTotal amount of an invocation. This field is the result of a sum. Example: 8
sourceLocPopLocation and PoP of the server that received the request. Example: lax-bso
tsTimestamp of when the event was created. Example: 2022-10-20T10:10:10

When a field is a result of any kind of calculation, such as a sum, they’re considered as calculated fields.

Calculated fieldDescription
edgeApplicationInvocationsTotal amount of invocations of a function from an edge application. Example: 50
edgeFirewallInvocationsTotal amount of invocations of a function from an edge firewall. Example: 30

imageProcessedMetrics (Image Processor)

Section titled imageProcessedMetrics (Image Processor)
FieldDescription
bytesSentNumber of bytes sent to a client. This field is the result of a sum. Example: 191
configurationIdUnique Azion configuration identifier set on virtual host configuration file. Example: 1595368520
hostHost information sent on the request line. Stores: host name from the request line, or host name from the “Host” request header field, or the server name matching a request. Example: hello.myhost.net
remoteAddressClassClass of the IP address of the origin that generated the request. Example: 44.192.0.0/11
requestMethodHTTP request method. Example: GET or POST.
requestTimeRequest 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
requestsTotal amount of requests in the aggregation being used. This field is the result of a sum. Example: 11
schemeRequest scheme. Example: HTTP or HTTPS.
sourceLocPopLocation and PoP of the server that received the request. Example: lax-bso
statusHTTP status code of the request. Example: 200
tsTimestamp of when the event was created. Example: 2022-10-20T10:10:10
upstreamCacheStatusStatus of the local edge cache. Can be: MISS, BYPASS, EXPIRED, STALE, UPDATING, REVALIDATED, HIT, or -
upstreamResponseTimeTime 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 -.
upstreamStatusHTTP 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 -.

edgeDnsQueriesMetrics (Edge DNS)

Section titled edgeDnsQueriesMetrics (Edge DNS)
FieldDescription
qtypeDefinition of the type of record that’ll be used. Example: PTR, A, AAAA, HTTPS, NS, SRV
requestsTotal amount of requests in the aggregation being used. This field is the result of a sum. Example: 11
sourceLocPopLocation and PoP of the server that received the request. Example: lax-bso
tsTimestamp of when the event was created. Example: 2022-10-20T10:10:10
zoneIdUnique identifier of the Edge DNS zone. Example: 1340

dataStreamedMetrics (Data Stream)

Section titled dataStreamedMetrics (Data Stream)
FieldDescription
configurationIdUnique Azion configuration identifier set on virtual host configuration file. Example: 1595368520
dataStreamedTotal amount of data streamed in bytes to the configured endpoint. This field is the result of a sum. Example: 1270
endpointTypeType of endpoint used in the configured Data Stream. Example: S3
requestsTotal amount of requests in the aggregation being used. This field is the result of a sum. Example: 11
sourceLocPopLocation and PoP of the server that received the request. Example: lax-bso
streamedLinesTotal amount of lines streamed to the configured endpoint. Maximum value of 2000. This field is the result of a sum. Example: 837
tsTimestamp of when the event was created. Example: 2022-10-20T10:10:10

The following datasets were discontinued. It’s recommended to use the new datasets which replaced them.

FieldDescription
bytesSentNumber of bytes sent to a client. This field is the result of a sum. Example: 191
configurationIdUnique Azion configuration identifier set on virtual host configuration file. Example: 1595368520
hostHost information sent on the request line. Stores: host name from the request line, or host name from the “Host” request header field, or the server name matching a request. Example: hello.myhost.net
proxyStatusHTTP error status code or origin when no response is obtained from the upstream. Example: 520. In case of cache, the response is -.
remoteAddressClassClass of the IP address of the origin that generated the request. Example: 44.192.0.0/11
requestLengthRequest length in bytes, including request line, headers, and body. This field is the result of a sum. Example: 167
requestMethodHTTP request method. Example: GET or POST.
requestTimeRequest 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
requestsTotal amount of requests in the aggregation being used. This field is the result of a sum. Example: 11
schemeRequest scheme. Example: HTTP or HTTPS.
sourceLocPopLocation and PoP of the server that received the request. Example: lax-bso
statusHTTP status code of the request. Example: 200
tsTimestamp the event was created. Example: 2022-10-20T10:10:10
upstreamBytesReceivedNumber of bytes received by the origin’s edge if the content isn’t cached. This field is the result of a sum. Example: 8304
upstreamCacheStatusStatus of the local edge cache. Can be: MISS, BYPASS, EXPIRED, STALE, UPDATING, REVALIDATED, HIT, or -
upstreamResponseTimeTime 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 -.
upstreamStatusHTTP 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 -.

When a field is a result of any kind of calculation, such as a sum, they’re considered as calculated fields.

Calculated fieldDescription
dataTransferredInSum of the request length in bytes. If the data wasn’t a cache hit, the request length is summed once more. Example: 1202
dataTransferredOutSum of the bytes sent. If the data wasn’t a cache hit, the upstream bytes sent is summed. Example: 6460
dataTransferredTotalValue of Data Transferred In + Data Transferred Out in bytes. Example: 766
offloadPercentage of client data delivered by Azion, saving data. Example: 9.71

FieldDescription
qtypeDefinition of the type of record that’ll be used. Example: PTR, A, AAAA, HTTPS, NS, SRV
requestsTotal amount of requests in the aggregation being used. This field is the result of a sum. Example: 11
sourceLocPopLocation and PoP of the server that received the request. Example: lax-bso
tsTimestamp of when the event was created. Example: 2022-10-20T10:10:10
zoneIDUnique identifier of the Edge DNS zone. Example: 1340

Contributors