mirror of
https://github.com/YunoHost-Apps/netdata_ynh.git
synced 2024-09-03 19:46:33 +02:00
Upgrade to upstream version 1.15.0 (#34)
* upgrade 1.15.0 (app.src file) * 1.15.0 uninstall script update. * Update README.md for 1.15.0 * manifest, update version to 1.15.0 sorry for tons of commit. gitlab web interface is better ^^. * Adapt to new configuration folder structure
This commit is contained in:
Narbonne
JimboJoe
parent
d248520c50
commit
9a3ab95d68
5 changed files with 360 additions and 165 deletions
504
README.md
504
README.md
|
|
@ -14,7 +14,7 @@ _netdata is **fast** and **efficient**, designed to permanently run on all syste
|
|||
(**physical** & **virtual** servers, **containers**, **IoT** devices), without
|
||||
disrupting their core function._
|
||||
|
||||
**Shipped version:** 1.12.2
|
||||
**Shipped version:** 1.15.0
|
||||
|
||||
**Customization brought by the package:**
|
||||
|
||||
|
|
@ -42,236 +42,424 @@ location /stub_status {
|
|||
|
||||
It has been tested on x86_64 and ARM.
|
||||
|
||||
## Features
|
||||
## Why Netdata
|
||||
|
||||
<p align="center">
|
||||
<img src="https://cloud.githubusercontent.com/assets/2662304/19168687/f6a567be-8c19-11e6-8561-ce8d589e8346.gif"/>
|
||||
</p>
|
||||
Netdata has a quite different approach to monitoring.
|
||||
|
||||
- **Stunning interactive bootstrap dashboards**<br/>
|
||||
mouse and touch friendly, in 2 themes: dark, light
|
||||
Netdata is a monitoring agent you install on all your systems. It is:
|
||||
|
||||
- **Amazingly fast**<br/>
|
||||
responds to all queries in less than 0.5 ms per metric,
|
||||
even on low-end hardware
|
||||
- a **metrics collector** - for system and application metrics (including web servers, databases, containers, etc)
|
||||
- a **time-series database** - all stored in memory (does not touch the disks while it runs)
|
||||
- a **metrics visualizer** - super fast, interactive, modern, optimized for anomaly detection
|
||||
- an **alarms notification engine** - an advanced watchdog for detecting performance and availability issues
|
||||
|
||||
- **Highly efficient**<br/>
|
||||
collects thousands of metrics per server per second,
|
||||
with just 1% CPU utilization of a single core, a few MB of RAM and no disk I/O at all
|
||||
All the above, are packaged together in a very flexible, extremely modular, distributed application.
|
||||
|
||||
- **Sophisticated alarming**<br/>
|
||||
hundreds of alarms, **out of the box**!<br/>
|
||||
supports dynamic thresholds, hysteresis, alarm templates,
|
||||
multiple role-based notification methods (such as email, slack.com,
|
||||
pushover.net, pushbullet.com, telegram.org, twilio.com, messagebird.com)
|
||||
This is how Netdata compares to other monitoring solutions:
|
||||
|
||||
- **Extensible**<br/>
|
||||
you can monitor anything you can get a metric for,
|
||||
using its Plugin API (anything can be a netdata plugin,
|
||||
BASH, python, perl, node.js, java, Go, ruby, etc)
|
||||
Netdata|others (open-source and commercial)
|
||||
:---:|:---:
|
||||
**High resolution metrics** (1s granularity)|Low resolution metrics (10s granularity at best)
|
||||
Monitors everything, **thousands of metrics per node**|Monitor just a few metrics
|
||||
UI is super fast, optimized for **anomaly detection**|UI is good for just an abstract view
|
||||
**Meaningful presentation**, to help you understand the metrics|You have to know the metrics before you start
|
||||
Install and get results **immediately**|Long preparation is required to get any useful results
|
||||
Use it for **troubleshooting** performance problems|Use them to get *statistics of past performance*
|
||||
**Kills the console** for tracing performance issues|The console is always required for troubleshooting
|
||||
Requires **zero dedicated resources**|Require large dedicated resources
|
||||
|
||||
- **Embeddable**<br/>
|
||||
it can run anywhere a Linux kernel runs (even IoT)
|
||||
and its charts can be embedded on your web pages too
|
||||
Netdata is **open-source**, **free**, super **fast**, very **easy**, completely **open**, extremely **efficient**,
|
||||
**flexible** and integrate-able.
|
||||
|
||||
- **Customizable**<br/>
|
||||
custom dashboards can be built using simple HTML (no javascript necessary)
|
||||
It has been designed by **SysAdmins**, **DevOps** and **Developers** for troubleshooting performance problems,
|
||||
not just visualize metrics.
|
||||
|
||||
- **Zero configuration**<br/>
|
||||
auto-detects everything, it can collect up to 5000 metrics
|
||||
per server out of the box
|
||||
## News
|
||||
|
||||
- **Zero dependencies**<br/>
|
||||
it is even its own web server, for its static web files and its web API
|
||||
`May 21st, 2019` - **[Netdata v1.15.0 released!](https://github.com/netdata/netdata/releases)**
|
||||
|
||||
- **Zero maintenance**<br/>
|
||||
you just run it, it does the rest
|
||||
Release v1.15.0 contains 11 bug fixes and 30 improvements.
|
||||
|
||||
- **scales to infinity**<br/>
|
||||
requiring minimal central resources
|
||||
We are very happy and proud to be able to include two major improvements in this release: The aggregated node view and the [new database engine](https://docs.netdata.cloud/database/engine/).
|
||||
|
||||
- **several operating modes**<br/>
|
||||
autonomous host monitoring, headless data collector, forwarding proxy, store and forward proxy, central multi-host monitoring, in all possible configurations.
|
||||
Each node may have different metrics retention policy and run with or without health monitoring.
|
||||
*Aggregated node view*
|
||||
|
||||
- **time-series back-ends supported**<br/>
|
||||
can archive its metrics on `graphite`, `opentsdb`, `prometheus`, json document DBs, in the same or lower detail
|
||||
(lower: to prevent it from congesting these servers due to the amount of data collected)
|
||||
The No. 1 request from our community has been a better way to view and manage their Netdata installations, via an aggregated view. The node menu with the simple list of hosts on the agent UI just didn't do it for people with hundreds, or thousands of instances. This release introduces the node view, which uses the power of [Netdata Cloud](https://blog.netdata.cloud/posts/netdata-cloud-announcement/) to deliver powerful views of a Netdata-based monitoring infrastructure. You can read more about Netdata Cloud and the future of Netdata [here](https://blog.netdata.cloud/posts/netdata-cloud-announcement/).
|
||||
|
||||
|
||||
*New database engine*
|
||||
|
||||
Historically, Netdata has required a lot of memory for long-term metrics storage. To mitigate this we've been building a new DB engine for several months and will continue improving until it can become the default `memory mode` for new Netdata installations. The version included in release v1.15.0 already permits longer-term storage of compressed data and we'll continue reducing the required memory in following releases.
|
||||
|
||||
*Other major additions*
|
||||
|
||||
We have added support for the [AWS Kinesis backend](https://docs.netdata.cloud/backends/aws_kinesis/) and new collectors for [OpenVPN](https://docs.netdata.cloud/collectors/go.d.plugin/modules/openvpn/), the [Tengine web server](https://docs.netdata.cloud/collectors/go.d.plugin/modules/tengine/), [ScaleIO (VxFlex OS)](https://docs.netdata.cloud/collectors/go.d.plugin/modules/scaleio/), [ioping-like latency metrics](https://docs.netdata.cloud/collectors/ioping.plugin/) and [Energi Core node instances](https://docs.netdata.cloud/collectors/python.d.plugin/energid/).
|
||||
|
||||
We now have a new, ["text-only" chart type](https://github.com/netdata/netdata/issues/5578), [cpu limits for v2 cgroups](https://github.com/netdata/netdata/issues/5850), [docker swarm metrics](https://docs.netdata.cloud/collectors/go.d.plugin/modules/docker_engine/) and improved [documentation](https://docs.netdata.cloud/).
|
||||
|
||||
We continued improving the [Kubernetes helmchart](https://github.com/netdata/helmchart) with liveness probes for slaves, persistence options, a fix for a `Cannot allocate memory` issue and easy configuration for the kubelet, kube-proxy and coredns collectors.
|
||||
|
||||
Finally, we built a process to quickly replace any problematic nightly builds and added more automated CI tests to prevent such builds from being published in the first place.
|
||||
|
||||
---
|
||||
|
||||
## What does it monitor?
|
||||
`Apr 26th, 2019` - **[Netdata v1.14.0 released!](https://github.com/netdata/netdata/releases)**
|
||||
|
||||
netdata collects several thousands of metrics per device.
|
||||
All these metrics are collected and visualized in real-time.
|
||||
Release 1.14 contains 14 bug fixes and 24 improvements.
|
||||
|
||||
> _Almost all metrics are auto-detected, without any configuration._
|
||||
The release introduces major additions to Kubernetes monitoring, with tens of new charts for [Kubelet](https://docs.netdata.cloud/collectors/go.d.plugin/modules/k8s_kubelet/), [kube-proxy](https://docs.netdata.cloud/collectors/go.d.plugin/modules/k8s_kubeproxy/) and [coredns](https://github.com/netdata/go.d.plugin/tree/master/modules/coredns) metrics, as well as significant improvements to the Netdata [helm chart](https://github.com/netdata/helmchart/).
|
||||
|
||||
Two new collectors were added, to monitor [Docker hub](https://docs.netdata.cloud/collectors/go.d.plugin/modules/dockerhub/) and [Docker engine](https://docs.netdata.cloud/collectors/go.d.plugin/modules/docker_engine/) metrics.
|
||||
|
||||
This is a list of what it currently monitors:
|
||||
Finally, v1.14 adds support for [version 2 cgroups](https://github.com/netdata/netdata/pull/5407), [OpenLDAP over TLS](https://github.com/netdata/netdata/pull/5859), [NVIDIA SMI free and per process memory](https://github.com/netdata/netdata/pull/5796/files) and [configurable syslog facilities](https://github.com/netdata/netdata/pull/5792).
|
||||
|
||||
- **CPU**<br/>
|
||||
usage, interrupts, softirqs, frequency, total and per core, CPU states
|
||||
---
|
||||
|
||||
- **Memory**<br/>
|
||||
RAM, swap and kernel memory usage, KSM (Kernel Samepage Merging), NUMA
|
||||
`Mar 14th, 2019` - **[Netdata v1.13.0 released!](https://github.com/netdata/netdata/releases)**
|
||||
|
||||
- **Disks**<br/>
|
||||
per disk: I/O, operations, backlog, utilization, space, software RAID (md)
|
||||
Release 1.13.0 contains 14 bug fixes and 8 improvements.
|
||||
|
||||
|
||||
Netdata has taken the first step into the world of Kubernetes, with a beta version of a [Helm chart](https://github.com/netdata/helmchart) for deployment to a k8s cluster and [proper naming](https://github.com/netdata/netdata/pull/5576) of the cgroup containers. We have [big plans](https://github.com/netdata/netdata/issues/5392) for Kubernetes, so stay tuned!
|
||||
|
||||
- **Network interfaces**<br/>
|
||||
per interface: bandwidth, packets, errors, drops
|
||||
A [major refactoring of the python.d plugin](https://github.com/netdata/netdata/pull/5552) has resulted in a dramatic decrease of the required memory, making Netdata even more resource efficient.
|
||||
|
||||
|
||||
We also added charts for IPC shared memory segments and total memory used.
|
||||
|
||||
- **IPv4 networking**<br/>
|
||||
bandwidth, packets, errors, fragments,
|
||||
tcp: connections, packets, errors, handshake,
|
||||
udp: packets, errors,
|
||||
broadcast: bandwidth, packets,
|
||||
multicast: bandwidth, packets
|
||||
---
|
||||
|
||||
- **IPv6 networking**<br/>
|
||||
bandwidth, packets, errors, fragments, ECT,
|
||||
udp: packets, errors,
|
||||
udplite: packets, errors,
|
||||
broadcast: bandwidth,
|
||||
multicast: bandwidth, packets,
|
||||
icmp: messages, errors, echos, router, neighbor, MLDv2, group membership,
|
||||
break down by type
|
||||
`Feb 28th, 2019` - **[Netdata v1.12.2 released!](https://github.com/netdata/netdata/releases)**
|
||||
|
||||
- **Interprocess Communication - IPC**<br/>
|
||||
such as semaphores and semaphores arrays
|
||||
Patch release 1.12.2 contains 7 bug fixes and 4 improvements.
|
||||
|
||||
- **netfilter / iptables Linux firewall**<br/>
|
||||
connections, connection tracker events, errors
|
||||
The main motivation behind a new patch release is the introduction of a **stable release channel**.
|
||||
A "stable" installation and update channel was always on our roadmap, but it became a necessity when we realized that our users in China could not use the nightly releases published on Google Cloud. The "stable" channel is based on our official GitHub releases and uses assets hosted on GitHub.
|
||||
|
||||
- **Linux DDoS protection**<br/>
|
||||
SYNPROXY metrics
|
||||
We are also introducing a new **Oracle DB collector** module, implemented in Python.
|
||||
|
||||
- **fping** latencies</br>
|
||||
for any number of hosts, showing latency, packets and packet loss
|
||||
---
|
||||
|
||||
|
||||
`Feb 21st, 2019` - **[Netdata v1.12.1 released!](https://github.com/netdata/netdata/releases)**
|
||||
|
||||
Patch release 1.12.1 contains 22 bug fixes and 8 improvements.
|
||||
|
||||
---
|
||||
|
||||
`Feb 14th, 2019` - **[Netdata v1.12.0 released!](https://github.com/netdata/netdata/releases)**
|
||||
|
||||
Release 1.12 is made out of 211 pull requests and 22 bug fixes.
|
||||
The key improvements are:
|
||||
|
||||
- Introducing `netdata.cloud`, the free Netdata service for all Netdata users
|
||||
- High performance plugins with go.d.plugin (data collection orchestrator written in Go)
|
||||
- 7 new data collectors and 11 rewrites of existing data collectors for improved performance
|
||||
- A new management API for all Netdata servers
|
||||
- Bind different functions of the Netdata APIs to different ports
|
||||
- Improved installation and updates
|
||||
|
||||
---
|
||||
|
||||
`Nov 22nd, 2018` - **[Netdata v1.11.1 released!](https://github.com/netdata/netdata/releases)**
|
||||
|
||||
- Improved internal database to support values above 64bit.
|
||||
- New data collection plugins: [`openldap`](collectors/python.d.plugin/openldap/), [`tor`](collectors/python.d.plugin/tor/), [`nvidia_smi`](collectors/python.d.plugin/nvidia_smi/).
|
||||
- Improved data collection plugins: Netdata now supports monitoring network interface aliases, [`smartd_log`](collectors/python.d.plugin/smartd_log/), [`cpufreq`](collectors/proc.plugin/README.md#cpu-frequency), [`sensors`](collectors/python.d.plugin/sensors/).
|
||||
- Health monitoring improvements: network interface congestion alarm restored, [`alerta.io`](health/notifications/alerta/), `conntrack_max`.
|
||||
- `my-netdata`menu has been refactored.
|
||||
- Packaging: `openrc` service definition got a few improvements.
|
||||
|
||||
---
|
||||
|
||||
`Sep 18, 2018` - **Netdata has its own organization**
|
||||
|
||||
Netdata used to be a [firehol.org](https://firehol.org) project, accessible as `firehol/netdata`.
|
||||
|
||||
Netdata now has its own github organization `netdata`, so all github URLs are now `netdata/netdata`. The old github URLs, repo clones, forks, etc redirect automatically to the new repo.
|
||||
|
||||
## How it works
|
||||
|
||||
Netdata is a highly efficient, highly modular, metrics management engine. Its lockless design makes it ideal for concurrent operations on the metrics.
|
||||
|
||||
|
||||
|
||||
This is how it works:
|
||||
|
||||
Function|Description|Documentation
|
||||
:---:|:---|:---:
|
||||
**Collect**|Multiple independent data collection workers are collecting metrics from their sources using the optimal protocol for each application and push the metrics to the database. Each data collection worker has lockless write access to the metrics it collects.|[`collectors`](collectors/#data-collection-plugins)
|
||||
**Store**|Metrics are stored in RAM in a round robin database (ring buffer), using a custom made floating point number for minimal footprint.|[`database`](database/#database)
|
||||
**Check**|A lockless independent watchdog is evaluating **health checks** on the collected metrics, triggers alarms, maintains a health transaction log and dispatches alarm notifications.|[`health`](health/#health-monitoring)
|
||||
**Stream**|An lockless independent worker is streaming metrics, in full detail and in real-time, to remote Netdata servers, as soon as they are collected.|[`streaming`](streaming/#streaming-and-replication)
|
||||
**Archive**|A lockless independent worker is down-sampling the metrics and pushes them to **backend** time-series databases.|[`backends`](backends/)
|
||||
**Query**|Multiple independent workers are attached to the [internal web server](web/server/#web-server), servicing API requests, including [data queries](web/api/queries/#database-queries).|[`web/api`](web/api/#api)
|
||||
|
||||
The result is a highly efficient, low latency system, supporting multiple readers and one writer on each metric.
|
||||
|
||||
## Infographic
|
||||
|
||||
This is a high level overview of Netdata feature set and architecture.
|
||||
Click it to to interact with it (it has direct links to documentation).
|
||||
|
||||
[](https://my-netdata.io/infographic.html)
|
||||
|
||||
|
||||
- **Processes**<br/>
|
||||
running, blocked, forks, active
|
||||
## Features
|
||||
|
||||
- **Entropy**<br/>
|
||||
random numbers pool, using in cryptography
|
||||
|
||||
|
||||
- **NFS file servers and clients**<br/>
|
||||
NFS v2, v3, v4: I/O, cache, read ahead, RPC calls
|
||||
This is what you should expect from Netdata:
|
||||
|
||||
- **Network QoS**<br/>
|
||||
the only tool that visualizes network `tc` classes in realtime
|
||||
### General
|
||||
- **1s granularity** - the highest possible resolution for all metrics.
|
||||
- **Unlimited metrics** - collects all the available metrics, the more the better.
|
||||
- **1% CPU utilization of a single core** - it is super fast, unbelievably optimized.
|
||||
- **A few MB of RAM** - by default it uses 25MB RAM. [You size it](database).
|
||||
- **Zero disk I/O** - while it runs, it does not load or save anything (except `error` and `access` logs).
|
||||
- **Zero configuration** - auto-detects everything, it can collect up to 10000 metrics per server out of the box.
|
||||
- **Zero maintenance** - You just run it, it does the rest.
|
||||
- **Zero dependencies** - it is even its own web server, for its static web files and its web API (though its plugins may require additional libraries, depending on the applications monitored).
|
||||
- **Scales to infinity** - you can install it on all your servers, containers, VMs and IoTs. Metrics are not centralized by default, so there is no limit.
|
||||
- **Several operating modes** - Autonomous host monitoring (the default), headless data collector, forwarding proxy, store and forward proxy, central multi-host monitoring, in all possible configurations. Each node may have different metrics retention policy and run with or without health monitoring.
|
||||
|
||||
|
||||
### Health Monitoring & Alarms
|
||||
- **Sophisticated alerting** - comes with hundreds of alarms, **out of the box**! Supports dynamic thresholds, hysteresis, alarm templates, multiple role-based notification methods.
|
||||
- **Notifications**: [alerta.io](health/notifications/alerta/), [amazon sns](health/notifications/awssns/), [discordapp.com](health/notifications/discord/), [email](health/notifications/email/), [flock.com](health/notifications/flock/), [irc](health/notifications/irc/), [kavenegar.com](health/notifications/kavenegar/), [messagebird.com](health/notifications/messagebird/), [pagerduty.com](health/notifications/pagerduty/), [prowl](health/notifications/prowl/), [pushbullet.com](health/notifications/pushbullet/), [pushover.net](health/notifications/pushover/), [rocket.chat](health/notifications/rocketchat/), [slack.com](health/notifications/slack/), [smstools3](health/notifications/smstools3/), [syslog](health/notifications/syslog/), [telegram.org](health/notifications/telegram/), [twilio.com](health/notifications/twilio/), [web](health/notifications/web/) and [custom notifications](health/notifications/custom/).
|
||||
|
||||
- **Linux Control Groups**<br/>
|
||||
containers: systemd, lxc, docker
|
||||
### Integrations
|
||||
- **time-series dbs** - can archive its metrics to `graphite`, `opentsdb`, `prometheus`, json document DBs, in the same or lower resolution (lower: to prevent it from congesting these servers due to the amount of data collected).
|
||||
|
||||
- **Applications**<br/>
|
||||
by grouping the process tree and reporting CPU, memory, disk reads,
|
||||
disk writes, swap, threads, pipes, sockets - per group
|
||||
## Visualization
|
||||
|
||||
|
||||
- **Stunning interactive dashboards** - mouse, touchpad and touch-screen friendly in 2 themes: `slate` (dark) and `white`.
|
||||
- **Amazingly fast visualization** - responds to all queries in less than 1 ms per metric, even on low-end hardware.
|
||||
- **Visual anomaly detection** - the dashboards are optimized for detecting anomalies visually.
|
||||
- **Embeddable** - its charts can be embedded on your web pages, wikis and blogs. You can even use [Atlassian's Confluence as a monitoring dashboard](web/gui/confluence/).
|
||||
- **Customizable** - custom dashboards can be built using simple HTML (no javascript necessary).
|
||||
|
||||
- **Users and User Groups resource usage**<br/>
|
||||
by summarizing the process tree per user and group,
|
||||
reporting: CPU, memory, disk reads, disk writes, swap, threads, pipes, sockets
|
||||
### Positive and negative values
|
||||
|
||||
- **Apache and lighttpd web servers**<br/>
|
||||
`mod-status` (v2.2, v2.4) and cache log statistics, for multiple servers
|
||||
To improve clarity on charts, Netdata dashboards present **positive** values for metrics representing `read`, `input`, `inbound`, `received` and **negative** values for metrics representing `write`, `output`, `outbound`, `sent`.
|
||||
|
||||
- **Nginx web servers**<br/>
|
||||
`stub-status`, for multiple servers
|
||||
|
||||
|
||||
- **Tomcat**<br/>
|
||||
accesses, threads, free memory, volume
|
||||
*Netdata charts showing the bandwidth and packets of a network interface. `received` is positive and `sent` is negative.*
|
||||
|
||||
- **web server log files**<br/>
|
||||
extracting in real-time, web server performance metrics and applying several health checks
|
||||
### Autoscaled y-axis
|
||||
|
||||
- **mySQL databases**<br/>
|
||||
multiple servers, each showing: bandwidth, queries/s, handlers, locks, issues,
|
||||
tmp operations, connections, binlog metrics, threads, innodb metrics, and more
|
||||
Netdata charts automatically zoom vertically, to visualize the variation of each metric within the visible time-frame.
|
||||
|
||||
- **Postgres databases**<br/>
|
||||
multiple servers, each showing: per database statistics (connections, tuples
|
||||
read - written - returned, transactions, locks), backend processes, indexes,
|
||||
tables, write ahead, background writer and more
|
||||
|
||||
|
||||
- **Redis databases**<br/>
|
||||
multiple servers, each showing: operations, hit rate, memory, keys, clients, slaves
|
||||
*A zero based `stacked` chart, automatically switches to an auto-scaled `area` chart when a single dimension is selected.*
|
||||
|
||||
- **mongodb**<br/>
|
||||
operations, clients, transactions, cursors, connections, asserts, locks, etc
|
||||
### Charts are synchronized
|
||||
|
||||
- **memcached databases**<br/>
|
||||
multiple servers, each showing: bandwidth, connections, items
|
||||
Charts on Netdata dashboards are synchronized to each other. There is no master chart. Any chart can be panned or zoomed at any time, and all other charts will follow.
|
||||
|
||||
- **elasticsearch**<br/>
|
||||
search and index performance, latency, timings, cluster statistics, threads statistics, etc
|
||||
|
||||
|
||||
- **ISC Bind name servers**<br/>
|
||||
multiple servers, each showing: clients, requests, queries, updates, failures and several per view metrics
|
||||
*Charts are panned by dragging them with the mouse. Charts can be zoomed in/out with`SHIFT` + `mouse wheel` while the mouse pointer is over a chart.*
|
||||
|
||||
- **NSD name servers**<br/>
|
||||
queries, zones, protocols, query types, transfers, etc.
|
||||
> The visible time-frame (pan and zoom) is propagated from Netdata server to Netdata server, when navigating via the [node menu](registry#registry).
|
||||
|
||||
- **Postfix email servers**<br/>
|
||||
message queue (entries, size)
|
||||
### Highlighted time-frame
|
||||
|
||||
- **exim email servers**<br/>
|
||||
message queue (emails queued)
|
||||
To improve visual anomaly detection across charts, the user can highlight a time-frame (by pressing `ALT` + `mouse selection`) on all charts.
|
||||
|
||||
- **Dovecot** POP3/IMAP servers<br/>
|
||||
|
||||
|
||||
- **ISC dhcpd**<br/>
|
||||
pools utilization, leases, etc.
|
||||
*A highlighted time-frame can be given by pressing `ALT` + `mouse selection` on any chart. Netdata will highlight the same range on all charts.*
|
||||
|
||||
- **IPFS**<br/>
|
||||
bandwidth, peers
|
||||
> Highlighted ranges are propagated from Netdata server to Netdata server, when navigating via the [node menu](registry#registry).
|
||||
|
||||
- **Squid proxy servers**<br/>
|
||||
multiple servers, each showing: clients bandwidth and requests, servers bandwidth and requests
|
||||
---
|
||||
|
||||
- **HAproxy**<br/>
|
||||
bandwidth, sessions, backends, etc
|
||||
|
||||
- **varnish**<br/>
|
||||
threads, sessions, hits, objects, backends, etc
|
||||
## What does it monitor
|
||||
|
||||
- **OpenVPN**<br/>
|
||||
status per tunnel
|
||||
Netdata data collection is **extensible** - you can monitor anything you can get a metric for.
|
||||
Its [Plugin API](collectors/plugins.d/) supports all programing languages (anything can be a Netdata plugin, BASH, python, perl, node.js, java, Go, ruby, etc).
|
||||
|
||||
- **Hardware sensors**<br/>
|
||||
`lm_sensors` and `IPMI`: temperature, voltage, fans, power, humidity
|
||||
- For better performance, most system related plugins (cpu, memory, disks, filesystems, networking, etc) have been written in `C`.
|
||||
- For faster development and easier contributions, most application related plugins (databases, web servers, etc) have been written in `python`.
|
||||
|
||||
- **NUT and APC UPSes**<br/>
|
||||
load, charge, battery voltage, temperature, utility metrics, output metrics
|
||||
#### APM (Application Performance Monitoring)
|
||||
- **[statsd](collectors/statsd.plugin/)** - Netdata is a fully featured statsd server.
|
||||
- **[Go expvar](collectors/python.d.plugin/go_expvar/)** - collects metrics exposed by applications written in the Go programming language using the expvar package.
|
||||
- **[Spring Boot](collectors/python.d.plugin/springboot/)** - monitors running Java Spring Boot applications that expose their metrics with the use of the Spring Boot Actuator included in Spring Boot library.
|
||||
- **[uWSGI](collectors/python.d.plugin/uwsgi/)** - collects performance metrics from uWSGI applications.
|
||||
|
||||
- **PHP-FPM**<br/>
|
||||
multiple instances, each reporting connections, requests, performance
|
||||
#### System Resources
|
||||
- **[CPU Utilization](collectors/proc.plugin/)** - total and per core CPU usage.
|
||||
- **[Interrupts](collectors/proc.plugin/)** - total and per core CPU interrupts.
|
||||
- **[SoftIRQs](collectors/proc.plugin/)** - total and per core SoftIRQs.
|
||||
- **[SoftNet](collectors/proc.plugin/)** - total and per core SoftIRQs related to network activity.
|
||||
- **[CPU Throttling](collectors/proc.plugin/)** - collects per core CPU throttling.
|
||||
- **[CPU Frequency](collectors/proc.plugin/)** - collects the current CPU frequency.
|
||||
- **[CPU Idle](collectors/proc.plugin/)** - collects the time spent per processor state.
|
||||
- **[IdleJitter](collectors/idlejitter.plugin/)** - measures CPU latency.
|
||||
- **[Entropy](collectors/proc.plugin/)** - random numbers pool, using in cryptography.
|
||||
- **[Interprocess Communication - IPC](collectors/proc.plugin/)** - such as semaphores and semaphores arrays.
|
||||
|
||||
- **hddtemp**<br/>
|
||||
disk temperatures
|
||||
#### Memory
|
||||
- **[ram](collectors/proc.plugin/)** - collects info about RAM usage.
|
||||
- **[swap](collectors/proc.plugin/)** - collects info about swap memory usage.
|
||||
- **[available memory](collectors/proc.plugin/)** - collects the amount of RAM available for userspace processes.
|
||||
- **[committed memory](collectors/proc.plugin/)** - collects the amount of RAM committed to userspace processes.
|
||||
- **[Page Faults](collectors/proc.plugin/)** - collects the system page faults (major and minor).
|
||||
- **[writeback memory](collectors/proc.plugin/)** - collects the system dirty memory and writeback activity.
|
||||
- **[huge pages](collectors/proc.plugin/)** - collects the amount of RAM used for huge pages.
|
||||
- **[KSM](collectors/proc.plugin/)** - collects info about Kernel Same Merging (memory dedupper).
|
||||
- **[Numa](collectors/proc.plugin/)** - collects Numa info on systems that support it.
|
||||
- **[slab](collectors/proc.plugin/)** - collects info about the Linux kernel memory usage.
|
||||
|
||||
- **smartd**<br/>
|
||||
disk S.M.A.R.T. values
|
||||
#### Disks
|
||||
- **[block devices](collectors/proc.plugin/)** - per disk: I/O, operations, backlog, utilization, space, etc.
|
||||
- **[BCACHE](collectors/proc.plugin/)** - detailed performance of SSD caching devices.
|
||||
- **[DiskSpace](collectors/proc.plugin/)** - monitors disk space usage.
|
||||
- **[mdstat](collectors/proc.plugin/)** - software RAID.
|
||||
- **[hddtemp](collectors/python.d.plugin/hddtemp/)** - disk temperatures.
|
||||
- **[smartd](collectors/python.d.plugin/smartd_log/)** - disk S.M.A.R.T. values.
|
||||
- **[device mapper](collectors/proc.plugin/)** - naming disks.
|
||||
- **[Veritas Volume Manager](collectors/proc.plugin/)** - naming disks.
|
||||
- **[megacli](collectors/python.d.plugin/megacli/)** - adapter, physical drives and battery stats.
|
||||
- **[adaptec_raid](collectors/python.d.plugin/adaptec_raid/)** - logical and physical devices health metrics.
|
||||
- **[ioping](collectors/ioping.plugin/)** - to measure disk read/write latency.
|
||||
|
||||
- **SNMP devices**<br/>
|
||||
can be monitored too (although you will need to configure these)
|
||||
#### Filesystems
|
||||
- **[BTRFS](collectors/proc.plugin/)** - detailed disk space allocation and usage.
|
||||
- **[Ceph](collectors/python.d.plugin/ceph/)** - OSD usage, Pool usage, number of objects, etc.
|
||||
- **[NFS file servers and clients](collectors/proc.plugin/)** - NFS v2, v3, v4: I/O, cache, read ahead, RPC calls
|
||||
- **[Samba](collectors/python.d.plugin/samba/)** - performance metrics of Samba SMB2 file sharing.
|
||||
- **[ZFS](collectors/proc.plugin/)** - detailed performance and resource usage.
|
||||
|
||||
- **statsd**<br/>
|
||||
[netdata is a fully featured statsd server](https://github.com/firehol/netdata/wiki/statsd)
|
||||
#### Networking
|
||||
- **[Network Stack](collectors/proc.plugin/)** - everything about the networking stack (both IPv4 and IPv6 for all protocols: TCP, UDP, SCTP, UDPLite, ICMP, Multicast, Broadcast, etc), and all network interfaces (per interface: bandwidth, packets, errors, drops).
|
||||
- **[Netfilter](collectors/proc.plugin/)** - everything about the netfilter connection tracker.
|
||||
- **[SynProxy](collectors/proc.plugin/)** - collects performance data about the linux SYNPROXY (DDoS).
|
||||
- **[NFacct](collectors/nfacct.plugin/)** - collects accounting data from iptables.
|
||||
- **[Network QoS](collectors/tc.plugin/)** - the only tool that visualizes network `tc` classes in real-time
|
||||
- **[FPing](collectors/fping.plugin/)** - to measure latency and packet loss between any number of hosts.
|
||||
- **[ISC dhcpd](collectors/python.d.plugin/isc_dhcpd/)** - pools utilization, leases, etc.
|
||||
- **[AP](collectors/charts.d.plugin/ap/)** - collects Linux access point performance data (`hostapd`).
|
||||
- **[SNMP](collectors/node.d.plugin/snmp/)** - SNMP devices can be monitored too (although you will need to configure these).
|
||||
- **[port_check](collectors/python.d.plugin/portcheck/)** - checks TCP ports for availability and response time.
|
||||
|
||||
And you can extend it, by writing plugins that collect data from any source, using any computer language.
|
||||
#### Virtual Private Networks
|
||||
- **[OpenVPN](collectors/python.d.plugin/ovpn_status_log/)** - collects status per tunnel.
|
||||
- **[LibreSwan](collectors/charts.d.plugin/libreswan/)** - collects metrics per IPSEC tunnel.
|
||||
- **[Tor](collectors/python.d.plugin/tor/)** - collects Tor traffic statistics.
|
||||
|
||||
#### Processes
|
||||
- **[System Processes](collectors/proc.plugin/)** - running, blocked, forks, active.
|
||||
- **[Applications](collectors/apps.plugin/)** - by grouping the process tree and reporting CPU, memory, disk reads, disk writes, swap, threads, pipes, sockets - per process group.
|
||||
- **[systemd](collectors/cgroups.plugin/)** - monitors systemd services using CGROUPS.
|
||||
|
||||
#### Users
|
||||
- **[Users and User Groups resource usage](collectors/apps.plugin/)** - by summarizing the process tree per user and group, reporting: CPU, memory, disk reads, disk writes, swap, threads, pipes, sockets
|
||||
- **[logind](collectors/python.d.plugin/logind/)** - collects sessions, users and seats connected.
|
||||
|
||||
#### Containers and VMs
|
||||
- **[Containers](collectors/cgroups.plugin/)** - collects resource usage for all kinds of containers, using CGROUPS (systemd-nspawn, lxc, lxd, docker, kubernetes, etc).
|
||||
- **[libvirt VMs](collectors/cgroups.plugin/)** - collects resource usage for all kinds of VMs, using CGROUPS.
|
||||
- **[dockerd](collectors/python.d.plugin/dockerd/)** - collects docker health metrics.
|
||||
|
||||
#### Web Servers
|
||||
- **[Apache and lighttpd](collectors/python.d.plugin/apache/)** - `mod-status` (v2.2, v2.4) and cache log statistics, for multiple servers.
|
||||
- **[IPFS](collectors/python.d.plugin/ipfs/)** - bandwidth, peers.
|
||||
- **[LiteSpeed](collectors/python.d.plugin/litespeed/)** - reads the litespeed rtreport files to collect metrics.
|
||||
- **[Nginx](collectors/python.d.plugin/nginx/)** - `stub-status`, for multiple servers.
|
||||
- **[Nginx+](collectors/python.d.plugin/nginx_plus/)** - connects to multiple nginx_plus servers (local or remote) to collect real-time performance metrics.
|
||||
- **[PHP-FPM](collectors/python.d.plugin/phpfpm/)** - multiple instances, each reporting connections, requests, performance, etc.
|
||||
- **[Tomcat](collectors/python.d.plugin/tomcat/)** - accesses, threads, free memory, volume, etc.
|
||||
- **[web server `access.log` files](collectors/python.d.plugin/web_log/)** - extracting in real-time, web server and proxy performance metrics and applying several health checks, etc.
|
||||
- **[HTTP check](collectors/python.d.plugin/httpcheck/)** - checks one or more web servers for HTTP status code and returned content.
|
||||
|
||||
#### Proxies, Balancers, Accelerators
|
||||
- **[HAproxy](collectors/python.d.plugin/haproxy/)** - bandwidth, sessions, backends, etc.
|
||||
- **[Squid](collectors/python.d.plugin/squid/)** - multiple servers, each showing: clients bandwidth and requests, servers bandwidth and requests.
|
||||
- **[Traefik](collectors/python.d.plugin/traefik/)** - connects to multiple traefik instances (local or remote) to collect API metrics (response status code, response time, average response time and server uptime).
|
||||
- **[Varnish](collectors/python.d.plugin/varnish/)** - threads, sessions, hits, objects, backends, etc.
|
||||
- **[IPVS](collectors/proc.plugin/)** - collects metrics from the Linux IPVS load balancer.
|
||||
|
||||
#### Database Servers
|
||||
- **[CouchDB](collectors/python.d.plugin/couchdb/)** - reads/writes, request methods, status codes, tasks, replication, per-db, etc.
|
||||
- **[MemCached](collectors/python.d.plugin/memcached/)** - multiple servers, each showing: bandwidth, connections, items, etc.
|
||||
- **[MongoDB](collectors/python.d.plugin/mongodb/)** - operations, clients, transactions, cursors, connections, asserts, locks, etc.
|
||||
- **[MySQL and mariadb](collectors/python.d.plugin/mysql/)** - multiple servers, each showing: bandwidth, queries/s, handlers, locks, issues, tmp operations, connections, binlog metrics, threads, innodb metrics, and more.
|
||||
- **[PostgreSQL](collectors/python.d.plugin/postgres/)** - multiple servers, each showing: per database statistics (connections, tuples read - written - returned, transactions, locks), backend processes, indexes, tables, write ahead, background writer and more.
|
||||
- **[Proxy SQL](collectors/python.d.plugin/proxysql/)** - collects Proxy SQL backend and frontend performance metrics.
|
||||
- **[Redis](collectors/python.d.plugin/redis/)** - multiple servers, each showing: operations, hit rate, memory, keys, clients, slaves.
|
||||
- **[RethinkDB](collectors/python.d.plugin/rethinkdbs/)** - connects to multiple rethinkdb servers (local or remote) to collect real-time metrics.
|
||||
|
||||
#### Message Brokers
|
||||
- **[beanstalkd](collectors/python.d.plugin/beanstalk/)** - global and per tube monitoring.
|
||||
- **[RabbitMQ](collectors/python.d.plugin/rabbitmq/)** - performance and health metrics.
|
||||
|
||||
#### Search and Indexing
|
||||
- **[ElasticSearch](collectors/python.d.plugin/elasticsearch/)** - search and index performance, latency, timings, cluster statistics, threads statistics, etc.
|
||||
|
||||
#### DNS Servers
|
||||
- **[bind_rndc](collectors/python.d.plugin/bind_rndc/)** - parses `named.stats` dump file to collect real-time performance metrics. All versions of bind after 9.6 are supported.
|
||||
- **[dnsdist](collectors/python.d.plugin/dnsdist/)** - performance and health metrics.
|
||||
- **[ISC Bind (named)](collectors/node.d.plugin/named/)** - multiple servers, each showing: clients, requests, queries, updates, failures and several per view metrics. All versions of bind after 9.9.10 are supported.
|
||||
- **[NSD](collectors/python.d.plugin/nsd/)** - queries, zones, protocols, query types, transfers, etc.
|
||||
- **[PowerDNS](collectors/python.d.plugin/powerdns/)** - queries, answers, cache, latency, etc.
|
||||
- **[unbound](collectors/python.d.plugin/unbound/)** - performance and resource usage metrics.
|
||||
- **[dns_query_time](collectors/python.d.plugin/dns_query_time/)** - DNS query time statistics.
|
||||
|
||||
#### Time Servers
|
||||
- **[chrony](collectors/python.d.plugin/chrony/)** - uses the `chronyc` command to collect chrony statistics (Frequency, Last offset, RMS offset, Residual freq, Root delay, Root dispersion, Skew, System time).
|
||||
- **[ntpd](collectors/python.d.plugin/ntpd/)** - connects to multiple ntpd servers (local or remote) to provide statistics of system variables and optional also peer variables.
|
||||
|
||||
#### Mail Servers
|
||||
- **[Dovecot](collectors/python.d.plugin/dovecot/)** - POP3/IMAP servers.
|
||||
- **[Exim](collectors/python.d.plugin/exim/)** - message queue (emails queued).
|
||||
- **[Postfix](collectors/python.d.plugin/postfix/)** - message queue (entries, size).
|
||||
|
||||
#### Hardware Sensors
|
||||
- **[IPMI](collectors/freeipmi.plugin/)** - enterprise hardware sensors and events.
|
||||
- **[lm-sensors](collectors/python.d.plugin/sensors/)** - temperature, voltage, fans, power, humidity, etc.
|
||||
- **[Nvidia](collectors/python.d.plugin/nvidia_smi/)** - collects information for Nvidia GPUs.
|
||||
- **[RPi](collectors/charts.d.plugin/sensors/)** - Raspberry Pi temperature sensors.
|
||||
- **[w1sensor](collectors/python.d.plugin/w1sensor/)** - collects data from connected 1-Wire sensors.
|
||||
|
||||
#### UPSes
|
||||
- **[apcupsd](collectors/charts.d.plugin/apcupsd/)** - load, charge, battery voltage, temperature, utility metrics, output metrics
|
||||
- **[NUT](collectors/charts.d.plugin/nut/)** - load, charge, battery voltage, temperature, utility metrics, output metrics
|
||||
- **[Linux Power Supply](collectors/proc.plugin/)** - collects metrics reported by power supply drivers on Linux.
|
||||
|
||||
#### Social Sharing Servers
|
||||
- **[RetroShare](collectors/python.d.plugin/retroshare/)** - connects to multiple retroshare servers (local or remote) to collect real-time performance metrics.
|
||||
|
||||
#### Security
|
||||
- **[Fail2Ban](collectors/python.d.plugin/fail2ban/)** - monitors the fail2ban log file to check all bans for all active jails.
|
||||
|
||||
#### Authentication, Authorization, Accounting (AAA, RADIUS, LDAP) Servers
|
||||
- **[FreeRadius](collectors/python.d.plugin/freeradius/)** - uses the `radclient` command to provide freeradius statistics (authentication, accounting, proxy-authentication, proxy-accounting).
|
||||
|
||||
#### Telephony Servers
|
||||
- **[opensips](collectors/charts.d.plugin/opensips/)** - connects to an opensips server (localhost only) to collect real-time performance metrics.
|
||||
|
||||
#### Household Appliances
|
||||
- **[SMA webbox](collectors/node.d.plugin/sma_webbox/)** - connects to multiple remote SMA webboxes to collect real-time performance metrics of the photovoltaic (solar) power generation.
|
||||
- **[Fronius](collectors/node.d.plugin/fronius/)** - connects to multiple remote Fronius Symo servers to collect real-time performance metrics of the photovoltaic (solar) power generation.
|
||||
- **[StiebelEltron](collectors/node.d.plugin/stiebeleltron/)** - collects the temperatures and other metrics from your Stiebel Eltron heating system using their Internet Service Gateway (ISG web).
|
||||
|
||||
#### Game Servers
|
||||
- **[SpigotMC](collectors/python.d.plugin/spigotmc/)** - monitors Spigot Minecraft server ticks per second and number of online players using the Minecraft remote console.
|
||||
|
||||
#### Distributed Computing
|
||||
- **[BOINC](collectors/python.d.plugin/boinc/)** - monitors task states for local and remote BOINC client software using the remote GUI RPC interface. Also provides alarms for a handful of error conditions.
|
||||
|
||||
#### Media Streaming Servers
|
||||
- **[IceCast](collectors/python.d.plugin/icecast/)** - collects the number of listeners for active sources.
|
||||
|
||||
### Monitoring Systems
|
||||
- **[Monit](collectors/python.d.plugin/monit/)** - collects metrics about monit targets (filesystems, applications, networks).
|
||||
|
||||
#### Provisioning Systems
|
||||
- **[Puppet](collectors/python.d.plugin/puppet/)** - connects to multiple Puppet Server and Puppet DB instances (local or remote) to collect real-time status metrics.
|
||||
|
||||
You can easily extend Netdata, by writing plugins that collect data from any source, using any computer language.
|
||||
|
||||
## Links
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
SOURCE_URL=https://github.com/netdata/netdata/releases/download/v1.12.2/netdata-v1.12.2.tar.gz
|
||||
SOURCE_SUM=f8cd689ec1ab262903b5a54c8df2fd0fe6e5e7b0ab4a2c60fde4e88f37aa72b5
|
||||
SOURCE_URL=https://github.com/netdata/netdata/releases/download/v1.15.0/netdata-v1.15.0.tar.gz
|
||||
SOURCE_SUM=7d2f25c62003ea96669e460ec96b69a9616c9ddd6f48a48707a79a898077d911
|
||||
SOURCE_FORMAT=tar.gz
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
SOURCE_URL=https://raw.githubusercontent.com/netdata/netdata/v1.12.2/packaging/installer/netdata-uninstaller.sh
|
||||
SOURCE_SUM=a91970882dd90fd3b2352be185c6df9fc1b0ecda9e08677a1f47a0fd281a7615
|
||||
SOURCE_URL=https://raw.githubusercontent.com/netdata/netdata/v1.15.0/packaging/installer/netdata-uninstaller.sh
|
||||
SOURCE_SUM=a4727069b47138cea5c466bc902934545841c88dc5f641728ef0feb921efd218
|
||||
SOURCE_FILENAME=netdata-uninstaller.sh
|
||||
SOURCE_EXTRACT=false
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
"en": "real-time performance and health monitoring",
|
||||
"fr": "Monitoring serveur en temps reel"
|
||||
},
|
||||
"version": "1.12.2~ynh1",
|
||||
"version": "1.15.0~ynh1",
|
||||
"url": "http://my-netdata.io/",
|
||||
"license": "GPL-3.0",
|
||||
"maintainer": {
|
||||
|
|
|
|||
|
|
@ -51,6 +51,9 @@ touch /opt/netdata/etc/netdata/.opt-out-from-anonymous-statistics
|
|||
# Add a web_log entry for every YunoHost domain
|
||||
netdata_add_yunohost_web_logs () {
|
||||
local web_log_file="/opt/netdata/etc/netdata/python.d/web_log.conf"
|
||||
if [ ! -f $web_log_file ] ; then
|
||||
cp /opt/netdata/etc/netdata/orig/python.d/web_log.conf $web_log_file
|
||||
fi
|
||||
if [ -z "$(grep "YUNOHOST" $web_log_file)" ] ; then
|
||||
echo "# ------------YUNOHOST DOMAINS---------------" >> $web_log_file
|
||||
for domain in $(yunohost domain list --output-as plain); do
|
||||
|
|
@ -67,8 +70,12 @@ EOF
|
|||
|
||||
# If PostgreSQL is installed, add a PostgreSQL entry using instance password
|
||||
netdata_add_yunohost_postgres_configuration () {
|
||||
if [ -f /etc/yunohost/psql ] && [ -z "$(grep "yunohost:" /opt/netdata/etc/netdata/python.d/postgres.conf)" ] ; then
|
||||
cat >> /opt/netdata/etc/netdata/python.d/postgres.conf <<EOF
|
||||
local postgres_file="/opt/netdata/etc/netdata/python.d/postgres.conf"
|
||||
if [ ! -f $postgres_file ] ; then
|
||||
cp /opt/netdata/etc/netdata/orig/python.d/postgres.conf $postgres_file
|
||||
fi
|
||||
if [ -f /etc/yunohost/psql ] && [ -z "$(grep "yunohost:" $postgres_file)" ] ; then
|
||||
cat >> $postgres_file <<EOF
|
||||
yunohost:
|
||||
name : 'local'
|
||||
database : 'postgres'
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue