netdata/docs/glossary.md

Glossary

Welcome to Netdata's terminology guide! Whether you're a seasoned engineer or just starting your journey in system monitoring, this glossary helps demystify the terms used throughout our documentation and community.

This glossary serves as a living document, continuously updated to help you understand Netdata concepts, features, and terminology. Each term links to detailed documentation for deeper exploration.

Missing a term? Let us know or submit a request to expand our glossary. Together, we can make Netdata more accessible to everyone.

A | B | C | D| E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

A

• Agent or Netdata Agent: Netdata's distributed monitoring Agent collects thousands of metrics from systems, hardware, and applications with zero configuration. It runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices.

• Agent-cloud link or ACLK: The Agent-Cloud link (ACLK) is the mechanism responsible for securely connecting a Netdata Agent to your web browser through Netdata Cloud.

• Aggregate Function: A function applied When the granularity of the data collected is higher than the plotted points on the chart.

• Alerts (formerly Alarms): With the information that appears on Netdata Cloud and the local dashboard about active alerts, you can configure alerts to match your infrastructure's needs or your team's goals.

• Alarm Entity Type: Entity types that are attached to specific charts and use the alarm label.

• Anomaly Advisor: A Netdata feature that lets you focus on potentially anomalous metrics and charts related to a particular highlight window of interest.

C

• Child: A node, running Netdata, that streams metric data to one or more Parents.

• Cloud or Netdata Cloud: Netdata Cloud is a web application that gives you real-time visibility for your entire infrastructure. With Netdata Cloud, you can view key metrics, insightful charts, and active alerts from all your nodes in a single web interface.

• Collector: A catch-all term for any Netdata process that gathers metrics from an endpoint.

• Community: As a company with a passion and genesis in open-source, we are not just very proud of our community, but we consider our users, fans, and chatters to be an imperative part of the Netdata experience and culture.

• Context: A way of grouping charts by the types of metrics collected and dimensions displayed. It's kind of like a machine-readable naming and organization scheme.

• Custom dashboards A dashboard that you can create using simple HTML (no JavaScript is required for basic dashboards).

D

• Dashboard: Out-of-the-box visual representation of metrics to provide insight into your infrastructure, its health and performance.

• Definition Bar: Bar within a composite chart that provides important information and options about the metrics within the chart.

• Dimension: A dimension is a value that gets shown on a chart.

E

• External Plugins: These gather metrics from external processes, such as a webserver or database, and run as independent processes that communicate with the Netdata daemon via pipes.

F

• Family: 1. What we consider our Netdata community of users and engineers. 2. A single instance of a hardware or software resource that needs to be displayed separately from similar instances.

• Flood Protection: If a node has too many state changes like firing too many alerts or going from reachable to unreachable, Netdata Cloud enables flood protection. As long as a node is in flood protection mode, Netdata Cloud doesn’t send notifications about this node

• Functions or Netdata Functions: Routines exposed by a collector on the Netdata Agent that can bring additional information to support troubleshooting or trigger some action to happen on the node itself.

G

• Group by: The drop-down on the dimension bar of a composite chart that allows you to group metrics by dimension, node, or chart.

• Health Configuration Files: Files that you can edit to configure your Agent's health watchdog service.

• Health Entity Reference:

• Home tab: Tab in Netdata Cloud that provides a predefined dashboard of relevant information about entities in the Room.

I

• Internal plugins: These gather metrics from /proc, /sys, and other Linux kernel sources. They are written in C and run as threads within the Netdata daemon.

K

• Kickstart or Kickstart Script: An automatic one-line installation script named 'kickstart.sh' that works on all Linux distributions and macOS.

• Kubernetes Dashboard or Kubernetes Tab: Netdata Cloud features enhanced visualizations for the resource utilization of Kubernetes (k8s) clusters, embedded in the default Overview dashboard.

M

• Metrics Collection: With zero configuration, Netdata auto-detects thousands of data sources upon starting and immediately collects per-second metrics. Netdata can immediately collect metrics from these endpoints thanks to 300+ collectors, which all come pre-installed when you install Netdata.

• Metric Correlations: A Netdata feature that lets you quickly find metrics and charts related to a particular window of interest that you want to explore further.

• Metrics Exporting: Netdata allows you to export metrics to external time-series databases with the exporting engine. This system uses a number of connectors to initiate connections to more than thirty supported databases, including InfluxDB, Prometheus, Graphite, ElasticSearch, and much more.

• Metrics Storage: Upon collection the collected metrics need to be either forwarded, exported or just stored for further treatment. The Agent is capable to store metrics both short and long-term, with or without the usage of non-volatile storage.

• Metrics Streaming Replication: Each node running Netdata can stream the metrics it collects, in real time, to another node. Metric streaming allows you to replicate metrics data across multiple nodes, or centralize all your metrics data into a single time-series database (TSDB).

N

• Netdata: Netdata is a monitoring tool designed by system administrators, DevOps engineers, and developers to collect everything, help you visualize metrics, troubleshoot complex performance problems, and make data interoperable with the rest of your monitoring stack.

• Netdata Agent or Agent: Netdata's distributed monitoring Agent collects thousands of metrics from systems, hardware, and applications with zero configuration. It runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices.

• Netdata Cloud or Cloud: Netdata Cloud is a web application that gives you real-time visibility for your entire infrastructure. With Netdata Cloud, you can view key metrics, insightful charts, and active alerts from all your nodes in a single web interface.

• Netdata Functions or Functions: Routines exposed by a collector on the Netdata Agent that can bring additional information to support troubleshooting or trigger some action to happen on the node itself.

O

• Obsoletion(of nodes): Removing nodes from a space.

• Orchestrators: External plugins that run and manage one or more modules. They run as independent processes.

P

• Parent: A node, running Netdata, that receives streamed metric data.

R

• Registry: Registry that allows Netdata to provide unified cross-server dashboards.

• Replication Streaming: Streaming configuration where child A, with a database and web dashboard, streams metrics to parent B.

• Room: Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.

S

• Single Node Dashboard: A dashboard pre-configured with every installation of the Netdata Agent, with thousands of metrics and hundreds of interactive charts that requires no setup.

• Space: A high-level container and virtual collaboration area where you can organize team members, access levels, and the nodes you want to monitor.

T

• Template Entity Type: Entity type that defines rules that apply to all charts of a specific context, and use the template label. Templates help you apply one entity to all disks, all network interfaces, all MySQL databases, and so on.

• Tiers: Tiering is a mechanism of providing multiple tiers of data with different granularity of metrics (the frequency they are collected and stored, i.e., their resolution).

U

• Unlimited Scalability: With Netdata's distributed architecture, you can seamlessly observe a couple, hundreds or even thousands of nodes. There are no actual bottlenecks especially if you retain metrics locally in the Agents.

V

• Visualizations: Netdata uses dimensions, contexts, and families to sort your metric data into graphs, charts, and alerts that maximize your understanding of your infrastructure and your ability to troubleshoot it, along or on a team.

Z

• Zero Configuration: Netdata is pre-configured and capable of autodetect and monitor any well-known application that runs on your system. You deploy and connect Netdata Agents in your Netdata space, and monitor them in seconds.