destination_conf - Refer to Destination for details.
Response
A challenge file will be written to the destination, and the filename will be in the response (the filename may be expressed as a path if appropriate for your destination). For example:
You will need to provide the token contained in this file when creating a job in the next step.
Step 2 - Create a job
Parameters
name (optional) - We suggest using your domain name as the job name; the name cannot be changed after the job is created.
destination_conf - Refer to Destination for details.
dataset - The category of logs you want to receive. Refer to Log fields for the full list of supported datasets; this parameter cannot be changed after the job is created.
In the response, you get a newly-created job ID. For example:
Step 3 - Enable (update) a job
Start by retrieving information about a specific job, using a job ID:
Response
Note that by default a job is not enabled ("enabled": false).
If you do not remember your job ID, you can retrieve it using your zone ID:
Next, to enable the job, send an update request:
Response
Once the job is enabled, you will start receiving logs within a few minutes and then in batches as soon as possible until you disable the job. For zones with very high request volume, it may take several hours before you start receiving logs for the first time.
In addition to modifying enabled, you can also update the value for output_options. To modify destination_conf, you will need to request an ownership challenge and provide the associated token with your update request. You can also delete your current job and create a new one.
Once a job has been enabled and has started executing, the last_complete field will show the time when the last batch of logs was successfully sent to the destination:
Request to get job by ID and see last_complete info
Response
Optional - Delete a job
Be careful when deleting a job because this action cannot be reversed.
Response
Optional - Retrieve your job
Retrieve a specific job, using the job ID:
Response
Retrieve all jobs for all datasets:
Response
Optional - Update output_options
If you want to add (or remove) fields, change the timestamp format, or enable protection against the Log4j - CVE-2021-44228 vulnerability, first retrieve the current output_options for your zone.
Response
Next, edit the output_options as desired and create a PUT request. The following example enables the CVE-2021-44228 redaction option.
Note that at this time, the CVE-2021-44228 option is not available through the UI, and updating your Logpush job through the UI will remove this option.
Response
Was this helpful?
What did you like?
What went wrong?
Thank you for helping improve Cloudflare's documentation!