Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New component: dnstap #33705

Open
3 tasks
atoulme opened this issue Jun 21, 2024 · 2 comments
Open
3 tasks

New component: dnstap #33705

atoulme opened this issue Jun 21, 2024 · 2 comments
Labels
Sponsor Needed New component seeking sponsor

Comments

@atoulme
Copy link
Contributor

atoulme commented Jun 21, 2024

The purpose and use-cases of the new component

dnstap is a flexible, structured binary log format for DNS software. It uses Protocol Buffers to encode events that occur inside DNS software in an implementation-neutral format. This is a binary stream of data. It's used in many modern DNS servers like Bind9 or Unbound.

Example configuration for the component

I don't know enough yet. This issue will add more information as we gather support.

dnstap:
  endpoint: localhost:1234

Telemetry data types supported

metrics

Is this a vendor-specific component?

  • This is a vendor-specific component
  • If this is a vendor-specific component, I am a member of the OpenTelemetry organization.
  • If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

No response

Sponsor (optional)

No response

Additional context

No response

@atoulme atoulme added Sponsor Needed New component seeking sponsor needs triage New item requiring triage labels Jun 21, 2024
@thiagogcm
Copy link

This dnstap plugin in coredns might be a useful example

https://github.com/coredns/coredns/tree/master/plugin/dnstap

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Sponsor Needed New component seeking sponsor
Projects
None yet
Development

No branches or pull requests

2 participants