aziontech · rodrigomaria · Mar 20, 2026
@@ -45,7 +45,7 @@ See each available field and their descriptions below.
 
 ---
 
-## cellsConsoleEvents (Azion Runtime)
+## functionConsoleEvents (previous cellsConsoleEvents) (Azion Runtime)
 
 | Field | Description |
 | ----- | ----------- |
@@ -75,23 +75,23 @@ See each available field and their descriptions below.
 
 ---
 
-## edgeFunctionsEvents (Functions)
+## functionEvents (previous edgeFunctionsEvents) (Functions)
 
 | Field | Description |
 | ----- | ----------- |
 | configurationId | Unique Azion configuration identifier set on virtual host configuration file. Example: `1595368520` |
-| edgeFunctionsInstanceIdList | List of functions instances that were invoked during the request. Example: `10728` |
-| edgeFunctionsInitiatorTypeList | List of initiators used in the function separated by `;`. Can be `1` (Applications) or `2` (Firewall). |
-| edgeFunctionsList | List of 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 function. Example: `1321` |
-| edgeFunctionsTime | Total execution time, in seconds, for the function during its processing. This field is the result of a sum. Example: `0.021` |
+| functionsInstanceIdList (previous edgeFunctionsInstanceIdList) | List of functions instances that were invoked during the request. Example: `10728` |
+| functionsInitiatorTypeList (previous edgeFunctionsInitiatorTypeList) | List of initiators used in the function separated by `;`. Can be `1` (Applications) or `2` (Firewall). |
+| functionsList (previous edgeFunctionsList) | List of 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` |
+| functionsSolutionId (previous edgeFunctionsSolutionId) | Identifier of your function. Example: `1321` |
+| functionsTime (previous 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` |
 
 ---
 
-## httpEvents (Applications, WAF)
+## workloadEvents (previous httpEvents) (Applications, WAF)
 
 | Field | Description |
 | ----- | ----------- |

@@ -29,8 +29,11 @@ Azion **GraphQL API** uses defined datasets to indicate what requests you can ru
 Find each available dataset and what they request next.
 
 :::note
-Four datasets are deprecated and were replaced by other datsets:
+Seven datasets are deprecated and were replaced by other datsets:
 
+- **cellsConsoleEvents** for **functionConsoleEvents**
+- **edgeFunctionEvents** for **functionEvents**
+- **httpEvents** for **workloadEvents**
 - **idnsQueriesMetrics** for **edgeDnsQueriesMetrics**
 - **idnsQueriesEvents** for **edgeDnsQueriesEvents**
 - **l2CacheMetrics** for **tieredCacheMetrics**
@@ -59,10 +62,10 @@ Four datasets are deprecated and were replaced by other datsets:
 | Dataset | Description |
 | ------- | ----------- |
 | activityHistoryEvents | Events logs from an account on Azion Console regarding activities registered on [Activity History](/en/documentation/products/accounts/activity-history/). It stores data for *2 years* and exhibits data starting from *September 22nd, 2023*. |
-| cellsConsoleEvents |  Events logs from applications using [Azion Runtime](/en/documentation/runtime/overview/) returned by the Cells Console. |
+| functionConsoleEvents |  Events logs from applications using [Azion Runtime](/en/documentation/runtime/overview/) returned by the Cells Console. |
 | dataStreamedEvents | Sent events of data by [Data Stream](/en/documentation/products/observe/data-stream/) to the clients' endpoint. |
-| edgeFunctionsEvents | Events executed by [Functions](/en/documentation/products/build/applications/functions/). |
-| httpEvents | Request events registered by [Applications](/en/documentation/products/build/applications/) and [Firewall](/en/documentation/products/secure/firewall/). |
+| functionEvents | Events executed by [Functions](/en/documentation/products/build/applications/functions/). |
+| workloadEvents | Request events registered by [Applications](/en/documentation/products/build/applications/) and [Firewall](/en/documentation/products/secure/firewall/). |
 | edgeDnsQueriesEvents | Query events performed on [Edge DNS](/en/documentation/products/secure/edge-dns/). |
 | imagesProcessedEvents |  Image processing events by [Image Processor](/en/documentation/products/build/applications/image-processor/). |
 | tieredCacheEvents | Request events registered by [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/). |

@@ -38,7 +38,7 @@ Here's an example of a raw Real-Time Events GraphQL query:
 
 ```graphql
 query HttpQuery {
-  httpEvents(
+  workloadEvents(
     limit: 10,
     filter: {
       tsRange: {begin:"2023-02-14T10:10:10", end:"2023-02-15T10:10:10"}
@@ -59,7 +59,7 @@ And the response to the query:
 ```json
 {
   "data": {
-    "httpEvents": [
+    "workloadEvents": [
       {
         "ts": "2023-08-08T10:10:10Z",
         "remoteAddress": "xx.xx.xxx.xxx",
@@ -104,7 +104,7 @@ For example, to perform a **NOT LIKE** query, use the `not` operator with the `L
 
 ```graphql
 query HttpQuery {
-  httpEvents(
+  workloadEvents(
     limit: 10,
     filter: {
       tsRange: {begin:"2023-02-14T10:10:10", end:"2023-02-15T10:10:10"},

@@ -68,7 +68,7 @@ Then, on Postman’s GraphQL request code box, add the following **HTTP Query**,
 
 ```graphql
 query HttpQuery {
-  httpEvents(
+  workloadEvents(
     limit: 10,
     filter: {
       tsRange: {begin:"2023-02-14T10:10:10", end:"2023-02-15T10:10:10"}
@@ -98,7 +98,7 @@ Send your request. You’ll receive a response similar to this:
 ```json
 {
   "data": {
-    "httpEvents": [
+    "workloadEvents": [
       {
         "ts": "2023-02-15T17:52:16Z",
         "remoteAddress": "00.00.000.00",

@@ -14,7 +14,7 @@ Then, on Postman's GraphQL request code box, add the following query, modifying
 
 ```graphql
 query ConsoleLog {
-  cellsConsoleEvents(
+  functionConsoleEvents(
     limit: 10,
     filter: {
       tsRange: {begin:"2023-02-01T10:10:10", end:"2023-06-15T10:10:10"}
@@ -39,7 +39,7 @@ Send your request. You'll receive a response similar to this:
 ```json
 {
     "data": {
-        "cellsConsoleEvents": [
+        "functionConsoleEvents": [
             {
                 "ts": "2023-06-12T17:09:54Z",
                 "solutionId": "1531300483",

@@ -122,14 +122,14 @@ Follow the steps described in [How to use a pre-built dashboard with the Azion p
 						"annotationText": "",
 						"annotationTitle": "",
 						"constant": 6.5,
-						"dataPath": "httpEvents",
+						"dataPath": "workloadEvents",
 						"datasource": {
 							"type": "fifemon-graphql-datasource",
 							"uid": "loKOM5K4k"
 						},
 						"endTimePath": "endTime",
 						"groupBy": "requestUri",
-						"queryText": "query {\n httpEvents(\n limit: 10,\n filter: {\n\ttsRange: { begin: \"${__from:date:iso}\", end: \"${__to:date:iso}\" }\n\t \n\t\t},\n aggregate: {count: host} \n groupBy: [requestUri]\n #orderBy: [count_DESC]\n )\n {\n requestUri\n #status\n count\n \n }\n}",
+						"queryText": "query {\n workloadEvents(\n limit: 10,\n filter: {\n\ttsRange: { begin: \"${__from:date:iso}\", end: \"${__to:date:iso}\" }\n\t \n\t\t},\n aggregate: {count: host} \n groupBy: [requestUri]\n #orderBy: [count_DESC]\n )\n {\n requestUri\n #status\n count\n \n }\n}",
 						"refId": "A",
 						"timeFormat": "",
 						"timePath": "tsRange"
@@ -194,14 +194,14 @@ Follow the steps described in [How to use a pre-built dashboard with the Azion p
 						"annotationText": "",
 						"annotationTitle": "",
 						"constant": 6.5,
-						"dataPath": "httpEvents",
+						"dataPath": "workloadEvents",
 						"datasource": {
 							"type": "fifemon-graphql-datasource",
 							"uid": "loKOM5K4k"
 						},
 						"endTimePath": "endTime",
 						"groupBy": "httpUserAgent",
-						"queryText": "query {\n httpEvents(\n limit: 10,\n filter: {\n\ttsRange: { begin: \"${__from:date:iso}\", end: \"${__to:date:iso}\" }\n\t \n\t\t},\n aggregate: {count: host} \n groupBy: [httpUserAgent]\n #orderBy: [count_DESC]\n )\n {\n httpUserAgent\n #status\n count\n \n }\n}",
+						"queryText": "query {\n workloadEvents(\n limit: 10,\n filter: {\n\ttsRange: { begin: \"${__from:date:iso}\", end: \"${__to:date:iso}\" }\n\t \n\t\t},\n aggregate: {count: host} \n groupBy: [httpUserAgent]\n #orderBy: [count_DESC]\n )\n {\n httpUserAgent\n #status\n count\n \n }\n}",
 						"refId": "A",
 						"timeFormat": "",
 						"timePath": "tsRange"
@@ -266,14 +266,14 @@ Follow the steps described in [How to use a pre-built dashboard with the Azion p
 						"annotationText": "",
 						"annotationTitle": "",
 						"constant": 6.5,
-						"dataPath": "httpEvents",
+						"dataPath": "workloadEvents",
 						"datasource": {
 							"type": "fifemon-graphql-datasource",
 							"uid": "loKOM5K4k"
 						},
 						"endTimePath": "endTime",
 						"groupBy": "host",
-						"queryText": "query {\n httpEvents(\n limit: 10,\n filter: {\n\ttsRange: { begin: \"${__from:date:iso}\", end: \"${__to:date:iso}\" }\n\t \n\t\t},\n aggregate: {count: host} \n groupBy: [host,status]\n #orderBy: [count_DESC]\n )\n {\n host\n #status\n count\n \n }\n}",
+						"queryText": "query {\n workloadEvents(\n limit: 10,\n filter: {\n\ttsRange: { begin: \"${__from:date:iso}\", end: \"${__to:date:iso}\" }\n\t \n\t\t},\n aggregate: {count: host} \n groupBy: [host,status]\n #orderBy: [count_DESC]\n )\n {\n host\n #status\n count\n \n }\n}",
 						"refId": "A",
 						"timeFormat": "",
 						"timePath": "tsRange"

@@ -19,7 +19,7 @@ Then, on Postman’s GraphQL request code box, add the following **Top X Query**
 
 ```graphql
 query EventsTopUri {
- httpEvents(
+ workloadEvents(
    limit: 5,
    filter: {
      tsRange: {begin:"2022-11-20T10:10:10", end:"2022-11-27T10:10:10"}
@@ -52,7 +52,7 @@ Send your request. You’ll receive a response similar to this:
 ```json
 {
    "data": {
-       "httpEvents": [
+       "workloadEvents": [
            {
                "requestUri": "/requests/images",
                "count": 610081

@@ -7,7 +7,7 @@ permalink: /documentation/products/guides/query-top-ips-attack-traffic-with-grap
 menu_namespace: graphqlMenu
 ---
 
-You can use information from the `httpEvents` dataset to monitor traffic patterns, detect anomalies, and analyze potential threats. This guide explains how to filter the 5 IPs that generated the most requests identified by the WAF as attacks.
+You can use information from the `workloadEvents` dataset to monitor traffic patterns, detect anomalies, and analyze potential threats. This guide explains how to filter the 5 IPs that generated the most requests identified by the WAF as attacks.
 
 ---
 
@@ -21,7 +21,7 @@ To query the Top 5 IPs generating attack traffic, according to the WAF, proceed
 
 ```graphql
 query TOP5IPsWAFRequests {
-  httpEvents(
+  workloadEvents(
     limit: 5
     filter: {
       tsRange: {
@@ -67,7 +67,7 @@ This example retrieves data for `remoteAddress` and the total (count) of request
 ```graphql
 {
   "data": {
-    "httpEvents": [
+    "workloadEvents": [
       {
         "remoteAddress": "123.456.789.123",
         "wafAttackFamily": "$SQL, $XSS",

@@ -115,7 +115,7 @@ This query fetches the 10 most recent Console events containing a specific log l
 
 ```graphql
 query getConsoleEvents {
-  cellsConsoleEvents(
+  functionConsoleEvents(
     limit: 10,
     filter: {
       tsRange: {begin: "2024-09-28T12:00:00", end: "2024-09-28T13:00:00"},

@@ -145,7 +145,7 @@ You can also test this query to filter the IPs that generated the most requests
 
 ```graphql
 query TOP5IPsWAFRequests {
-  httpEvents(
+  workloadEvents(
     limit: 5
     filter: {
       tsRange: {

@@ -36,7 +36,7 @@ Begin your investigation with a query focused on the countries making requests.
 
 ```graphql
 query requestsInvestigationCountries {
-  httpEvents(
+  workloadEvents(
     limit: 100,
     filter: {
       tsRange: {begin:"2024-03-20T10:10:10", end:"2024-03-27T10:10:10"}
@@ -64,7 +64,7 @@ query requestsInvestigationCountries {
 ```json
 {
   "data": {
-    "httpEvents": [
+    "workloadEvents": [
       {
         "geolocCountryName": "Brazil",
         "host": "myhost.com",
@@ -139,7 +139,7 @@ Now, in the query response for the example of this guide, the requests coming fr
 
 ```graphql
 query requestsInvestigationStatus {
-  httpEvents(
+  workloadEvents(
     limit: 100,
     filter: {
       tsRange: {begin:"2024-03-20T10:10:10", end:"2024-03-27T10:10:10"}
@@ -173,7 +173,7 @@ Next, you'll investigate the `User-Agent` header being used in the requests from
 
 ```graphql
 query requestsInvestigationUserAgent {
-  httpEvents(
+  workloadEvents(
     limit: 100,
     filter: {
       tsRange: {begin:"2024-03-20T10:10:10", end:"2024-03-27T10:10:10"}
@@ -199,7 +199,7 @@ You'll receive a response similar to:
 ```json
 {
   "data": {
-    "httpEvents": [
+    "workloadEvents": [
       {
         "geolocCountryName": "Brazil",
         "status": 403,

@@ -37,7 +37,7 @@ Veja um exemplo de uma query de dados brutos da GraphQL do Real-Time Events:
 
 ```graphql
 query HttpQuery {
-  httpEvents(
+  workloadEvents(
     limit: 10,
     filter: {
       tsRange: {begin:"2023-02-14T10:10:10", end:"2023-02-15T10:10:10"}
@@ -58,7 +58,7 @@ E a resposta à consulta:
 ```json
 {
   "data": {
-    "httpEvents": [
+    "workloadEvents": [
       {
         "ts": "2023-08-08T10:10:10Z",
         "remoteAddress": "xx.xx.xxx.xxx",
@@ -103,7 +103,7 @@ Por exemplo, para realizar uma consulta **NOT LIKE**, você pode usar o operador
 
 ```graphql
 query HttpQuery {
-  httpEvents(
+  workloadEvents(
     limit: 10,
     filter: {
       tsRange: {begin:"2023-02-14T10:10:10", end:"2023-02-15T10:10:10"},

@@ -44,7 +44,7 @@ Veja cada campo disponível e suas descrições abaixo.
 
 ---
 
-## cellsConsoleEvents (Azion Runtime)
+## functionConsoleEvents (anteriormente cellsConsoleEvents) (Azion Runtime)
 
 | Campo | Descrição |
 | ----- | --------- |
@@ -76,24 +76,24 @@ Veja cada campo disponível e suas descrições abaixo.
 
 ---
 
-## edgeFunctionsEvents (Functions)
+## functionEvents (anteriormente edgeFunctionsEvents) (Functions)
 
 | Campo | Descrição |
 | ----- | --------- |
 | configurationId | Identificador único de configuração na Azion definido no arquivo de configuração do virtual host. Exemplo: `1595368520` |
-| edgeFunctionsInstanceIdList | Lista de functions instances que foram invocadas durante a solicitação. Exemplo: `10728` |
-| edgeFunctionsInitiatorTypeList | Lista de initiators utilizados na function, separados por`;`. Pode ser `1` (Applications) ou `2` (Firewall). |
-| edgeFunctionsList | Lista de functions que foram invocadas durante a requisição, em ordem. A ordem começa da esquerda para a direita, o que significa que as funções à esquerda foram invocadas primeiro. Exemplo: `3324;43` |
-| edgeFunctionsSolutionId | Identificador da function. Exemplo: `1321` |
-| edgeFunctionsTime | Tempo total de execução, em segundos, da function durante seu processamento. Este campo é o resultado de uma soma. Exemplo: `0.021` |
+| functionsInstanceIdList (anteriormente edgeFunctionsInstanceIdList) | Lista de functions instances que foram invocadas durante a solicitação. Exemplo: `10728` |
+| functionsInitiatorTypeList (anteriormente edgeFunctionsInitiatorTypeList) | Lista de initiators utilizados na function, separados por`;`. Pode ser `1` (Applications) ou `2` (Firewall). |
+| functionsList (anteriormente edgeFunctionsList) | Lista de functions que foram invocadas durante a requisição, em ordem. A ordem começa da esquerda para a direita, o que significa que as funções à esquerda foram invocadas primeiro. Exemplo: `3324;43` |
+| functionsSolutionId (anteriormente edgeFunctionsSolutionId) | Identificador da function. Exemplo: `1321` |
+| functionsTime (previous edgeFunctionsTime) | Tempo total de execução, em segundos, da function durante seu processamento. Este campo é o resultado de uma soma. Exemplo: `0.021` |
 | functionLanguage | Linguagem utilizada na function. Exemplo: `javascript` |
 | source | Servidor que gerou a linha do log. Exemplo: `edg-fln-ggn001p` |
 | ts | Data e hora de quando o evento foi criado. Exemplo: `2022-10-20T10:10:10` |
 | virtualHostId | Identificador disponível no Azion Console. Definido no arquivo de configuração do virtual host. Exemplo: `2410001a` |
 
 ---
 
-## httpEvents (Applications, WAF)
+## workloadEvents (anteriormente httpEvents)  (Applications, WAF)
 
 | Campo | Descrição |
 | ----- | --------- |

@@ -27,8 +27,11 @@ A **API GraphQL** da Azion usa conjuntos de dados para indicar quais requisiçõ
 Veja cada um dos conjuntos de dados disponíveis e o que eles buscam.
 
 :::note
-Quatro conjuntos de dados foram descontinuados e substituiídos por outros:
+Sete conjuntos de dados foram descontinuados e substituídos por outros:
 
+- **cellsConsoleEvents** por **functionConsoleEvents**
+- **edgeFunctionEvents** por **functionEvents**
+- **httpEvents** por **workloadEvents**
 - **idnsQueriesMetrics** por **edgeDnsQueriesMetrics**
 - **idnsQueriesEvents** por **edgeDnsQueriesEvents**
 - **l2CacheMetrics** por **tieredCacheMetrics**
@@ -57,10 +60,10 @@ Quatro conjuntos de dados foram descontinuados e substituiídos por outros:
 | Conjunto de dados | Descrição |
 | ----------------- | --------- |
 | activityHistoryEvents | Logs de eventos de uma conta no Azion Console relacionados às atividades registradas no [Activity History](/pt-br/documentacao/produtos/gestao-de-contas/activity-history/). Armazena dados por *2 anos* e exibe dados a partir de *22 de setembro de 2023*. |
-| cellsConsoleEvents | Logs de eventos das aplicações usando o [Azion Runtime](/pt-br/documentacao/runtime/visao-geral/) retornados pelo Cells Console. |
+| functionConsoleEvents | Logs de eventos das aplicações usando o [Azion Runtime](/pt-br/documentacao/runtime/visao-geral/) retornados pelo Cells Console. |
 | dataStreamedEvents | Registros de envio de dados do [Data Stream](/pt-br/documentacao/produtos/observe/data-stream/) para o endpoint do cliente. |
-| edgeFunctionsEvents | Eventos de execução do [Functions](/pt-br/documentacao/produtos/build/applications/functions/). |
-| httpEvents | Eventos de requisições registradas pelo [Applications](/pt-br/documentacao/produtos/build/applications/) e [Firewall](/pt-br/documentacao/produtos/secure/firewall/). |
+| functionEvents | Eventos de execução do [Functions](/pt-br/documentacao/produtos/build/applications/functions/). |
+| workloadEvents | Eventos de requisições registradas pelo [Applications](/pt-br/documentacao/produtos/build/applications/) e [Firewall](/pt-br/documentacao/produtos/secure/firewall/). |
 | idnsQueriesEvents | Eventos de consultas realizadas no [Edge DNS](/pt-br/documentacao/produtos/secure/edge-dns/). |
 | imagesProcessedEvents | Eventos de processamento de imagens do [Image Processor](/pt-br/documentacao/produtos/build/applications/image-processor/). |
 | l2CacheEvents | Eventos de requisições registradas pelo [Tiered Cache](/pt-br/documentacao/produtos/build/applications/cache/tiered-cache/). |