diff --git a/src/content/docs/en/pages/devtools/api-graphql/queries/queries.mdx b/src/content/docs/en/pages/devtools/api-graphql/queries/queries.mdx index 338c6fdcac..04ef72256e 100644 --- a/src/content/docs/en/pages/devtools/api-graphql/queries/queries.mdx +++ b/src/content/docs/en/pages/devtools/api-graphql/queries/queries.mdx @@ -100,6 +100,27 @@ To query raw data, it's *mandatory* to inform: - A time range interval for all datasets, using either **tsRange** or **tsGt** + **tsLt**. - Which consulted data should be exhibited. On the presented example, the **ts**, **remoteAddress**, **requestUri**, and **stacktrace** fields were used. +For example, to perform a **NOT LIKE** query, you can use the `Ne` operator combined with the `Like` or `Ilike` operators to filter out entries that match a certain pattern. Here's an example: + +```graphql +query HttpQuery { + httpEvents( + limit: 10, + filter: { + tsRange: {begin:"2023-02-14T10:10:10", end:"2023-02-15T10:10:10"}, + requestUriNe: "%/verify%" + } + orderBy: [ts_ASC] + ) + { + ts + remoteAddress + requestUri + stacktrace + } +} +``` + :::tip You can also use the **Top X query** feature with the Real-Time Events GraphQL API. It helps to visualize how resources and tools are being used and provide a more detailed analysis of certain conditions that are either more or less commonly used. For example, you can query for “Top 10 Hosts” or “Top 10 Status Codes”. @@ -380,9 +401,7 @@ Depending on the [type of field of a dataset](/en/documentation/devtools/graphql | String | `Eq`, `Ne`, `Like`, `Ilike`, `In`, `NotIn`, `IsNull` | | Integer, Float, DateTime | `Eq`, `Lt`, `Lte`, `Gt`, `Gte`, `Ne`, `In`, `NotIn`, `IsNull`, `Range` | - Discover the essential role of operators in GraphQL queries. Watch the video below:
- +
- diff --git a/src/content/docs/en/pages/guides/edge-application/ea-enforce-hls.mdx b/src/content/docs/en/pages/guides/edge-application/ea-enforce-hls.mdx index f40fa743c4..bf7a683609 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-enforce-hls.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-enforce-hls.mdx @@ -14,7 +14,7 @@ import InterfaceNote from '~/includes/snippets/InterfaceNote/en/snippet.mdx' -Azion Edge Platform allows you to [deliver live streaming content in HLS format](https://www.azion.com/en/solutions/live-streaming-delivery/), being able to easily self-provision and configure your cache policies. This guide covers the step-by-step to enforce HLS cache, managing chunks and playlists caching, and setting up rules engines rules. +Azion Edge Platform allows you to [deliver live streaming content in HLS format](https://www.azion.com/en/solutions/live-streaming-delivery/), being able to easily self-provision and configure your cache policies. This guide covers the step-by-step to enforce HLS cache, manage chunks and playlists caching, set up rules engines rules, and utilize Azion Edge Storage for optimal video delivery. --- @@ -23,6 +23,7 @@ Azion Edge Platform allows you to [deliver live streaming content in HLS format] - An existing Azion edge application, or [create a new one](/en/documentation/products/guides/build/build-an-application/). - [A domain associated with the edge application](/en/documentation/products/guides/configure-a-domain/). - [Tiered Cache enabled](/en/documentation/products/guides/billing-and-subscriptions/) in your account. +- Access to [Azion Edge Storage](/en/documentation/products/store/edge-storage/) for storing video content. --- @@ -34,7 +35,7 @@ In this example, an edge application and a domain linked to it has been previous ### Creating a cache policy for the chunks -First, you must to create a cache policy for the chunks: +First, you must create a cache policy for the chunks: CLI @@ -47,7 +48,7 @@ First, you must to create a cache policy for the chunks: 3. Enable Tiered Cache for your application: `$ azion update edge-application --application-id 1234 --l2-caching true` 4. Create an origin: `$ azion create origin --application-id 1234 --name "origin-edge" --origin-type single_origin --addresses "example.com" --host-header "example.com"` 5. Configure the cache policy for the chunks: `$ azion create cache-setting --application-id 1234 --name "chunks-policy" --browser-cache-settings "override" --browser-cache-settings-maximum-ttl 0 --cdn-cache-settings "override" --cnd-cache-settings-maximum-ttl 60` -- Define **Advanced Cache Key** behavoirs according to your needs. Check the optional flags for the [create command](/en/documentation/devtools/cli/create/#optional-flags-3). +- Define **Advanced Cache Key** behaviors according to your needs. Check the optional flags for the [create command](/en/documentation/devtools/cli/create/#optional-flags-3). - The recommendation is selecting **Content does not vary**, for **Query String** and/or **Cookies**, according to your needs. @@ -92,7 +93,7 @@ First, you must to create a cache policy for the chunks: Now configure the cache policy for the playlist: `$ azion create cache-setting --application-id 1234 --name "playlist-policy" --browser-cache-settings "override" --browser-cache-settings-maximum-ttl 0 --cdn-cache-settings "override" --cnd-cache-settings-maximum-ttl 5` -- Define **Advanced Cache Key** behavoirs according to your needs. Check the optional flags for the [create command](/en/documentation/devtools/cli/create/#optional-flags-3). +- Define **Advanced Cache Key** behaviors according to your needs. Check the optional flags for the [create command](/en/documentation/devtools/cli/create/#optional-flags-3). - The recommendation is selecting **Content does not vary**, for **Query String** and/or **Cookies**, according to your needs. @@ -126,6 +127,14 @@ Still on the **Cache Settings** tab: Read more about setting up [cache settings](/en/documentation/products/build/edge-application/cache-settings/) for your edge applications. ::: +### Utilizing Azion Edge Storage for HLS video delivery + +To deliver MP4 videos using HLS and Azion Edge Storage: + +1. Upload your MP4 video files to Azion Edge Storage. +2. Configure your encoder to convert MP4 files to HLS format and point to Azion Edge Storage as the origin. +3. Follow the cache policy setup steps outlined above to ensure efficient video delivery. + ### Creating Rules Engine rules @@ -238,5 +247,3 @@ Go to the [Rules Engine for Edge Application](/en/documentation/products/build/e ::: - - diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/web-application-firewall/custom-allowed-rule.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/web-application-firewall/custom-allowed-rule.mdx index 320824e48f..01b5db3aac 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/web-application-firewall/custom-allowed-rule.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/web-application-firewall/custom-allowed-rule.mdx @@ -92,7 +92,4 @@ See the list of all available internal rules below: | 1402 | Possible trick to evade protection: encoded chars `%20-%3F` found in Body, Path, Query String or Cookies. | | 1500 | Possible File Upload attempt: `asp/php` or `.ph`, `.asp`, `.ht` found in filename in a multipart POST containing a file. | - - - - + diff --git a/src/content/docs/pt-br/pages/devtools/api-graphql/queries/queries-gql.mdx b/src/content/docs/pt-br/pages/devtools/api-graphql/queries/queries-gql.mdx index 3d169b2dff..2ce0c44569 100644 --- a/src/content/docs/pt-br/pages/devtools/api-graphql/queries/queries-gql.mdx +++ b/src/content/docs/pt-br/pages/devtools/api-graphql/queries/queries-gql.mdx @@ -99,6 +99,27 @@ Para consultar dados brutos, é *obrigatório* informar: - Um intervalo de tempo para todos os conjuntos de dados, utilizando **tsRange** ou **tsGt** + **tsLt**. - Quais dados consultados devem ser exibidos. No exemplo apresentado, os campos **ts**, **remoteAddress**, **requestUri** e **stacktrace** foram usados. +Por exemplo, para realizar uma consulta **NOT LIKE**, você pode usar o operador `Ne` combinado com os operadores `Like` ou `Ilike` para filtrar entradas que correspondem a um determinado padrão. Aqui está um exemplo: + +```graphql +query HttpQuery { + httpEvents( + limit: 10, + filter: { + tsRange: {begin:"2023-02-14T10:10:10", end:"2023-02-15T10:10:10"}, + requestUriNe: "%/verify%" + } + orderBy: [ts_ASC] + ) + { + ts + remoteAddress + requestUri + stacktrace + } +} +``` + :::tip[dica] Você também pode utilizar o recurso **Top X query** com a API GraphQL do Real-Time Events. Ela tem a finalidade de visualizar o uso de recursos e ferramentas e ter uma visão detalhada sobre determinadas condições que são mais ou menos usadas. Por exemplo, você pode consultar os “Top 10 Hosts” ou os “Top 10 Status Codes”. @@ -378,8 +399,3 @@ Dependendo do [tipo de campo de um conjunto de dados](/pt-br/documentacao/devtoo | ------------- | -------------------- | | String | `Eq`, `Ne`, `Like`, `Ilike`, `In`, `NotIn`, `IsNull` | | Integer, Float, DateTime | `Eq`, `Lt`, `Lte`, `Gt`, `Gte`, `Ne`, `In`, `NotIn`, `IsNull`, `Range` | - - - ---- - diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-enforce-hls.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-enforce-hls.mdx index 387fac4184..75a5291462 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-enforce-hls.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-enforce-hls.mdx @@ -14,7 +14,7 @@ import InterfaceNote from '~/includes/snippets/InterfaceNote/pt/snippet.mdx' -A Plataforma de Edge da Azion permite que você [entregue conteúdo de streaming ao vivo no formato HLS](https://www.azion.com/pt-br/solucoes/live-streaming/), capacitando-lhe a autoprovisionar e configurar suas política de cache facilmente. Este guia abrange o passo a passo para implementar o cache HLS, gerenciando o cache de chunks e playlists e configurando regras no Rules Engine. +A Plataforma de Edge da Azion permite que você [entregue conteúdo de streaming ao vivo no formato HLS](https://www.azion.com/pt-br/solucoes/live-streaming/), capacitando-lhe a autoprovisionar e configurar suas política de cache facilmente. Este guia abrange o passo a passo para implementar o cache HLS, gerenciar o cache de chunks e playlists, configurar regras no Rules Engine e utilizar o Edge Storage para uma entrega de vídeo otimizada. --- @@ -23,6 +23,7 @@ A Plataforma de Edge da Azion permite que você [entregue conteúdo de streaming - Uma edge application existente na Azion, ou [crie uma nova](/pt-br/documentacao/produtos/guias/build/criar-uma-aplicacao/). - [Um domínio associado à edge application](/pt-br/documentacao/produtos/guias/configurar-dominio/). - [Tiered Cache habilitado](/pt-br/documentacao/produtos/guias/billing-and-subscriptions/) em sua conta. +- Acesso ao [Edge Storage da Azion](/pt-br/documentacao/produtos/store/edge-storage/) para armazenar conteúdo de vídeo. --- @@ -130,6 +131,14 @@ Ainda na aba **Cache Settings**: Leia mais sobre a configuração de [cache settings](/pt-br/documentacao/produtos/build/edge-application/cache-settings/) para suas edge applications. ::: +### Utilize o Edge Storage da Azion para entrega de vídeos HLS + +Para entregar vídeos MP4 usando HLS e o Edge Storage: + +1. Faça o upload dos arquivos de vídeo MP4 para o Edge Storage. +2. Configure o seu codificador para converter os arquivos MP4 para o formato HLS e defina o Edge Storage como origem. +3. Siga as etapas de configuração da política de cache mencionadas acima para garantir uma entrega eficiente de vídeo. + ### Crie regras no Rules Engine @@ -242,6 +251,3 @@ Acesse a documentação do [Rules Engine for Edge Application](/pt-br/documentac ::: - ---- -