https://github.com/netdata/netdata/releases/tag/v2.9.0 new version again ...
I just want to warn you, version 2.9.0 turns out that it can no longer visualize data from more than 5 servers ( 2.8.5 still works with more then 5 ), even if it is not connected to netdata.cloud. Honestly, this is already too commercializing the project for me. The main problem is that I can't find a good real-time working alternative. There are some workarounds published like https://github.com/unixfox/netdata-unlock-5-nodes but it's hacking and is practically illegal.
Apologies for the super late reply. I'll try to get a patch together this week. Unfortunately IRL has been very complicated the last month. With these changes, I might be switching away from netdata in the future. Not completely sure yet but it's an idea I have, I'll still try to provide updates tho, even if I switch away.
Created attachment 268962 [details] upgrade to 2.9.0 - uses agent downloaded from internet Port can't be build inside poudriere because it downloads agent from internet. It's useful for early adopters like me. # portlint -A /usr/ports/net-mgmt/netdata 2>&1 WARN: Makefile: possible use of absolute pathname "/var/cache/${PORTNAM...". WARN: Makefile: possible use of absolute pathname "/var/log/${PORTNAME}". WARN: Makefile: possible use of absolute pathname "/var/db/${PORTNAME}". WARN: Makefile: possible use of absolute pathname "/var/run/${PORTNAME}". WARN: Makefile: new ports should not set PORTREVISION. WARN: /usr/ports/net-mgmt/netdata/files/patch-CMakeLists.txt: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format. WARN: /usr/ports/net-mgmt/netdata/files/patch-packaging_cmake_Modules_NetdataDlib.cmake: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format. WARN: Consider to set DEVELOPER=yes in /etc/make.conf 0 fatal errors and 8 warnings found.
Created attachment 268975 [details] updated to 2.9.0, still with downloads of agent dashboard and open telemetry from internet updated to 2.9.0, still with downloads of agent dashboard and open telemetry from internet. will not build inside poudriere w/o internet access.
Created attachment 268990 [details] upgrade to 2.9.0 - Update DISTVERSION to 2.9.0 - Fix CMake FetchContent issues (Corrosion, dlib) - Add nd-mcp Go bridge vendoring - Fix installation paths (usr/libexec → libexec) - Add OTEL_SIGNAL_VIEWER as separate option - Update pkg-plist for new files There are still references to old agent dashboard. Will be fixed in next patch.
Created attachment 269016 [details] upgrade to 2.9.0 with removed custom agent data - nkeor mirror removed - NETDATA_DASHBOARD_VERSION removed - DASHBOARD_CMAKE_BOOL added - DASHBOARD_DISTFILES/EXTRACT_ONLY removed - OTEL_SIGNAL_VIEWER_CMAKE_BOOL added - post-install-DASHBOARD-on removed - patch-packaging_cmake_Modules_NetdataDlib.cmake added
Created attachment 269019 [details] option DASHBOARD set to on triggers BROKEN if building inside poudriere DASHBOARD triggers BROKEN if building is in poudriere. OPENTELEMETRY_BROKEN removed, because devel/corrosion is dependency. all previously defined improvements are inside too.
Created attachment 269074 [details] update to netdata/agent 2.9.0/7.98.0 ---------------------------------------------------------------- netdata port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.9.0 [INFO] Checking latest netdata release on GitHub... [WARN] Could not fetch latest version from GitHub [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.97.0 [INFO] Fetching remote dashboard version (this may take a moment)... [NEW] New dashboard version: 7.98.0 (installed: 7.97.0) ---------------------------------------------------------------- Summary ---------------------------------------------------------------- [WARN] Dashboard updated but port version unchanged. The dashboard is fetched live during build. To update pkg-plist with new dashboard files: 1. Rebuild: rm -rf /usr/ports/net-mgmt/netdata/work make -C /usr/ports/net-mgmt/netdata build && make -C /usr/ports/net-mgmt/netdata stage 2. Regenerate plist: python3 /usr/local/bin/generate_netdata_plist.py \ /usr/ports/net-mgmt/netdata/work > /usr/ports/net-mgmt/netdata/pkg-plist
Created attachment 269117 [details] upgrade to netdata/agent versions 2.9.0/7.98.0 with proxy support improvements ---------------------------------------------------------------- netdata port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.9.0 [INFO] Checking latest netdata release on GitHub... [WARN] Could not fetch latest version from GitHub [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.98.0 [INFO] Fetching remote dashboard version (this may take a moment)... [OK] Dashboard is up to date (7.98.0) ---------------------------------------------------------------- Summary ---------------------------------------------------------------- [OK] Everything is up to date. No action needed.
Created attachment 269143 [details] upgrade to netdata/agent 2.9.0/7.99.0 with enhanced proxy support ---------------------------------------------------------------- netdata port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.9.0 [INFO] Checking latest netdata release on GitHub... [OK] Port is up to date (2.9.0) [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.99.0 [INFO] Fetching remote dashboard version (this may take a moment)... [OK] Dashboard is up to date (7.99.0) ---------------------------------------------------------------- Summary ---------------------------------------------------------------- [OK] Everything is up to date. No action needed.
Created attachment 269147 [details] upgrade to netdata/agent 2.9.0/7.99.1 with enhanced proxy support ---------------------------------------------------------------- netdata port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.9.0 [INFO] Checking latest netdata release on GitHub... [OK] Port is up to date (2.9.0) [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.99.1 [INFO] Fetching remote dashboard version (this may take a moment)... [OK] Dashboard is up to date (7.99.1)
> I just want to warn you, version 2.9.0 turns out that it can no longer > visualize data from more than 5 servers ( 2.8.5 still works with more then 5 ), > even if it is not connected to netdata.cloud. Honestly, this is already > too commercializing the project for me. If this is the case, the update will break the runtime for many users.
(In reply to Vladimir Druzenko from comment #12) My experiments with the port version that I published here show that things still continue in the old way, as they worked. That is, I have 2 tier 2 netdata servers that visualize the information from 20 other netdata agents. The important thing is that these two that visualize, have never been connected to any netdata.cloud. I also have a 3rd server (tier 3) which is however debian 13.4 and it receives data from the tier 2 machines. However, I had to apply hacks to it to visualize the 23 machines for which there is data. Even since the hack is on node.js which did not want to run under freebsd, I made an alternative version (formed as a port) of python3 daemon doing what node.js does. This is my actual observation, and for the moment I have stopped making changes because I think it would be a big game to adapt the port from the way I have it, to a way in which it will be able to work in poudrierre without internet access. The problem for me is mostly with the rust/cargo part, which depends on too many files downloaded from the internet at the moment. The dashboard itself is not that complicated to use a static snapshot, the problem is with a place (with enough bandwidth for fast access) where it will be hosted. My check_netdata_update.sh still confirms that diff I've added is actual to current moment: ---------------------------------------------------------------- netdata port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.9.0 [INFO] Checking latest netdata release on GitHub... [OK] Port is up to date (2.9.0) [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.99.1 [INFO] Fetching remote dashboard version (this may take a moment)... [OK] Dashboard is up to date (7.99.1) ---------------------------------------------------------------- Summary ---------------------------------------------------------------- [OK] Everything is up to date. No action needed.
(In reply to Vladimir Druzenko from comment #12) I completely understand the approach of compiling the port in an isolated environment, without files downloaded from github, crates.io, etc. It is clear that this is safer and more secure, because the world has already seen several times the compromise of sources in the repositories. However, the truth is that I personally do not have the capacity to truly check whether the code that is downloaded is safe. That is why I stopped at this stage with the modifications of net-mgmt/netdata, because this way I can more easily update it to new versions. I just added block .if defined(HTTP_PROXY) FETCH_ENV+= HTTP_PROXY=${HTTP_PROXY} HTTPS_PROXY=${HTTPS_PROXY} CONFIGURE_ENV+= HTTP_PROXY=${HTTP_PROXY} HTTPS_PROXY=${HTTPS_PROXY} \ NO_PROXY=${NO_PROXY} MAKE_ENV+= HTTP_PROXY=${HTTP_PROXY} HTTPS_PROXY=${HTTPS_PROXY} \ NO_PROXY=${NO_PROXY} GO_ENV+= HTTP_PROXY=${HTTP_PROXY} HTTPS_PROXY=${HTTPS_PROXY} \ NO_PROXY=${NO_PROXY} .endif so that if the machine has a defined HTTP_PROXY in its environment, it can download through that proxy and rust things for opentelemetry.
(In reply to Vladimir Druzenko from comment #12) I could dynamically generate the pkg-plist file so that there is no problem with changes to https://app.netdata.cloud/agent.tar.gz. But I also didn't add this as a block: I could dynamically generate the pkg-plist file so that there is no problem with changes to https://app.netdata.cloud/agent.tar.gz. But I also didn't add this as a block: post-install-DASHBOARD-on: @${ECHO_MSG} "===> Generating dynamic plist for dashboard files..." @${FIND} ${STAGEDIR}${DATADIR}/web/gui -type f | \ ${SED} -ne 's,^${STAGEDIR}${PREFIX}/,,p' >> ${TMPPLIST} @${FIND} ${STAGEDIR}${DATADIR}/web/gui -type d -empty | \ ${SED} -ne 's,^${STAGEDIR}${PREFIX}/,@dir ,p' >> ${TMPPLIST} because I'm not sure how well this approach complies with the port rules.
(In reply to Vladimir Druzenko from comment #12) I would like to mention that what I mentioned above with hacking the communication between browser and netdata server, I personally do not approve of. On the other hand, I personally do not approve of the way an open source project is commercialized. I agree that if storage and AI from netdata.cloud are used, it is right to collect some fee, because of the costs incurred for infrastructure. But other users should not be forced to pay fees, just because they want to monitor multiple servers on their own infrastructure. I also looked for alternatives to netdata, because of my above understandings, but unfortunately the closest is the beszel project (my experiment is at https://beszel.ostreff.info , as well as the description of how I ran it under freebsd https://ostreff.info/how-can-you-use-beszel-on-freebsd/ ) - but it is unfortunately at a very early stage of its development. It can only monitor general metrics of the machine where the agent is run, without special metrics for specific daemons.
I would advice that either stop at 2.8.5 for now and see how it unfolds upstream or move it to a separate directory and keep it locked at the version.
(In reply to Daniel Engberg from comment #17) Sounds acceptable to me as proposal - maybe net-mgmt/netdata-devel is fine as name? My idea is more people to be included and to have possibility to try it.
Created attachment 269221 [details] net-mgmt/netdata-devel version with netdata/dashboard agent 2.9.0/7.99.1 initial version
Created attachment 269222 [details] net-mgmt/netdata-devel version of new-port with netdata/dashboard agent 2.9.0/7.99.1 fixed 1. added LIB_DEPENDS= libdlib.so:science/dlib-cpp 2. CONFLICTS_INSTALL= netdata
Created attachment 269253 [details] net-mgmt/netdata-devel upgrade to 2.9.0/7.99.2 [NEW] New dashboard version: 7.99.2 (was: 7.99.1)
Created attachment 269349 [details] net-mgmt/netdata-devel update to netdata/agent 2.9.0/7.99.4
Created attachment 269451 [details] net-mgmt/netdata-devel upgrade to netdata/agent 2.9.0/7.100.0 with enhanced proxy support ---------------------------------------------------------------- netdata port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.9.0 [INFO] Checking latest netdata release on GitHub... [OK] Port is up to date (2.9.0) [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.100.0 [INFO] Fetching remote dashboard version (this may take a moment)... [OK] Dashboard is up to date (7.100.0) ---------------------------------------------------------------- Summary ---------------------------------------------------------------- [OK] Everything is up to date. No action needed.
Created attachment 269487 [details] net-mgmt/netdata-devel upgrade to netdata/agent 2.9.0/7.100.1 with enhanced proxy support The new dashboard tab implemented into new agent version. ---------------------------------------------------------------- netdata port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.9.0 [INFO] Checking latest netdata release on GitHub... [OK] Port is up to date (2.9.0) [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.100.1 [INFO] Fetching remote dashboard version (this may take a moment)... [OK] Dashboard is up to date (7.100.1) ---------------------------------------------------------------- Summary ---------------------------------------------------------------- [OK] Everything is up to date. No action needed.
Created attachment 269488 [details] net-mgmt/netdata-devel whole port tree compressed covering versions 2.90/7.100.1
Created attachment 269547 [details] net-mgmt/netdata-devel upgrade to netdata/agent 2.9.0/7.100.2 with enhanced proxy support git -C /usr/ports apply --intent-to-add netdata-devel-20260409-145632.patch ---------------------------------------------------------------- netdata port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.9.0 [INFO] Checking latest netdata release on GitHub... [OK] Port is up to date (2.9.0) [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.100.2 [INFO] Fetching remote dashboard version (this may take a moment)... [OK] Dashboard is up to date (7.100.2) ---------------------------------------------------------------- Summary ---------------------------------------------------------------- [OK] Everything is up to date. No action needed.
Created attachment 269548 [details] net-mgmt/netdata upgrade to 2.90/7.100.2
Netdata is still "yelling" at users of the FreeBSD port to get the latest security fixes.
Created attachment 269559 [details] net-momt/netdata upgrade to 2.10.0/7.100.3 netdata port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.10.0 [INFO] Checking latest netdata release on GitHub... [OK] Port is up to date (2.10.0) [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.100.3 [INFO] Fetching remote dashboard version (this may take a moment)... [OK] Dashboard is up to date (7.100.3) ---------------------------------------------------------------- Summary ---------------------------------------------------------------- [OK] Everything is up to date. No action needed.
Created attachment 269560 [details] net-mgmt/netdata-devel upgrade to netdata/agent 2.10.0/7.100.3 with enhanced proxy support netdata-devel port update checker ---------------------------------------------------------------- [INFO] Checking current port version... [OK] Current port version: 2.10.0 [INFO] Checking latest netdata release on GitHub... [OK] Port is up to date (2.10.0) [INFO] Checking dashboard version... [OK] Installed dashboard version: 7.100.3 [INFO] Fetching remote dashboard version (this may take a moment)... [OK] Dashboard is up to date (7.100.3) ---------------------------------------------------------------- Summary ---------------------------------------------------------------- [OK] Everything is up to date. No action needed.
Created attachment 269562 [details] net-momt/netdata upgrade to 2.10.0/7.100.3
Created attachment 269563 [details] net-mgmt/netdata-devel upgrade to netdata/agent 2.10.0/7.100.3 with enhanced proxy support
Created attachment 269564 [details] net-mgmt/netdata upgrade to 2.10.0/7.100.3
Created attachment 269565 [details] net-momt/netdata-devel whole port tree compressed covering versions 2.10.0/7.100.3
Created attachment 269600 [details] net-mgmt/netdata-devel upgrade to netdata/agent 2.10.1/7.100.3 with enhanced proxy support
Created attachment 269601 [details] net-mgmt/netdata-devel whole port tree compressed covering versions 2.10.1/7.100.3
Created attachment 269617 [details] net-mgmt/netdata-devel whole port tree compressed covering versions 2.10.1/7.100.3
Created attachment 269618 [details] net-mgmt/netdata-devel upgrade to netdata/agent 2.10.1/7.100.3
Created attachment 269619 [details] net-mgmt/netdata upgrade to 2.10.0/7.100.3
(In reply to Jan Bramkamp from comment #28) For sure you can get my experimental net-mgmt/netdata-devel port, or other experimental ports which are changing the original net-mgmt/netdata official port. The issue with this versions of port is that they downloads too many of his components from internet. This is agains the freebsd ports rules - the security is lowered for source compromise, but gives flexibility to quickly adapt to new versions...
Created attachment 269629 [details] net-mgmt/netdata upgrade to 2.10.1/7.100.3
Created attachment 269630 [details] net-mgmt/netdata upgrade to 2.10.1/7.100.3
Created attachment 269631 [details] net-mgmt/netdata-devel upgrade to netdata/agent 2.10.1/7.100.3
Created attachment 269632 [details] net-mgmt/netdata-devel whole port tree compressed covering versions 2.10.1/7.100.3