The trick with the Netdata agent is to try the install script if running into trouble.

Yeah, having looked at what the script does I decided to 'containerize' the agent, and that led to other issues like configuring email alerts etc.

I was already a week deep into looking at various options and had to deliver on basic metrics and alerting, so I figured a couple of bash scripts, that log into local files with log rotation, systemd, and a dump/memory only receiving end running on nodejs for the alerts would be much faster and easier to maintain.

So far so good.

Well, that's the beauty of Netdata, no need to configure collectors. As for InfluxDB integration, it's fairly easy to export from Netdata using what InfluxDB calls the line protocol format (the "plaintext interface").

https://learn.netdata.cloud/docs/agent/exporting

You may want to read through and register your interest for this github issue which likely solves what you ran into.

https://github.com/netdata/netdata/issues/4392#issue-3698875...

Honestly, I would swear up and down that I tried that already (e.g. `old_stats` is already in the plugins list) but apparently not quite exactly right - now I have stats.

Thanks!

[edit: Although, saying that, I have stats that are resolutely stuck at 0 for everything even though I'm watching the traffic go through. But it's a start.]