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

Support for CPU, network and filesystem stat collection on NetBSD #1868

Closed
wants to merge 4 commits into from

Conversation

sthomen
Copy link

@sthomen sthomen commented Oct 16, 2020

This PR adds code to make node_exporter more useful on NetBSD hosts. I mainly cobbled this together from the freebsd and openbsd specific code that was already in here, since I don't speak golang at all.

There probably are opportunities for deduplication--especially netdev_netbsd.go which is a single line difference from the netdev_bsd.go which assumes that a FreeBSD-specific struct member exists--that I just don't know about, and I would ask you to please check my work.

@SuperQ @discordianfish

Staffan Thomen added 4 commits October 16, 2020 22:56
Signed-off-by: Staffan Thomen <staffan@thomen.fi>
…qdrops

Signed-off-by: Staffan Thomen <staffan@thomen.fi>
Signed-off-by: Staffan Thomen <staffan@thomen.fi>
Signed-off-by: Staffan Thomen <staffan@thomen.fi>
@tnn2
Copy link

tnn2 commented Nov 1, 2020

Hello,

I get some build errors with this PR. I think:

  • netdev_netbsd.go: needs to be rebased on netdev_openbsd.go
  • cpu_netbsd.go: func NewCPUCollector needs fixed call signature, should take logger log.Logger as argument like in cpu_freebsd.go.

@discordianfish
Copy link
Member

Yeah I kinda dropped the ball on this PR. Ideally someone with netbsd experience could help getting this into a shape to merge it. E.g fixing these issues, the ci issues and refactor it to get rid of the copypasta

@tnn2
Copy link

tnn2 commented Nov 25, 2020

@discordianfish I have a local branch where I have done most of the work so that it applies properly on master. I'll see about submitting it as new pull request(s) and then we can close this.

@sthomen
Copy link
Author

sthomen commented Nov 29, 2020

Thank you for looking into fixing my mess, sorry I can't really help much

@discordianfish
Copy link
Member

I'm going to close this for now. If anyone wants to pick that up, fix the issues and re-submit please do so!

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.

3 participants