The open-source observability platform everyone needs!
GPL-3.0 License
Bot releases are visible (Hide)
Published by netdatabot over 3 years ago
Release v1.29.3 is a patch release to improve the stability of the Netdata Agent.
We discovered a bug that when proc.plugin
attempts to collect the operstate
parameter for a virtual network interface. If the chart is obsoleted, the Netdata Agent crashes. This bug was fixed in #10667. We're grateful to @gaia for first identifying this issue and working with our engineers, along with @sdellenb, to provide logs and point us toward the source of the bug.
This release also contains additional bug fixes and improvements.
Published by netdatabot over 3 years ago
Release v1.29.2 is a patch release to improve the stability of the Netdata Agent.
We discovered that an improvement introduced in v1.29.0 could inadvertently set all os_*
host labels to unknown
, which could affect users who leverage these host labels to organize their nodes, deploy health entities, or export metrics to external time-series databases. This bug was fixed in #10647.
This release also contains additional bug fixes and improvements.
app_groups.conf
file.API URL
configurable. (#10561, @tinyhammers)k8s_cluster_id
host label. (#10588, @ilyam8)apps.plugin
aggregation debug messages. (#10645, @vlvkobal)apps_groups.conf
. (#10621, @fayak)web/gui/readme.md
. (#10623, @OdysLam)CapabilityBoundingSet
workaround to the python.d collectors (that use sudo
). (#10587, @ilyam8)scheme
option in the Elasticsearch collector. (#10572, @vjt)system-info.sh
script. (#10647, @ilyam8)ipv4_tcp_resets
alarms. (#10644, @ilyam8)REMOVED
alarm status via ACLK if the previous status was WARN
/CRIT
. (#10533, @stelfrag)Published by netdatabot over 3 years ago
Release v1.29.1 is a hotfix release to address a crash in the Netdata Agent.
A locking bug in one of the internal collectors in Netdata could cause it to crash during shutdown in a way that would result in the Netdata Agent taking an excessively long time to exit.
Published by netdatabot over 3 years ago
The v1.29.0 release of the Netdata Agent is a maintenance release that brings incremental but necessary improvements that make your monitoring experience more robust. We've pushed improvements and bug fixes to the installation and update scripts, enriched our library of collectors, and focused on fixing bugs reported by the community.
This release contains 2 new collectors, the migration of 3 collectors from Python to Go, 25 other improvements, 25 documentation updates, and 26 bug fixes.
Netdata now collects and meaningfully organizes metrics from both the Couchbase JSON document database and the nginx-module-vts
module for exposing metrics about NGINX virtual hosts. Click either of the links to head straight into the documentation that explains what they collect and how to configure both based on whether they're collecting over localhost
or across nodes.
We've also migrated more collectors from Python to Go in our continued efforts to make data collection faster and more robust. The newest effort includes our Redis, Pika, and Energi Core Wallet collectors.
On the dashboard, we improved the responsiveness of panning forward and backward through historical metrics data by preventing unnecessary updates and reducing the number of calls. The charts should also now immediately update when you stop panning.
hddtemp
collector.diskplace
plugin.nginxvts
collectorcouchbase
collectorprometheus
collector default configurationapps
and cgroups
collectors. (#10479, @vlvkobal)_is_k8s_node
label to the host labels. (#10501, @Ilyam8)diskspace
plugin. (#10441, @nabijaczleweli)socket-io
dependency. (#10557, @jacekkolasa)redis
collector. (go.d.plugin#518, @Ilyam8)pika
collector. (go.d.plugin#518, @Ilyam8)energis
collector. (go.d.plugin#524, @thiagoftsm)nginxvts
collector. (go.d.plugin#523, @ski2per)couchbase
collector. (go.d.plugin#530, @hamedbrd)prometheus
collector default configuration. (go.d.plugin#539, @g3offrey)expected_prefix
configuration option to the prometheus
collector. (go.d.plugin#541, @Ilyam8)filecheck
collector. (go.d.plugin#538, @Ilyam8)$TMPDIR
from installer to updater. (#10384, @Ferroin)netdata
for debugging. (#10425, @Steve8291)systemd-detect-virt
. (#10569, @cakrit)prometheus
collector (go.d.plugin#537, @Ilyam8)mysql.slave_status
alarm for go mysql collector (#10513, @Ilyam8)Published by netdatabot almost 4 years ago
Release v1.28.0 is a hotfix release to address a deadlock in the Netdata Agent. We intended to release this hotfix as v1.27.1
, but we can't backtrack on a release once we've begun to publish new Docker images and binary packages on other platforms.
If the Agent-Cloud link (ACLK) connection drops and the Agent fails to queue an on_connect
message, it also fails to properly release a lock in the web server thread.
Published by netdatabot almost 4 years ago
The v1.27.0 release of the Netdata Agent brings dramatic improvements to long-term metrics storage via the database engine, and new dashboard features like a time & date picker for visualizing precise timeframes. Two new collectors bring incredible new value to existing features, including a bit of machine learning magic.
This release contains 8 new collectors, 1 new notification method (2 others enhanced), 54 improvements, 41 documentation updates, and 58 bug fixes.
The Netdata Agent now uses SQLite to store host, chart, and dimension metadata. This replaces the only metadata log files, which were located inside of the /var/cache/netdata/dbengine
folder for both multihost and legacy children nodes streaming to a parent node. With SQLite powering the metadata log, you should notice faster Agent startups, as it no longer needs to replay metadata log files. The Agent no longer puts archived charts into memory on startup, further reducing memory usage. This is just the first of several improvements to the database engine and metadata log, with more coming in future releases.
The database engine now uses a new extent cache that improves query time by 10% under certain workloads and reduces disk I/O by 10%.
The Netdata Agent's local dashboard has received numerous improvements and bugfixes since v1.26. Perhaps most prominent is the new time & date picker, which helps you select precise timeframes when investigating an anomaly or troubleshooting an incident. See the dashboard repository's releases for the full changelog.
We also introduced two new collectors that monitor the Netdata Agent itself in unique ways. First is the anomalies collector, which uses machine learning (ML) to perform unsupervised anomaly detection on a node running the Netdata Agent. This collector trains itself to understand the baseline of specific charts, then charts anomalous data. A new alarms collector visualizes the volume of Netdata alarms triggered over time.
web_client.c
, which our team resolved within 24 hours.varnish
collector.varnish
collector.oracledb
collector.haproxy
collector README.nvidia_smi
collector.rabbitmq
collector.libreswan
collector parsing.hpssa
collector.web_log
collector.web_log
collector.filecheck
collector.plugin
and module
health entities. (#10041, @thiagoftsm)allow_past
. (#10112, @stelfrag)tcp_sendmsg
, tcp_retransmit_skb
, tcp_cleanup_rcv
, udp_sendmsg
, udp_recvmsg
functions charts to the eBPF collector. (#10360, @thiagoftsm)varnish
collector. (#10329, @thiagoftsm)varnish
collector. (#10317, @ernestojpg)crit
from unmatched alarms in the web_log
collector. (#10280, @ilyam8)nvidia_smi
collector) to dashboard_info.js
. (#10230, @ilyam8)oracledb
collector. (#10197, @jurgenhaas)nvidia_smi
collector. (#10098, @scatenag)rabbitmq
collector. (#10064, @fayak)hpssa
collector. (#10093, @martinpal)cgroups
collector default filtering by adding pod level cgroups. (#10095, @ilyam8)couchdb
). (go.d.plugin/#453, @vlvkobal)web_log
collector. (go.d.plugin/#458, @ilyam8)web_log
collector. (go.d.plugin/#467, @hamedbrd)powerdns
). (go.d.plugin/#501, @ilyam8)powerdns_recursor
). (go.d.plugin/#495, @ilyam8)dnsdist
). (go.d.plugin/#504, @thiagoftsm)dnsmasq
). (go.d.plugin/#503, @ilyam8)filecheck
collector. (go.d.plugin/#487, @ski2per)systemdunits
collector. (go.d.plugin/#502, @ilyam8)web_log
collector. (go.d.plugin/#514, @ilyam8)glibtoolize
on macOS instead of regular libtoolize
. (#10346, @Ferroin)1.0.5-netdata2
. (#10158, @Ferroin)python.d
plugin PR checklist README section. (#10302, @andrewm4894)bug_report.md
. (#10269, @OdysLam)CONTRIBUTING.md
with new meta title. (#10252, @joelhans)kickstart.sh
. (#10396, @Ferroin)used_file_descriptors
alarm. (#10328, @ilyam8)nvidia_smi
collector. (#10312, @ilyam8)nvidia_smi
collector. (#10268, @ilyam8)cached
to used
dimension. (#10183, @mfundul)libreswan
collector. (#10190, @wash2)python.d plugin
runtime chart creation. (#10296, @ilyam8)rrdset_first_entry_t()
and rrdset_last_entry_t()
. (#10276, @mfundul)elasticsearch_last_collected
alarm. (#10226, @ilyam8)xenstat.plugin
. (#10224, @ilyam8)web_log
collector. (go.d.plugin/#462, @hamedbrd)go.d.plugin
(go.d.plugin#460, @ilyam8)mysql
collector (go.d.plugin#465, @ilyam8)unbound
collector (go.d.plugin#478, @ilyam8)unbound
collector (go.d.plugin#480, @ilyam8)go.d.plugin
(go.d.plugin#472, @ilyam8)mysql
collector (go.d.plugin#498, @ilyam8)Netsplits
chart dimensions algorithm in the the vernemq
collector. (go.d.plugin#511, @ilyam8)dashboard_info.js
for VerneMQ. (#10223, @ilyam8)Published by netdatabot about 4 years ago
The v1.26.0 release of the Netdata Agent brings exciting new collectors written in Go, a new integration with the DevOps startup StackPulse, and massive improvements to the way users navigate Netdata's documentation. We've also added compatibility with an exciting new feature that's coming soon to Netdata Cloud—stay tuned!
This release contains 3 new collectors, 1 new notifcation method, 21 improvements, 13 documentation updates, and 12 bug fixes.
The Netdata Agent can now collect metrics from files/directories, systemd units, and ISC DHCP servers. These new collectors are part of our larger effort to migrate all collectors to Go, which provides more extensibility compared to previous implementations. You can read about each of these new collectors in our docs: filecheck, systemd, isc_dhcpd.
We're excited to extend our health watchdog even further to integrate with StackPulse, which is designed to help SREs manage and respond to incidents with code and automation. You can read more about how to configure Netdata to send notifications to StackPulse in the docs.
We rearchitected our docs/education site, Netdata Learn, to focus on users actions rather than the Netdata Agent's hierarchy of code. The core docs now better guide users through the most important actions, such as configuring collectors and interacting with charts, independent of whether they use only the Netdata Agent, or the Agent in combination with Netdata Cloud. Of course, all of our reference documentation is still alive and kicking for those who want to dive into every configuration option or API query. We also revamped our guides page with better visuals, a search/filter, and more rational categories.
We're grateful to the Netdata community for their contributions for this release.
proc.plugin
).go.d.plugin/web_log
collector.python.d/rabbitmq
.python.d/rabbitmq
. (#10031, @chadknutson)failed
dim to the connection_fails
alarm in the Portcheck alarm. (#10048, @ilyam8)-W buildinfo
. (#9936, @underhood)v0.23.0
. (#10046, @ilyam8)
NETDATA_PORT
to NETDATA_LISTENER_PORT
. (#10045, @knatsakis)/etc/cron.d
for auto-updates. (#9598, @Ferroin)nolock
when debugging. (#10036, @andrewm4894)uuidgen
. (#9925, @OdysLam)docsv2
documents. (#10015, @joelhans)docsv2
project to master branch. (#10000, @joelhans)mirrored_hosts_status
into Swagger docs. (#9867, @underhood)proc.plugin
). (#10013, @Saruspete)go.d.plugin/web_log
collector. (#10029, @hamedbrd)Published by netdatabot about 4 years ago
The v1.25.0 release of the Netdata Agent is focused on improving Netdata's usability across the board. We added more customization to how the Prometheus collector implemented in v1.24 meaningfully visualizes metrics. In addition, we've focused on fixing bugs and ensuring that core functionality of the Netdata Agent, such as the ACLK, works more efficiently.
This release contains 1 new collector, 27 improvements, 15 documentation updates, and 59 bug fixes.
Improved filtering and grouping for the Prometheus collector gives you more flexibility in how Netdata collects and visualizes metrics from more than 600 Prometheus endpoints. The Prometheus collector is designed to visualize every metric exposed on a Prometheus endpoint generically, but one chart for every metric is often not the most meaningful presentation. Filtering and grouping options bring the same "bespoke" feeling that you find in our other collectors, such as having input/output metrics on a single chart instead of two.
You can read about filtering and grouping in our documentation right now. If you haven't heard about the generic Prometheus collector, read our v1.24 blog post for details on why we continuously make Netdata more interoperable with other monitoring solutions.
We also made significant improvements to the robustness and responsiveness of the Agent-Cloud link (ACLK), which is used to stream metrics and alarm status if you sign up for Netdata Cloud and claim your nodes. The disconnect and reconnect process is now more reliable, and all metrics data is now Gzip compressed. Now that the payloads are smaller and more quickly processed, you'll see improved responsiveness when viewing dashboards in Netdata Cloud.
We added a new Elasticsearch collector, written in Go, to help you collect metrics from and monitor Elasticsearch instances. This collector is preinstalled with the Netdata Agent and often works with zero configuration, but can also be tweaked to collect only specific stats, gather metrics with TLS, and more. See the documentation for generated charts and configuration options.
We're grateful to the Netdata community for a huge wave of contributions for this release.
go.d/web_log
collector.go.d/phpfpm
collector.python.d/isc_dhcpd
collector.netdata
user.netdata-installer.sh
to enable Netdata Cloud support in macOS.system-info.sh
.python.d/dnsdist
collector.proc.plugin
to collect the active processes limit on Linux systems.python.d/openldap
collector.python.d/varnish
collector for multiple storage backends.claimed_id
for child nodes streamed to their parents (#9804, @underhood)netdata-installer.sh
to enable Netdata Cloud support in macOS (#9360, @mrbrutti)ebpf.plugin
(#9591, @thiagoftsm)maxmemory
to python.d/redis
(#9767, @ilyam8)python.d/varnish
(#9668, @florianmagnin)Edit this page
link in simple patterns doc (#9847, @joelhans)netdata
user (#9555, @mrbarletta)/api/v0/stats/repo
endpoint by default (#9687, @ilyam8)netdata-uninstaller.sh
to correctly state whether the group was deleted (#9835, @michmach)REINSTALL_OPTIONS
(#8808, @prologic)system-info.sh
(#9882, @weijing24)python.d/dnsdist
(#9871, @scottymuse)python.d/openldap
collector (#9853, @scatenag)Published by netdatabot about 4 years ago
The v1.24.0 release of the Netdata Agent brings enhancements to the breadth of metrics we collect with a new generic Prometheus/OpenMetrics collector and enhanced storage and querying with a new multi-host database mode.
This release broadens our commitment to open standards, interoperability, and extensibility with a new generic Prometheus collector that works seamlessly with any application that makes its metrics available in the Prometheus/OpenMetrics exposition format, including support for Windows 10 via windows_exporter. Netdata will autodetect over 600 Prometheus endpoints and instantly generate charts with all the exposed metrics, meaningfully visualized.
The Netdata Agent database engine enables long-term storage of per-second metrics inside the Agent using both RAM and disk space. In our new, multi-host database mode, parent and child nodes share resources in a single instance. Any pre-existing child node metrics remain in the legacy dbengine paths to ensure backward compatibility. To migrate those nodes to the new multi-host DB, simply delete those metric cache paths. This new mode supports distributed queries for the Agent as well as specific scenarios like streaming metrics from the child to parent database, streaming multiple child nodes to a single parent, and remembering which child or children are connected to the database even if streaming hasn't started.
/run/netdata
. (#9613, @Ferroin)current_time_ms_from_date
on macOS (#9636, @ilyam8)status\n
response (#9610, @ilyam8)-t
option for timeout
(#9568, @ilyam8)Published by netdatabot over 4 years ago
Release v1.23.2 of the Netdata Agent is a patch for one significant issue.
PR #9491 fixed a buffer overrun vulnerability in Netdata's JSON parsing code. This vulnerability could be used to crash Agents remotely, and in some circumstances, could be used in an arbitrary code execution (ACE) exploit.
We strongly encourage all Netdata users to update their nodes to v1.23.2 as soon as possible.
This release also contains additional bug fixes and improvements.
netdata-installer.sh
.my.cnf
parameter when monitoring MySQL.my.cnf
parameter (#9526, @anirudhdggl)Published by netdatabot over 4 years ago
Release v1.23.1 of the Netdata Agent is a patch for two significant issues.
PR #9436 fixed an issue where dimensions were marked obsolete and archived simultaneously, which caused segmentation faults. We're grateful to marioem, who first reported the issue, and other members of the Netdata community who contributed their insights and valuable log information, which we used to diagnose and fix the bug.
PR [#9428] fixed a significant issue with duplicate alarm IDs, which caused issues in how alarms were sent and displayed in Netdata Cloud.
This release also contains a few additional bug fixes that were not fully reviewed before the release of v1.23.0.
Published by netdatabot over 4 years ago
The v1.23.0 release of the Netdata Agent is all about unlocking new depths of visibility for your applications, services, and systems. We have Kubernetes service discovery, new eBPF metrics like virtual filesystem switch and bandwidth per process out of the Linux kernel at event frequency, more interoperability with your monitoring stack thanks to a new exporting engine, and much more.
This release contains 2 new collectors, 1 new exporting connector, 1 new alarm notification method, 55 improvements, 45 documentation updates, and 40 bug fixes.
Our service discovery collector detects Kubernetes (k8s) pods and immediately collects metrics from 22 different services as the associated pods are created, destroyed, and scaled. Service discovery is installed when you use our Helm chart, which means you can now collect and visualize service-, pod-, Kubelet-, kube-proxy-, and node-level k8s metrics with one helm install
command and zero configuration. All our Kubernetes monitoring components are open source and free for clusters of any size.
Our low-level Linux kernel monitoring via eBPF is now supercharged. Thanks to an integration with apps.plugin
, you can now monitor how a specific application interacts with the Linux kernel. This update also includes new metrics, such as virtual filesystem switch, bandwidth per process, and much more. Netdata collects these metrics at an event frequency, even better than our famous 1s granularity, so that you can debug applications or anomalies with pinpoint accuracy. The eBPF collector is also now installed and enabled by default except on static builds.
Read our guide on troubleshooting apps with eBPF metrics for more details.
Netdata is now more interoperable with your existing monitoring stack thanks to the exporting engine, which replaces the backends system. You can now export to multiple external databases through Graphite, Google Cloud Pub/Sub, Prometheus remote write, MongoDB, and JSON connectors, plus others. Send metrics as soon as they're collected to enrich single pane of glass views or analyze Netdata's metrics with machine learning.
Read our guide on exporting metrics to Graphite for specifics on just one of many pipelines you can set up to archive your Netdata metrics.
We're also releasing an improvement for the availability of your monitoring and metrics: persistent metadata. The Agent now writes metadata to disk alongside metrics to allow access to non-active charts from Netdata Cloud and enable future features.
We added some enhancements to our documentation site, including a new guides section. We'll continue to populate with more use case- and scenario-based content to help you monitor, troubleshoot, visualize, and export your Netdata metrics.
mem.kernel
chart.dash.html
custom dashboard.dash.html
. (#8762) by tnyeanderson
agent-service-discovery
collector plugin to apps_group.conf
. (#9315) by ilyam8
apps_groups.conf
. (#9284) by thiagoftsm
kickstart-static64.sh
). (#8879) by prologic
ebpf.plugin
and apps.plugin
. (#9178) by thiagoftsm
system-info.sh
to better handle certain cases when gathering info on the system's disk capacity. (#7902) by Ferroin
sudo
when not running as the root user. (#9038) by Duffyx
ebpf_process.plugin
to ebpf.plugin
. (#8822) by thiagoftsm
varnish
collector. (#8940) by pgjavier
install-required-packages.sh
. (#8286) by Ferroin
kickstart.sh
/kickstart-static64.sh
installation scripts. (#9165) by prologic
nc
backend to exporting. (#9030) by thiagoftsm
kickstart-static64.sh
). (#9130) by prologic
of
and foreach
options in lookup line. (#9255) by underhood
README.md
. (#9205) by Steve8291
README.md
. (#9151) by stephenrauch
docker run
instruction in claiming document. (#9058) by ilyam8
netdatalib
and netdatacache
volumes to the Docker-with-Caddy documentation. (#8999) by webash
UNUSED
from flood protection configuration options documentation. (#8964) by mfundul
opentsdb:https
and another connector were enabled together. (#9389) by vlvkobal
assert()
calls with new fatal_assert()
. (#9349) by mfundul
--disable-cloud
flag. (#9337) by stelfrag
--enable-ebpf
flag. (#9310) by Ferroin
netdata.conf
. (#9174) by Ferroin
install-required-packages.sh
to help users submit a GitHub issue. (#8911) by prologic
netdata
service in Debian package. (#9005) by MrFreezeex
SIGCHLD
signal handler. (#9107) by mfundul
netdata.conf
when updating. (#9046) by Ferroin
mem.kernel
chart. (#9096) by Neamar
.json
file. (#8814) by dpsy4
ram_in_use
and used_ram_to_ignore
in systems using ZFS. (#8913) by araemo
Published by netdatabot over 4 years ago
Release v1.22.1 is a hotfix release to address issues related to packaging and how Agents connect to Netdata Cloud.
With packaging, we fixed an error that caused DEB and RPM packages to only display the old dashboard and not the new React version. We also fixed an issue that caused Netdata Docker containers to fail due to incorrect permissions. Finally, we ensured JSON-C is correctly fetched and built for compatibility with Netdata Cloud.
We appreciate our community's help in identifying and diagnosing these issues so we could fix them quickly.
For Netdata Cloud, we optimized the on-connect payload sent through the Agent-Cloud link to improve latency between Agents and Cloud. We also removed a check for old alarm status when sending alarms to Cloud via the ACLK.
Finally, we made a fix that ensures Agents running on systems using the musl C library can receive auto-updates.
Published by netdatabot over 4 years ago
Release v1.22.0 marks the official launch of our rearchitected Netdata Cloud! This Agent release contains both backend and interface changes necessary to connect your distributed nodes to this dramatically improved experience.
Netdata Cloud builds on top of our open source monitoring Agent to give you real-time visibility for your entire infrastructure. Once you've connected your Agents to Cloud, you can view key metrics, insightful charts, and active alarms from all your nodes in a single web interface. When an anomaly strikes, seamlessly navigate to any node to troubleshoot and discover the root cause with the familiar Netdata dashboard.
Sign in to Cloud and read our Get started with Cloud guide for details on updating your nodes, claiming them, and navigating the new Cloud.
While Netdata Cloud offers a centralized method of monitoring your Agents, your metrics data is not stored or centralized in any way. Metrics data remains with your nodes and is only streamed to your browser through Cloud.
In addition, Cloud only expands on the functionality of the wildly popular free and open source Agent. We will never make any of our open source Agent features Cloud-exclusive, and we will actively continue to develop the Agent so that we can integrate new features with Netdata Cloud.
This release also contains 1 new collector, 1 new exporting connector, 1 new alarm notification method, 27 improvements, 16 documentation updates, and 22 bug fixes.
We added a new collector called whoisquery
that helps you monitor a domain name's expiration date. You can track as many domains as you'd like, and set custom warning and critical thresholds for each. For more information on setup and configuration, see the Whois domain expiry monitoring documentation.
We added a new connector to our experimental exporting engine: Prometheus remote write. You can use this connector to send Netdata metrics to your choice of more than 20 external storage providers for long-term archiving and further analysis.
Our new documentation experience is now available at Netdata Learn! We encourage you to try it out and give us feedback or ask questions in our GitHub issues. Learn features documentation for both the Agent and Cloud in separate-but-connected vaults, which streamlines the experience of learning about both products.
While Learn only features documentation for now, we plan on releasing more types of educational content serving the Agent's open-source community of developers, sysadmins, and DevOps folks. We'll have more to announce soon, but in the meantime, we hope you enjoy what we believe is a smoother (and prettier) docs experience.
netdata.conf
and netdata.service.v235.in
.netdata-installer.sh
.docs.netdata.cloud
) was replaced with Netdata Learn. All existing backlinks redirect to the new site.session-id
to ACLK using connect timestamp. (#8633) by amoss
apps.plugin
. (#8592) by vlvkobal
NETDATA_STOP_CMD
in netdata-installer.sh
. (#8897) by prologic
document-start
yamllint check. (#8522) by ilyam8
bind to
to [web]
section and update netdata.service.v235.in
to sync it with recent changes. (#8454) by amishmm
learn.netdata.cloud
. (#8936) by joelhans
charts.d.conf
. (#8740) by Jiab77
mkdocs-material
to re-enable Netlify builds of documentation site. (#8639) by joelhans
README.md
with v1.21 release news. (#8619) by joelhans
cron
symlink. (#8849) by prologic
netdata-installer.sh
. (#8811) by adamwolf
bundle-dashboard.sh
script to prevent broken package builds. (#8823) by prologic
failed devices
alarm. (#8752) by ilyam8
no-clear-notification
options from portcheck health templates. (#8748) by ilyam8
system-info.sh
regarding the parsing of lscpu
output. (#8754) by Ferroin
threads_creation_rate
chart context in the python.d MySQL collector. (#8636) by ilyam8
install-requred-packages.sh
on certain Linux systems. (#8606) by ilyam8
sudo
check in charts.d libreswan collector to prevent daily security notices. (#8569) by ilyam8
Published by netdatabot over 4 years ago
Release v1.21.1 is a hotfix release to improve the performance of the new React dashboard, which was merged and enabled by default in v1.21.0.
The React dashboard shipped in v1.21.0 did not properly freeze charts that were outside of the browser's viewport. If a user who loaded many charts by scrolling through the dashboard, charts outside of their browser's viewport continued updating. This excess of chart updates caused all charts to update more slowly than every second.
v.1.21.1 includes improvements to the way the Netdata dashboard freezes, maintains state, and restores charts as users scroll.
Published by netdatabot over 4 years ago
Release v1.21.0 contains 2 new collectors, 3 new exporting connectors, 37 bug fixes, 46 improvements, and 25 documentation updates. We also made 26 bug fixes or improvements related to the upcoming release of Netdata Cloud.
We added a new collector for Apache Pulsar, a popular open-source distributed pub-sub messaging system. We use Pulsar in our Netdata Cloud infrastructure (more on that later this month!), and are excited to start sharing metrics about our own Pulsar systems when the time comes. The Pulsar collector attempts to auto-detect any running Pulsar processes, but you can always configure the collector based on your setup.
Also new in v1.21 is a VerneMQ collector. We use the open-source MQ Telemetry Transport (MQTT) broker for Netdata Cloud as well. As with Pulsar, you can configure the VerneMQ collector to auto-detect your installation in just a few steps.
Our experimental exporting engine received significant updates with new connectors for Prometheus remote write, MongoDB, and AWS Kinesis Data Streams. You can now send Netdata metrics to more than 20 additional external storage providers for long-term archiving and deeper analysis. Learn more about the exporting engine in our documentation.
We upgraded our TLS compatibility to include 1.3, which applies to HTTPS for both Netdata's web server and streaming connections. TLS 1.3 is the most up-to-date version of the TLS protocol, and contains important fixes and improvements to ensure strong encryption. If you enabled TLS in the web server or streaming, Netdata attempts to use 1.3 by default, but you can also set the version and ciphers explicitly. Learn more in the documentation.
The Netdata dashboard has been completely re-written in React. While the look and behavior hasn't changed, these under-the-hood changes enable a suite of new features, UX improvements, and design overhauls. With React, we'll be able to work faster and better resource our talented engineers.
As part of the ongoing work to polish our eBPF collector tech preview, we've now proven the collector's performance is very good, and have vastly expanded the number of operating system versions the collector works on. Learn how to enable it in our documentation. We've also extensively stress-tested the eBPF collector and found that it's impressively fast given the depth of metrics it collects! Read up on our benchmarking analysis on GitHub.
\n
in various installation methods./var/
for .deb installations.kubectl
in bare-metal deployments.apps.plugin
.None.
idlejitter
. (#8441) by mfundul
dns_query
collector that detects DNS query failure. (#8434) by ilyam8
kubectl
in bare-metal deployments. (#7416) by WoozyMasta
install-required-packages.sh
. (#8339) by prologic
install-required-packages.sh
. (#8154) by Ferroin
README.md
. (#8547) by bceylan
install-required-packages.sh
. (#8347) by prologic
COLLECTORS.md
. (#8380) by ilyam8
README.md
. (#8335) by peroxy
CHANGELOG.md
more meaningful. (#8150) by cakrit
python.d
configuration files to YAML linting CI process and increase line limit to 120 characters. (#8541) and (#8542) by ilyam8
install-required-packages.sh
with Coverity scan. (#8388) by prologic
netdata
user by default, or override if necessary. (#8516) by amoss
info
endpoint for Cloud notifications. (#8519) by amoss
[agent_cloud_link]
settings to [cloud]
. (#8501) by underhood
timestamp-offset-usec
. (#8499) by stelfrag
claim.d
directory. (#8475) by amoss
make dist
. (#8275) by Ferroin
netdata-installer.sh
. (#8144) by Ferroin
/default.html
route. (#8599 by jacekkolasa
help-tooltips
styling, private registry node deletion, and the right-hand sidebar "jumping" on document clicks. (#8553 by jacekkolasa
netdata.service.*
to .gitignore
to hide system/netdata.service.v235
file. (#8556) by vlvkobal
apps.plugin
. (#8554) by vlvkobal
bytespersec
chart context in the Python Apache collector. (#8550) by ilyam8
charts.d.plugin
to exit properly during Netdata service restart. (#8529) by ilyam8
kickstart-static64.sh
) installs. (#8507) by prologic
\n
in uninstaller output. (#8446) by prologic
install-required-packages
script to self-update apt
. (#8491) by prologic
stop_all_netdata uv_pipe_connect()
in the installer. (#8444) by prologic
\n
in various installers. (#8324)/(#8325)/(#8326) by Jiab77
/var/
for .deb packages. (#8314) by SamK
osd_perf_infos
in versions 14.2 and higher. (#8248) by ilyam8
tmem
collection from xenstat_plugin to allow Netdata on Xen 4.13 to compile successfully. (#7951) by rushikeshjadhav
get_latest_version
for nightly channel update script. (#8172) by ilyam8
Published by netdatabot over 4 years ago
Release v1.20.0 contains 3 new collectors, 54 bug fixes, 89 improvements, and 38 documentation updates.
Our first major release of 2020 comes with an alpha version of our new eBPF collector. eBPF (extended Berkeley Packet Filter) is a virtual bytecode machine, built directly into the Linux kernel, that you can use for advanced monitoring and tracing.
With this release, the eBPF collector monitors system calls inside your kernel to help you understand and visualize the behavior of your file descriptors, virtual file system (VFS) actions, and process/thread interactions. You can already use it for debugging applications and better understanding how the Linux kernel handles I/O and process management.
The eBPF collector is in a technical preview, and doesn't come enabled out of the box. If you'd like to learn more about_why_ eBPF metrics are such an important addition to Netdata, see our blog post: Linux eBPF monitoring with Netdata. When you're ready to get started, enable the
eBPF collector by following the steps in our documentation.
This release also introduces host labels, a powerful new way of organizing your Netdata-monitored systems. Netdata automatically creates a handful of labels for essential information, but you can supplement the defaults by segmenting your systems based on their location, purpose, operating system, or even when they went live.
You can use host labels to create alarms that apply only to systems with specific labels, or apply labels to metrics you archive to other databases with our exporting engine. Because labels are streamed from slave to master systems, you can now find critical information about your entire infrastructure directly from the master system.
Our host labels tutorial will walk you through creating your first host labels and putting them to use in Netdata's other features.
Finally, we introduced a new CockroachDB collector. Because we use CockroachDB internally, we wanted a better way of keeping tabs on the health and performance of our databases. Given how popular CockroachDB is right now, we know we're not alone, and are excited to share this collector with our community. See our tutorial on monitoring CockroachDB metrics for set-up details.
We also added a new squid access log collector that parses and visualizes requests, bandwidth, responses, and much more. Our apps.plugin collector has new and improved way of processing groups together, and our cgroups collector is better at LXC (Linux
container) monitoring.
Speaking of collectors, we revamped our collectors documentation to simplify how users learn about metrics collection. You can now view a collectors quickstart to learn the process of enabling collectors and monitoring more applications and services with Netdata, and see everything Netdata collects in our supported collectors list.
We're extremely grateful to the following contributors for their help since our last major release in November 2019. Whether it's their first or fiftieth contribution, insights from our users not only help make Netdata better, but also remind us why we're so lucky to be part of a vibrant open-source community.
elastisearch
collector fix.freeipmi
support to our Docker image and lassebm for related fixes and documentation.httpcheck
collector.-fno-common
in CFLAGS.systemd
service files.litespeed
collector.softnet
alarm.configure
.bash
collectors apache
, cpu_apps
, cpufreq
, exim
, hddtemp
, load_average
, mem_apps
, mysql
, nginx
, phpfpm
, postfix
, squid
, tomcat
#7962 (ilyam8). If you were still using one of these collectors with custom configurations, you can find the new collector that replaces it in the supported collectors list.netdata.conf
#7451 #7458 (thiagoftsm)snmp.node.js
#7816 (ilyam8).rtreport
format #7705 (lucasRolff)nvidia-smi
in normal instead of loop mode #7372 (ilyam8)mktemp
so that they produce temporary directories in $TEMPDIR
instead of the current directory, in a way that is compatible with busybox. #8066 (Ferroin)go.d.plugin
, only if we have a new version #7946 (ilyam8)netdata
groups/users during uninstall (Debian postrm
) #7817 (prologic)systemd
service files, by removing unecessary ExecStartPre
lines and moving global options to netdata.conf
#7790 (amishmm)echo
calls from the updater. #7783 (Ferroin)dpkg-buildpackage
by modifying the formatting of the trailer line in the Debian changelog template. #7763 (Ferroin)/bin/sh
and removing use of sudo
#7725 (prologic)kickstart-static64
installations. #7704 (Ferroin)-f
option from groupdel
in uninstaller. #7507 (Ferroin)retroshare
collector readme #7849 (ilyam8)allmetrics
endpoint documentation #7776 (vlvkobal)buildyaml.sh
script so that docs generation works correctly. #7662 (Ferroin
libmosquitto
, netdata-cli
and other prerequisites:
-fno-common
in CFLAGS #7870 (#7877 (thiagoftsm)unbound
python collector (dead code) #7853 (ilyam8)dash.html
#7757 (tnyeanderson)uv_thread_set_name_np
from error to info. #7653 (Saruspete
invalid literal for float\(\): NN.NNt
error in the elasticsearch
python plugin, by adding terabyte unit parsing. #8013 (blaines)timeout
failing in docker containers which broke some python.d collectors #8002 (ilyam8)synology6
#7980 (ilyam8)httpcheck
python collector not being able to check URLs with the POST
method, by adding body
to the URLService
#7956 (ilyam8). Also record the new options in httpcheck.conf
#7952 (yasharne)netdata-updater.sh
appearing to fail #7955 (ilyam8)netdata-updater.sh
#7938 (prologic)edit-config
, when NetData is installed to a symlinked /opt
#7933 (prologic).keep
files #7829 (prologic)libuv
IPC pipe cleanup problem #7778 (mfundul)ROLE
was set to root
. #7769 (thiagoftsm)nfacct
plugin #7727 (vlvkobal)/lib
on SystemD systems like CoreOS in static build installation #7726 (prologic)invalid shell
installer error and netdata not starting from its installed location. #7698 (Ferroin)make install
. #7632 (Ferroin)broken pipe
error log entries, after a SIGKILL #7588 (thiagoftsm)cpuidle
plugin #7664 (Saruspete)sudo
#7655 (ilyam8)keys_redis
chart in the redis
collector, by populating keys at runtime #7639 (ilyam8)hpssa
collector #7580 (gnoddep)- Fixed race condition in dbengine #7565 (thiagoftsm)Published by netdatabot almost 5 years ago
Release v1.19.0 contains 2 new collectors, 19 bug fixes, 17 improvements, and 19 documentation updates.
We completed a major rewrite of our web log collector to dramatically improve its flexibility and performance. The new collector, written entirely in Go, can parse and chart logs from Nginx and Apache servers, and combines numerous improvements. Netdata now supports the LTSV log format, creates charts for TLS and cipher usage, and is amazingly fast. In a test using SSD storage, the collector parsed the logs for 200,000 requests in about 200ms, using 30% of a single core.
This Go-based collector also has powerful custom log parsing capabilities, which means we're one step closer to a generic application log parser for Netdata. We're continuing to work on this parser to support more application log formatting in the future.
We have a new tutorial on enabling the Go web log collector and using it with Nginx and/or Apache access logs with minimal configuration. Thanks to Wing924 for starting the Go rewrite!
We introduced more cmocka unit testing to Netdata. In this release, we're testing how Netdata's internal web server processes HTTP requests—the first step to improve the quality of code throughout, reduce bugs, and make refactoring easier. We wanted to validate the web server's behavior but needed to build a layer of parametric testing on top of the CMocka test runner. Read all about our process of testing and selecting cmocka on our blog post: Building an agile team's 'safety harness' with cmocka and FOSS.
Netdata's Unbound collector was also completely rewritten in Go to improve how it collects and displays metrics. This new version can get dozens of metrics, including details on queries, cache, uptime, and even show per-thread metrics. See our tutorial on enabling the new collector via Netdata's amazing auto-detection feature.
We fixed an error where invalid spikes appeared on certain charts by improving the incremental counter reset/wraparound detection algorithm.
Netdata can now send health alarm notifications to IRC channels thanks to Strykar!
And, Netdata can now monitor AM2320 sensors, thanks to hard work from Tom Buck.
Our thanks go to:
https://localhost:10250/metrics
. go.d.plugin/#285
http://kube-dns.kube-system.svc.cluster.local:9153/metrics
. go.d.plugin/#285
check xenstat_vbd_error
presence. #7103 (arkamar)cluster_status
alarm. #6989 (ilyam8)/etc/netdata
. #7244 (knatsakis)netdata-installer.sh
. #7200 (knatsakis)kickstart-static64.sh
and kickstart.sh
installations. #7262 (knatsakis)/var/run/netdata
for the unix socket, in running behind nginx documentation. #7206 (CtrlAltDel64)contrib/debian
descriptions for cupsd
. #7154 (arkamar)Makefile.am
. #7326 (oxplot)proc/pagetypeinfo
collection could under particular circumstances cause high CPU load. As a workaround, we disabled pagetypeinfo
by default. #7230 (vlvkobal)proc
plugin’s pagetypeinfo
collector. #7187 (thiagoftsm)"disk_free": "disk_free_monitoring_disabled"
error. #7226 (ilyam8)limits.h
before using LONG_MAX
. #7224 (mniestroj)UrlService
to skip tls_verify
for http scheme. #7223 (ilyam8)stable
option, so that the installers and automatic updater respect it. #7083 (knatsakis), #7051 (oxplot)--auto-update
option. #7076 (knatsakis)http://pi.hole
. go.d.plugin 289 (ilyam8)Published by netdatabot about 5 years ago
Release v1.18.1 contains 17 bug fixes, 5 improvements, and 5 documentation updates.
Patch release 1.18.1 contains several bug fixes, mainly related to FreeBSD and the binary package generation process.
Netdata can now send notifications to Google Hangouts Chat!
On certain systems, the slabinfo
plugin introduced in v1.18.0 added thousands of new metrics. We decided the collector's usefulness to most users didn't justify the increase in resource requirements. This release disables the collector by default.
Finally, we added a chart under Netdata Monitoring to present a better view of the RAM used by the database engine (dbengine). The chart doesn't currently take into consideration the RAM used for slave nodes, so we intend to add more related charts in the future.
We'd like to thank:
slabinfo
plugin by default to reduce the total number of metrics collected #7056 (vlvkobal)kickstart-static64.sh
) #7060 (knatsakis)api/v1/data
API responses. #7012 (amoss)mmap
fails - mostly with BSD kernels #7065 (mfundul)Published by netdatabot about 5 years ago
Release v1.18.0 contains 5 new collectors, 19 bug fixes, 28 improvements, and 20 documentation updates.
The database engine is now the default method of storing metrics in Netdata. You immediately get more efficient and configurable long-term metrics storage without any work on your part. By saving recent metrics in RAM and "spilling" historical metrics to disk for long-term storage, the database engine is laying the foundation for many more improvements to distributed metrics.
We even have a tutorial on switching to the database engine and getting the most from it. Or, just read up on how performant the database engine really is.
Both our python.d
and go.d
plugins now have more intelligent auto-detection by periodically dump a list of active modules to disk. When Netdata starts, such as after a reboot, the plugins use this list of known services to re-establish metrics collection much more reliably. No more worrying if the service or application you need to monitor starts up minutes after Netdata.
Two of our new collectors will help those with Hadoop big data infrastructures. The HDFS and Zookeeper collection modules come with essential alarms requested by our community and Netdata's auto-detection capabilities to keep the required configuration to an absolute minimum. Read up on the process via our HDFS and Zookeeper tutorial.
Speaking of new collectors—we also added the ability to collect metrics from SLAB cache, Gearman, and vCenter Server Appliances.
Before v1.18, if you wanted to create alarms for each dimension in a single chart, you need to write separate entities for each dimension—not very efficient or user-friendly. New dimension templates fix that hassle. Now, a single entity can automatically generate alarms for any number of dimensions in a chart, even those you weren't aware of! Our tutorial on dimension templates has all the details.
v1.18 brings support for installing Netdata on offline or air-gapped systems. To help users comply with strict security policies, our installation scripts can now install Netdata using previously-downloaded tarball and checksums instead of downloading them at runtime. We have guides for installing offline via kickstart.sh
or kickstart-static64.sh
in our installation documentation. We're excited to bring real-time monitoring to once-inaccessible systems!
Our thanks go to:
slabinfo
collector, that monitors SLAB cache mechanism metrics./api/vhosts
#6976 (ilyam8)kickstart.sh
or kickstart-static64.sh
#6693 (paulkatsoulakis)libuv
and judy
from source #6850 (paulkatsoulakis)grep
command in “high performance netdata” to be more specific #6794 (n0coast)family
into the allmetrics
JSON response #6966 (ilyam8)unhandled exception
log warnings in the python.d
collector orchestrator start\_job
#6928 (ilyam8)x-auth-token
in Access-Control-Allow-Headers
#6894 (cakrit)RRDSET: chart name 'XXX' on host 'YYY' already exists
, by changing the log level for chart updates #6887 (vlvkobal)/var/lib/netdata/registry
getting left behind after uninstall #6867 (davent)cppcheck
fixes #6386 (ac000)