Telegraf for ARM systems? (e.g. Netgate SG-3100).
-
I’ve looked only a little for the FreeBSD source for telegraf with the intention of compiling directly on the SG-1100 then making the binary available for others. Didn’t think about a Pi, or about 7 other SBCs laying around. Not sure how a cross compile on FreeBSD would look, but could be interesting.
-
I seem to recall suggesting that, or something similar, to our developers when we first saw this issue and it was dismissed as impractical due to the time it would require.
But if you've got the device and the time then give it a whirl.Cross compiling is problem for the dependencies here. I believe GO will not compile using our current setup which is the root of the problem here.
Steve
-
@stephenw10 Honestly this may be something that, if the community could help, may provide beneficial to everyone. I can go out and grab the source and compile it myself, but that doesn't really help the community as a whole unless everyone compiles it themselves.
Sounds like there are a couple of us willing to throw our hats in the ring to help in some way with this. -
I'd just like to add one more vote for getting Telegraf running on the SG-1100
-
Well, I upgraded my SG-1100 to 2.4.5 p1 and out of the blue Telegraf started working. I didn't even notice it at first until I was looking at my Grafana dashboard and saw more than one pfSense host reporting data. So not sure what changed with the p1 release, but that seems to have been the puzzle piece to getting this working.
-
This is interesting! I wonder if others are also working after the upgrade.
-
I experienced the same thing, Telegraf seems to work on my SG-1100 since the 2.4.5 p1 update.
-
is it back on the package manager? i cant seem to find it anymore, i also upgraded to p1
-
The SG-3100 is a different architecture than the SG-1100. Hence why telegraf is available for some (SG-1100) users and not the rest of. Note: the thread is about Telegraf on ARM devices including the SG-3100, my understanding is that Go complied cleanly on the SG-1100 so they can build for that. This leave those of us who paid for a beefier system from Netgate in a bind. If I'd have went with a cheaper Intel Potectli or Qotom, I'd have x86_64 architecture and the ability to run just about anything, while saving money. I can't see a reason to buy the SG-3100 going forward, Telegraf being just one example of how this architecture is a second-class citizen for Netgate.
-
I wouldn't say Netgate is to blame in this particular instance. The A57 in the SG-3100 is a newer, more advanced processor than the A9 that is in the SG-1100, so there's going to be some compiler challenges there.
But more so, this whole ARM journey fundamentally is a FreeBSD problem of being way behind the bar in this area. Until using pfSense and FreeNAS, I wouldn't touch BSD or any variant with a 10 foot pole, and outside of these two uses I still won't as there's jsut too many quarks with it in my humble opinion.
Anyway, Go is being distributed separately from anything Netgate has control over, so can't blame them for those shortcomings.
Now with that, I have my little SG-1100 which does not impress me in the least, and I have my larger Protectcli device, the FW2 to be exact, and going forward I will stay with my instincts and not go with the ARM based platforms for running freeBSD on to avoid the quarks. I will continue to have my assortment of ARM based systems mind you, just running Linux instead.
I do feel that the release of the ARM hardware for pfSense was a mistake on Netgate's part, it just created very bad feedback for them unfortunately without more support and maturity on the part of the freeBSD foundation.
-
@jlw52761 said in Telegraf for ARM systems? (e.g. Netgate SG-3100).:
I wouldn't say Netgate is to blame in this particular instance. The A57 in the SG-3100 is a newer, more advanced processor than the A9 that is in the SG-1100, so there's going to be some compiler challenges there.
But more so, this whole ARM journey fundamentally is a FreeBSD problem of being way behind the bar in this area. Until using pfSense and FreeNAS, I wouldn't touch BSD or any variant with a 10 foot pole, and outside of these two uses I still won't as there's jsut too many quarks with it in my humble opinion.
Anyway, Go is being distributed separately from anything Netgate has control over, so can't blame them for those shortcomings.
Now with that, I have my little SG-1100 which does not impress me in the least, and I have my larger Protectcli device, the FW2 to be exact, and going forward I will stay with my instincts and not go with the ARM based platforms for running freeBSD on to avoid the quarks. I will continue to have my assortment of ARM based systems mind you, just running Linux instead.
I do feel that the release of the ARM hardware for pfSense was a mistake on Netgate's part, it just created very bad feedback for them unfortunately without more support and maturity on the part of the freeBSD foundation.
The funny thing is... the package from github has worked on my sg3100 since being released. Even after updates.
-
Hi,
Which package from Github is this please?
How did you set it up?
Thanks,
Victor -
+1 I'd love to know about how you got it working on your SG-3100. I'm guessing you mean this package from github? If anyone has any resources to share on this, please post here. I would love to have monitoring for the SG-3100 but it's not worth hours of tinkering for me.
-
@jlw52761 - Well, what you say would make sense, if any Netgate pages actually mentioned that the SG-3100 doesn't support all software, or was a bit more open about the limitations when pushing it.
I love Netgate - and have bought > 10+ devices from them myself, but this lack of clarity/commitment really irks me:
I subscribe to the Netgate newsletter - today I get this email:
They're still pushing the SG-3100 as a great device - but fail to mention that various packages don't work with it, but will on x86 based hardware =(.
@stephenw10 - Do you know if fixing Golang/Rust packages is still on the roadmap for Netgate developers? Just having a clear answer would be good, so we know whether to keep buying the SG-3100, or if an x86-based option is a better choice.
-
I just saw the announcement of a new ARM-based device, the Netgate SG-2100.
Any chance that means Telegraf (and other Go/Rust packages) will be working on the Netgate ARM boxes soon?
-
@victorhooi telegraf is in the package manager on the SG-1100 and has been running pretty reliably.
As for the SG-2100, I’m still underwhelmed by FreeBSD on ARM in general and honestly for the same money I can get an x86 based Protectli FW2 with more horsepower and much more disk in the form of NVMe. I just can’t see justifying the SG-2100 purchase unless you don’t want to run Community Edition. -
I’m thinking about upgrading from the 1100 to the 2100 as it offers 4x the Ram and additional physical ports. The 1100 has been very stable and reliable for me but not really enough memory for running additional plugins. I would by the Netgate over the Protectli to support the company, their mission and their values.
-
@zaxxon you can purchase the TAC support and support the company or just donate. In the end it is about what fits your needs and if the SG-1100 has been fitting the bill then the SG-2100 definitely will.
-
It would be nice if the SG-3100 had 4GB of RAM, in due time maybe with the new release Telegraf will be supported.
-
The SG-2100 does support Telegraf because, like the SG-1100, it is arm64 which means the cross compiling issues can be worked around and native compiling is possible.
The problem here is 32bit arm, so the SG-3100 and SG-1000. Currently we have no solution to that but we would very much like to. We are still looking into ways to do this.BTW the FW2 does not support NVMe, it's mSATA like most systems of that age. So don't buy an NVMe drive if you have one.
Steve
-
This post is deleted! -
How's the progress on this?
-
Any update on this?
-
pls respond
-
No updates to share. We still have the same architectural challenges as before. As soon as our engineers can find a solution we will definitely post back to this thread to share with all.
-
@dennis_s What's really the blocker here? I currently have an SG-3100 with the current version of pfsense and am using telegraf from an older build. What's really blocking Netgate? Is it go or?
-
@dennis_s not being funny, this goes since April 2019. Are you really want to tell us that netgate devs can't make it work, they just don't listen or can't be bothered. 2 years ... it's not only thread where ppl are asking for it.
-
I find it odd because I had installed the telegraf pkg from an SG-1100 (through the Package Manager) sometime in January 2021. And since then, the pkg is no longer available (it was removed during my update to 21.02, and was unavailable after completing the update). So I had a fully-configured and functional telegraf module (reporting to InfluxDB) that got nuked in the 21.02 update process. Rather frustrating because I was using that to improve my monitoring resolution metrics for resolving some upstream WAN losses I've been having with my ISP.
EDIT: Should be noted that I forgot it was mentioned that the SG-1100 is
aarch64
, so there should be a pkg available. But it seems to have gone AWOL. -
Hi friends.
Same issue with the prometheus node_exporter.
Would like to have that for the SG-3100.
-
Telegraf is now available again for arm64 systems, SG-1100 and SG-2100 systems.
Please test and let us know if you see any issues there.The same problems still exist for arm32(v6/7) but there is potential solution in the pipeline.
Steve
-
@stephenw10 Thank you; genuinely appreciate this. The package installed without issue on my SG-1100 and even remembered its old configuration from 2.4.5p1. I will update without any issues or bugs that may arise as far as I can tell.
-
For anyone who can use Prometheus instead of Telegraf, I recently found this blog post that might unblock you. I am not the author, and I haven't had a chance to try it out yet. I'm posting just because I've been watching this thread hopefully for a long time, and I am pretty sure this will satisfy my monitoring needs when I get to it. https://brendonmatheson.com/2021/02/07/step-by-step-guide-to-connecting-prometheus-to-pfsense-via-snmp.html
-
I have a copy of the "telegraf-1.9.0.txz" from "https://github.com/influxdata/telegraf/issues/5282" if anyone wants / needs. I upgraded my SG-3100 via the gui and telegraf still survived after the 21.02 update. Thank Google for static linking...
-
https://github.com/influxdata/telegraf/issues/8922
Someone has to be able to do this. This /can/ work, but who's going to blink?
The code /looks/ to already be in FreeBSD. What am I missing? https://github.com/freebsd/freebsd-ports/blob/master/net-mgmt/telegraf/Makefile
https://github.com/rickyzhang82/FreeBSDWiki/wiki / https://forums.freebsd.org/threads/how-to-cross-compile-port-in-amd64-for-armv7.71761/ , funny enough, is about the SG-3100 and how to build freebsd ports for it.
I'm going to try and get a newer version of telegraf built and report back. Hopefully I don't get paged this week.... >_>
-
@somken said in Telegraf for ARM systems? (e.g. Netgate SG-3100).:
telegraf-1.9.0.txz
Yes please, I would love to give it a go
-
@stephenw10 said in Telegraf for ARM systems? (e.g. Netgate SG-3100).:
Telegraf is now available again for arm64 systems, SG-1100 and SG-2100 systems.
Please test and let us know if you see any issues there.The same problems still exist for arm32(v6/7) but there is potential solution in the pipeline.
Steve
I was excited to setup a TIG stack with my SG-3100 but very surprised to see that Telegraf wasn't available from the package manager. However, after learning about pfSense's uPnP performance, I wasn't very surprised to see that this has been an issue for over a year without any resolution. @stephenw10 you mentioned last March that you do not have any armv6 build hardware... do you guys still need an SG-3100?
-
OK OK OK, I'm working on the build now. Going with Science....
Edit: Dear Science the compiles take forever. An hour into building GO.... Ryzen 3900x...
-
@bigchimpin said in Telegraf for ARM systems? (e.g. Netgate SG-3100).:
@stephenw10 said in Telegraf for ARM systems? (e.g. Netgate SG-3100).:
Telegraf is now available again for arm64 systems, SG-1100 and SG-2100 systems.
Please test and let us know if you see any issues there.The same problems still exist for arm32(v6/7) but there is potential solution in the pipeline.
Steve
I was excited to setup a TIG stack with my SG-3100 but very surprised to see that Telegraf wasn't available from the package manager. However, after learning about pfSense's uPnP performance, I wasn't very surprised to see that this has been an issue for over a year without any resolution. @stephenw10 you mentioned last March that you do not have any armv6 build hardware... do you guys still need an SG-3100?
Isn't the SG-3100 armv7? https://en.wikipedia.org/wiki/ARM_Cortex-A9
-
@somken said in Telegraf for ARM systems? (e.g. Netgate SG-3100).:
@bigchimpin said in Telegraf for ARM systems? (e.g. Netgate SG-3100).:
@stephenw10 said in Telegraf for ARM systems? (e.g. Netgate SG-3100).:
Telegraf is now available again for arm64 systems, SG-1100 and SG-2100 systems.
Please test and let us know if you see any issues there.The same problems still exist for arm32(v6/7) but there is potential solution in the pipeline.
Steve
I was excited to setup a TIG stack with my SG-3100 but very surprised to see that Telegraf wasn't available from the package manager. However, after learning about pfSense's uPnP performance, I wasn't very surprised to see that this has been an issue for over a year without any resolution. @stephenw10 you mentioned last March that you do not have any armv6 build hardware... do you guys still need an SG-3100?
Isn't the SG-3100 armv7? https://en.wikipedia.org/wiki/ARM_Cortex-A9
Looks like it. So any ideas what version of Telegraf is worth installing on the SG-3100? And looking around, there doesn't seem to be up to date documentation on how to install a package outside of what's available from the package manager... do you have a guide you'd recommend for installation?
-
If it's a compiled package you can just add it:
pkg add <path-to-package>
As long as the dependencies are met.
Steve