Skip to content

DNS name tracking blog#32

Open
memodi wants to merge 4 commits intonetobserv:mainfrom
memodi:dnsname-tracking
Open

DNS name tracking blog#32
memodi wants to merge 4 commits intonetobserv:mainfrom
memodi:dnsname-tracking

Conversation

@memodi
Copy link
Member

@memodi memodi commented Mar 13, 2026

DNS name tracking blog

@github-actions
Copy link

github-actions bot commented Mar 13, 2026

🚀 PR Preview for netobserv.io has been successfully deployed!
It's available at https://netobserv-io-blog-32-preview.surge.sh and will be removed when the PR closes.

@memodi memodi force-pushed the dnsname-tracking branch from 2145af3 to 5cf49b7 Compare March 13, 2026 19:11
@memodi memodi changed the title WIP: DNS name Tracking blog DNS name Tracking blog Mar 13, 2026
@memodi
Copy link
Member Author

memodi commented Mar 13, 2026

/cc @jotak @jpinsonneau @stleerh

@memodi memodi requested review from jotak, jpinsonneau and stleerh March 13, 2026 19:13
@memodi memodi changed the title DNS name Tracking blog DNS name tracking blog Mar 13, 2026
@memodi memodi force-pushed the dnsname-tracking branch from 7e1ad4b to d0d4cbf Compare March 13, 2026 19:17
@memodi memodi force-pushed the dnsname-tracking branch from d0d4cbf to 605685a Compare March 13, 2026 19:32
Comment on lines +93 to +94
you must use Loki as your datasource. Captured DNS names will be truncated at 32
bytes to balance the memory netobserv-ebpf-agent's memory utilization.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can add a sentence explaining that 32 bytes is enough in most scenarios ?

jpinsonneau
jpinsonneau previously approved these changes Mar 16, 2026
Copy link
Member

@jpinsonneau jpinsonneau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks @memodi !


Network Observability has long had a feature that reports the DNS latencies and
response codes for the DNS resolutions in your Kubernetes cluster. `DNSTracking`
feature can be simply enabled in Flowcollector config as below.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: FlowCollector or flowcollector would be best.

memodi and others added 2 commits March 17, 2026 12:58
Co-authored-by: Amogh Rameshappa Devapura <aramesha@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants