# Say hello to ResponseTimeMs in your Gateway DNS logs!

Hey there, it's me, Shiichan! Today I've got a small-but-handy update that log fans will love.

## What was announced?

Straight from Cloudflare's Changelog, here's a [Logs](https://developers.cloudflare.com/logs/) update. The Gateway DNS Logpush dataset gained a new field called `ResponseTimeMs`. Just like the name says, it tells you how long a DNS request took, in milliseconds.

## The story so far

Until now, Gateway DNS logs recorded things like resolution and filtering results, but there wasn't a field that directly showed "how long this one request took." So when DNS felt slow, pulling the raw response time straight out of your logs was a bit of a chore.

## What changes

With `ResponseTimeMs` in place, you can aggregate and monitor the response time of each DNS request right through Logpush. When latency bugs you, you can now chase it down with real numbers, which makes performance a lot easier to see.

## Dive Deep

The field lives in the [Gateway DNS dataset](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/gateway_dns/) field definitions, and the description for [ResponseTimeMs](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/gateway_dns/#responsetimems) reads:

> Total response time of the DNS request in milliseconds.

So it's a single, simple value: the total response time of a DNS request in milliseconds. If you already run a Logpush job for this dataset, you just add the field to what you ingest and you're good to go.

## Wrap-up

- The Gateway DNS Logpush dataset gained a `ResponseTimeMs` field
- It holds the total response time of a DNS request, in milliseconds
- You can now track DNS latency with real numbers through Logpush

This one quietly helps out the ops folks watching their networks through Zero Trust Gateway!