# Basic troubleshooting on Azion Web Platform

Use this guide to troubleshoot your application on the Azion Web Platform. Learn how to enable Debug Rules, use Real-Time Events, and query data with GraphQL to understand why specific actions were applied to your requests. This guide includes a practical example that shows how to identify which rules were executed and why a request was blocked.

## Enabling Debug Rules

Debug Rules can be enabled in both **Applications** and **Firewall**. They show which rules were executed for a request and the actions those rules took (blocking is just one example), helping you understand why a specific action was applied.

To enable Debug Rules for Applications:

1. Access [Console](https://console.azion.com).
2. Go to **Products menu** > **Applications**.
3. Select an existing application to activate debug.
4. On the **Main Settings** tab, enable the **Debug Rules** option.
5. Click the **Save** button.

To enable Debug Rules for Firewalls:

1. Access [Console](https://console.azion.com).
2. Go to **Products menu** > **Firewalls**.
3. Select the firewall you want to configure.
4. On the **Main Settings** tab, enable the **Debug Rules** option.
5. Click the **Save** button.

### Real-Time Events

To access Real-Time Events, follow these steps:

1. Access [Console](https://console.azion.com).
2. On the upper-left corner, select **Products menu** > **Real-Time Events**.
3. Select the **HTTP Requests** tab.
4. Modify the desired time range and filters.
5. Click the **Search** button.

### GraphQL

To access the Azion **GraphQL** built-in playground accessible via the Real-Time Events menu, or by [visiting this link](https://api.azion.com/v4/events/graphql#query=query%20\(%0A%09%24tsRange_begin%3A%20DateTime!%0A%09%24tsRange_end%3A%20DateTime!%0A\)%20%7B%0A%09httpEvents%20\(%0A%09%09limit%3A%2010%0A%09%09orderBy%3A%20%5Bts_DESC%5D%0A%09%09filter%3A%20%7B%0A%09%09%09tsRange%3A%20%7B%20begin%3A%20%24tsRange_begin%2C%20end%3A%20%24tsRange_end%20%7D%0A%09%09%09%23hostEq%3A%20%0A%09%09%09%23statusEq%3A%0A%20%20%20%20%20%20%23requestIdEq%3A%22%22%0A%09%09%7D%0A%09\)%20%7B%0A%20%20%20%20ts%0A%20%20%20%20requestId%0A%09%09%23configurationId%0A%09%09host%0A%09%09%23requestMethod%0A%09%09status%0A%20%20%20%20upstreamStatus%0A%20%20%20%20%23upstreamResponseTime%0A%09%09%23upstreamBytesSent%0A%09%09%23sslProtocol%0A%09%09%23wafLearning%0A%09%09%23requestTime%0A%09%09%23serverProtocol%0A%09%09upstreamCacheStatus%0A%09%09%23httpReferer%0A%09%09remoteAddress%0A%20%20%20%20stacktrace%0A%09%09wafMatch%0A%09%09%23serverPort%0A%09%09%23sslCipher%0A%09%09wafEvheaders%0A%09%09%23serverAddr%0A%09%09%23scheme%0A%20%20%20%20httpUserAgent%0A%20%20%20%20%0A%09%7D%0A%7D\&variables=%7B%22tsRange_begin%22%3A%222026-01-29T12%3A00%3A00%22%2C%22tsRange_end%22%3A%222026-01-29T13%3A59%3A59%22%7D).

> **Tip**
>
> Check the [GraphQL API documentation](/en/documentation/devtools/graphql/overview/) for more information.

By default, all requests are logged using the UTC time zone.

## A practical example

For this example we will use a sample application in which when you access the `/block` URI the request will be blocked with a `403` status.

So if you tried to access the site you will get a 403 error page that looks like this:

![Azion Error page](/assets/docs/images/troubleshooting-guides/basic-troubleshoot-error.png)

How can you find out exactly why this request was blocked?

For the steps below, copy the **Request ID** displayed on the page.

> **Tip**
>
> The **Request ID** is the same identifier shown on the Azion error page under **Error Details**. For a description of all fields on that page and what each HTTP status code means, see [HTTP Error Status Codes](/en/documentation/fundamentals/http-status-codes/).

### In Real Time Events

1. Access **Real-Time Events**
2. Filter by the request id you copied.
3. Select the log body.
4. Look for the **stacktrace** field.

You'll see a response similar to this:

```json
{
  "edge_application_request": [
    "Default Rule",
    "block"
  ]
}
```

The `stacktrace` field tells you that the Application rule named `block` was executed.

### In GraphQL Playground

1. Access the GraphQL Playground
2. Run the query below, replacing the `tsRange` and `requestIdEq` fields with the correct values.

```graphql
 query (
	$tsRange_begin: DateTime!
	$tsRange_end: DateTime!
) {
	httpEvents (
		limit: 10
		orderBy: [ts_DESC]
		filter: {
			tsRange: { begin: $tsRange_begin, end: $tsRange_end }
			#hostEq: 
			#statusEq:
      #requestIdEq:""
		}
	) {
        ts
        requestId
		#configurationId
		host
		#requestMethod
		status
        upstreamStatus
        #upstreamResponseTime
		#upstreamBytesSent
		#sslProtocol
		#wafLearning
		#requestTime
		#serverProtocol
		upstreamCacheStatus
		#httpReferer
		remoteAddress
        stacktrace
		wafMatch
		#serverPort
		#sslCipher
		wafEvheaders
		#serverAddr
		#scheme
    httpUserAgent
    
	}
}
```

You'll get a response similar to this:

```json
{
  "data": {
    "httpEvents": [
      {
        "configurationId": "xxx",
        "host": "xxxxx.azionedge.net",
        "requestId": "your_request_id_here",
        "httpUserAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.1 Safari/605.1.15",
        "requestMethod": "GET",
        "status": 403,
        "ts": "2026-01-22T21:10:38Z",
        "stacktrace": "{\\\"edge_application_request\\\":[\\\"Default Rule\\\",\\\"block\\\"]}",
        "upstreamBytesSent": 0,
        "sslProtocol": "TLSv1.3",
        "wafLearning": "-",
        "requestTime": "0",
        "serverProtocol": "HTTP/2.0",
        "upstreamCacheStatus": "-",
        "httpReferer": "-",
        "remoteAddress": "xxxx",
        "wafMatch": "-",
        "serverPort": "443",
        "sslCipher": "TLS_AES_256_GCM_SHA384",
        "wafEvheaders": "-",
        "serverAddr": "192.0.2.11",
        "scheme": "https"
      }
    ]
  }
}
```

The `stacktrace` field tells you that the Application rule named `block` was executed.