TenantID and Firewall for AI fields join Logpush!
Hey there, it's me, Shii-chan! Today I've got a nice little treat for the log lovers out there.
Cloudflare Changelog
developers.cloudflare.com
What was announced?
Over on the Cloudflare Changelog, there's news that a few new fields have been added to the Logpush datasets. This April 15, 2026 update brings two kinds of additions: the TenantID field, and a set of Firewall for AI fields.
The story so far
Until now, with the Gateway-style logs it was a bit of a pain to tie a request back to which tenant it came from using the logs alone. And for AI-related threat detection, there wasn't yet a place in the logs to record exactly what verdict was reached.
What changes
The TenantID field was added to four datasets: Gateway DNS, Gateway HTTP, Gateway Network, and Zero Trust Network Sessions. Now you can identify which tenant each request belongs to right from the logs. For anyone running multi-tenant setups, that's a quietly useful one.
The other addition, the Firewall for AI fields, landed in the Firewall Events and HTTP Requests datasets.
Dive Deep
The Firewall for AI fields put verdicts like the injection score, PII category detection, token counting, and unsafe-topic categorization into your logs. When you want to keep an eye on prompt injection or leaking personal info, being able to analyze it from the raw logs is a lovely thing.
The field definitions for the affected datasets are documented under Firewall Events and HTTP Requests.
Wrap-up
- On April 15, 2026, new fields were added to the Logpush datasets
- TenantID covers four datasets: Gateway DNS / HTTP / Network and Zero Trust Network Sessions
- Firewall for AI fields (injection score, PII, token count, unsafe topics) were added to Firewall Events and HTTP Requests
- This one lands well for folks running multi-tenant setups, and for security folks who want to trace AI-driven threats through their logs!
