|
1 | 1 | --- |
2 | 2 | pcx_content_type: how-to |
3 | | -title: Logpush |
| 3 | +title: Send Zaraz logs to Logpush |
4 | 4 | sidebar: |
5 | 5 | order: 11 |
| 6 | + label: Logpush |
6 | 7 | --- |
7 | 8 |
|
8 | 9 | import { Plan } from "~/components"; |
9 | 10 |
|
10 | | -Send Zaraz logs to an external storage provider like R2, S3, etc. |
| 11 | +Send Zaraz logs to an external storage provider like R2 or S3. |
11 | 12 |
|
12 | 13 | This is an Enterprise only feature. |
13 | 14 |
|
14 | 15 | ## Setup |
15 | 16 |
|
16 | | -To configure logpush support for Zaraz please follow these steps |
| 17 | +Follow these steps to configure Logpush support for Zaraz: |
17 | 18 |
|
18 | | -### 1. Create a logpush job |
| 19 | +### 1. Create a Logpush job |
19 | 20 |
|
20 | | -Navigate to your Website (Zone) and from the left sidebar find **Analytics and Logs**. |
21 | | - |
22 | | -Under this **Analytics and Logs** section navigate to **Logpush** |
23 | | - |
24 | | -Click on **Create a Logpush Job** and follow the steps described in the [Logpush](/logs/logpush/) documentation. |
25 | | - |
26 | | -When it comes to selecting a dataset please make sure to select **Zaraz Events** |
| 21 | +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and zone. |
| 22 | +2. Go to **Analytics & Logs** > **Logpush**. |
| 23 | +3. Select **Create a Logpush Job** and follow the steps described in the [Logpush](/logs/logpush/) documentation.<br/> |
| 24 | + When selecting a dataset, make sure you select **Zaraz Events**. |
27 | 25 |
|
28 | 26 | ### 2. Enable Logpush from Zaraz settings |
29 | 27 |
|
30 | | -Navigate to your website's [Zaraz settings](https://dash.cloudflare.com/?to=/:account/:zone/zaraz/settings) |
31 | | - |
32 | | -Enable **Export Zaraz Logs**. |
| 28 | +1. Go to your website's [Zaraz settings](https://dash.cloudflare.com/?to=/:account/:zone/zaraz/settings). |
| 29 | +2. Enable **Export Zaraz Logs**. |
33 | 30 |
|
34 | 31 | ## Fields |
35 | 32 |
|
36 | | -Logs will have the following fields |
| 33 | +Logs will have the following fields: |
37 | 34 |
|
38 | | -| Field | Type | Description | |
39 | | -| -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | |
40 | | -| RequestHeaders | `JSON` | The headers that were sent with the request. | |
41 | | -| URL | `String` | The Zaraz URL to which the request was made. | |
42 | | -| IP | `String` | The originating IP. | |
43 | | -| Body | `JSON` | The body that was sent along with the request. | |
| 35 | +| Field | Type | Description | |
| 36 | +| -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | |
| 37 | +| RequestHeaders | `JSON` | The headers that were sent with the request. | |
| 38 | +| URL | `String` | The Zaraz URL to which the request was made. | |
| 39 | +| IP | `String` | The originating IP. | |
| 40 | +| Body | `JSON` | The body that was sent along with the request. | |
44 | 41 | | Event Type | `String` | Can be one of the following: `server_request`, `server_response`, `action_triggered`, `ecommerce_triggered`, `client_request`, `component_error`. | |
45 | | -| Event Details | `JSON` | Details about the event. | |
46 | | -| TimestampStart | `String` | The time at which the event occured. | |
| 42 | +| Event Details | `JSON` | Details about the event. | |
| 43 | +| TimestampStart | `String` | The time at which the event occurred. | |
0 commit comments