# The `ebpf object flavor` option selects the eBPF object file family:
#  `arena`  : Use the BPF arena object flavor when available.
#  `buffer` : Use the ring-buffer object flavor when available (aliases: `buffer ring`, `ring buffer`).
#  `legacy` : Use the legacy tracing object files (alias: `tracing`).
# If the requested flavor is not available, eBPFGo falls back to the next supported flavor.
# Legacy C modules accept this key for compatibility; `legacy` forces the legacy path.
#
# The legacy `ebpf type format` option is still accepted for compatibility:
#  `auto`  : Let the collector choose the load path.
#  `legacy`: Use the legacy tracing object files.
#  `co-re` : Use CO-RE when available.
#
# Uncomment lines to define specific options for the dns thread.
[global]
    update every = 10
    ebpf object flavor = buffer
    ebpf type format = auto
    # The `per query tracking` option enables per-DNS-query latency tracking.
    # When enabled, the collector records the time between each DNS request and
    # its matching response, producing per-query latency metrics.
    # Required for the dns-queries Function consumed by network-viewer.  Default: yes.
    # per query tracking = yes
    # The `flow ttl` option defines the DNS flow record lifetime in seconds.
    # Two constraints apply:
    #   1. update every must not exceed this value: records older than flow ttl expire
    #      in the kernel ring before collection, causing silent data loss.
    #   2. This value must equal NV_DNS_UPDATE_EVERY (20) in network-viewer.c.
    #      The network-viewer dns-queries Function reads the SHM once every 20 s and
    #      expects exactly one non-overlapping window per read.  A value other than 20
    #      causes double-counting (flow ttl > 20) or silent record loss (flow ttl < 20).
    #      Changing this option without a matching network-viewer rebuild will break
    #      the dns-queries Function results.  Default: 20.
    # flow ttl = 20
