Netdata
linux
Our great sponsors
Netdata | linux | |
---|---|---|
118 | 974 | |
67,581 | 168,342 | |
1.1% | - | |
9.9 | 10.0 | |
6 days ago | 3 days ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Netdata
-
A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
netdata.cloud — Netdata is an open-source tool to collect real-time metrics. It's a growing product and can also be found on GitHub!
-
Looking for a way to remote in to K's of raspberry pi's...
Monitoring = netdata on each RPi https://www.netdata.cloud/ binded to the vpn interface being scraped into a prometeus thaons https://thanos.io/ setup with grafana to give management the Green all is good screens (very important).
-
Netdata: query, explore and visualize SystemD Journals!
Home Page and source code: https://github.com/netdata/netdata
-
Show HN: The simplest centralized logs management ever, with SystemD and Netdata
I started the discussion, and offered a solution too:
ok, can we discuss how you see this working for you? How do you believe you can provide SSO to all your Netdata agents?
Please open a discussion here: https://github.com/netdata/netdata/discussions
Even if this may be a niche need, I am open to create such a feature for those that need it, at a small price. But we need some specs.
-
μMon: Stupid simple monitoring
hey - I work on ML at Netdata (disclaimer).
We have a big PR open and under review at moment that brings in a lot more logs capabilities: https://github.com/netdata/netdata/pull/13291
We also have some specific logs collectors too - i think in here might be best place to look around at the moment, should take you to the logs part of the integrations section in our demo space (no login needed, sorry for the long horrible url, we adding this section to our docs soon but at moment only lives in the app)
https://app.netdata.cloud/spaces/netdata-demo/rooms/all-node...
-
Ask HN: How do you monitor your systemd services?
> So I turned to Netdata. A one liner on each server and we had super sexy and fast dashboard for each server. No birds eye view, but fine. I then spent maybe 3-4 days trying to figure out how to get alerting to work (just email, but fine) and get temperature readings (or something like that).
I work in Netdata. Just wanted to mention that as of last release a parent node will show all children in the agent dashboard so if doing again as of today a parent netdata might have got you the birds eye view as a starting point https://github.com/netdata/netdata/releases/tag/v1.41.0
- Show HN: Netdata got new impressive dashboard
-
Questions about Netdata update size/how to disable or move from nightly to stable?
Stable releases are a bit more complicated. Major and minor releases are typically once every few months at the moment, but do not have a consistent release schedule (we’re trying to shift internally to having a consistent release schedule though for these, likely every six to eight weeks). Patch releases are published as needed (either when some serious issue is discovered with the associated release, or when we have enough easily backported fixes in the nightlies to warrant a patch release). You can watch releases at https://github.com/netdata/netdata to see when stable releases are published (though again do note that native packages get published asynchronously relative to these releases being published).
linux
-
TinyMCE (also) moving from MIT to GPL
Correct. And the combined work needs to carry the MIT license text and copyright attributions for the MIT software authors. With binary distribution it must also be overt, not hidden in some source code drop, but directly accompanying the binary.
Many people who talk about relicensing never credit the MIT developers or distribute the MIT license text. "Because it's GPL now."
I don't think that you believe that, but many developers do.
Some don't see the need for source code scans for Open Source compliance, because the license.txt says GPL, so it's GPL. Prime example is the Linux kernel. There is code under different licenses in there, but people don't even read https://github.com/torvalds/linux/blob/master/COPYING till the end ("In addition, other licenses may also apply.") and conclude it's simply GPL 2 and nothing else.
Also be aware that sublicensing is not the same as relicensing.
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
So If we would only count code and not comments, it is only 9489 LoC Rust. Which would be about 0.03% and if we take all lines and not only LoC it would be around 0.05%
[0] https://github.com/XAMPPRocky/tokei
[1] https://github.com/torvalds/linux/commit/b401b621758e46812da...
-
Proposed Windows NT sync driver brings big Wine/Proton performance improvements
AIUI fsync is built on futex_waitv which has been upstreamed. So this has to be more than that.
https://github.com/torvalds/linux/commit/a0eb2da92b715d0c97b...
-
Tell HN: GitHub no longer readable without JavaScript
git clone --no-checkout --depth 1 https://github.com/torvalds/linux.git $dir
-
PixieFail: Nine Vulnerabilities UEFI Implementations
Device trees are what you get if you don't implement ACPI.
While there are alternatives, you generally seem to get "device trees and a barebones bootloader" on ARM and "UEFI + ACPI" on amd64.
ACPI will list hardware and necessary hardware properties based on some basic API calls to the system interface. UEFI initialises the ACPI data structure and exposes it to the bootloader so the appropriate drivers can be loaded and configured.
With device trees, you basically configure and build the drivers and configuration into the kernel/OS you're trying to load. That's why compiling Linux on amd64 is generally easy and produces a single image, while for many other devices (smartphones, some SBCs) you need to compile a kernel per device. The device trees only need to be imported/written once per device (or device type, depending on how nice the manufacturers are), but that's how you get stuff like this: https://github.com/torvalds/linux/tree/master/arch/arm64/boo...
On ARM there are actually a few devices that implement UEFI, but most of them have Secure Boot locked in and configured to only boot Windows.
ACPI is not perfect and it's not technically required to have UEFI to implement something better than device trees, but I'm not sure if reinventing the wheel here is necessary or even preferable. UEFI already has open source implementations ready to go, with kernels and other tools already containing code to interact with those APIs, whereas a custom ACPI replacement protocol would need more implementation work,
-
Maestro: A Linux-compatible kernel in Rust
The Linux Kernel Driver Interface
(all of your questions answered and then some)
https://github.com/torvalds/linux/blob/master/Documentation/...
-
Uniting the Linux random-number devices
A bit later another commit [1] was merged that makes reads from /dev/urandom opportunistically initialize the RNG. In practice this has the same result as the reverted commit on non-obsolete architectures, which do have a cycle counter and thus jitter entropy.
[1] https://github.com/torvalds/linux/commit/48bff1053c172e6c7f3...
The commit [1] was eventually reverted [2]
[1] https://github.com/torvalds/linux/commit/6f98a4bfee72c22f50a...
-
Linux: Ext4 data corruption in 6.1.64-1
Here's my understanding so far:
In the upstream Linux kernel there were two fixes posted months from each other, one for direct io [0] and the other one for ext4 [1]. The ext4 one was marked for backport to stable (CC: [email protected]), the other was not. The problem is that these commits depend on each other for things to work properly. If you have both, you're fine. If you have only the backported one, you have a problem.
What versions are affected? We know for sure that 6.1.64 is affected, 6.1.55 is not (because it doesn't have the commit). As of right now, 6.1.64 is still marked as "stable" in Debian [2] but if you actually try to install it from the official mirrors (deb.debian.org), you will get error 403. The fix is included in version 6.1.66 which will soon be available.
The issue seems to be only highlighted in the context of Debian but it is not specific to it. The issue is/was in the official upstream release.
[0] https://github.com/torvalds/linux/commit/936e114a245b6e38e0d...
What are some alternatives?
Zabbix - Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud.
zen-kernel - Zen Patched Kernel Sources
cadvisor - Analyzes resource usage and performance characteristics of running containers.
LibreNMS - Community-based GPL-licensed network monitoring system
ElastiFlow - Network flow analytics (Netflow, sFlow and IPFIX) with the Elastic Stack
Munin - Main repository for munin master / node / plugins
Nagios - Nagios Core
node_exporter - Exporter for machine metrics
DS4Windows - Like those other ds4tools, but sexier
Performance Co-Pilot - Performance Co-Pilot
truenas-influxdb-grafana - TrueNAS customized dashboard using Grafana and InfluxDb time series database
Icinga2