Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Packetbeat] Update DNS protocol to use ECS fields (#9941)
* Vendor github.com/elastic/ecs/code/go/ecs Update NOTICE * Update DNS protocol to use ECS fields This updates the DNS protocol to have more closely follow ECS. The DNS tunneling dashboard has been updated to work with the new field names. In order to better interoperate with other data sources the trailing dot has been removed from domain names. For example, previously Packetbeat would produce `dns.question.name:elastic.co.` and now it will simply produce `dns.question.name:elastic.co`. It's a breaking change but it will be make it easier to pivot with other data sources. Part of #7968 Here's a summary of what fields changed. Changed - bytes_in -> source.bytes - bytes_out -> destination.bytes - notes -> error.message - responsetime -> event.duration (unit are now nanoseconds) - transport -> network.transport Added - event.end - event.start - network.bytes - network.community_id - network.protocol = dns - network.transport = udp/tcp - network.type Unchanged Packetbeat Fields - method - dns opcode - query = class {{ dns.question.class }}, type {{ dns.question.type }}, {{ dns.question.name }} - request - text representation of the entire request - response - text representation of the entire response - resource - dns.question.name - status - type = dns (we might remove this since we have event.dataset) * Add packetbeat fields to ecs-migration.yml No aliases yet because these fields are still used. * Fix DNS overview dashboard There was an ID collision over the `DNS` ID. * Update dashboards.yml * Send zero value time.Duration With low resolution timers on Windows it's very possible that an event can have an event.duration=0 and we want to send that field when this occurs.
- Loading branch information