From 112b5b91647c3dea45cc1c9bc364df526c8012f1 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 26 Jan 2022 19:05:15 +0100 Subject: Merging upstream version 1.33.0. Signed-off-by: Daniel Baumann --- docs/anonymous-statistics.md | 4 +- docs/collect/application-metrics.md | 2 +- docs/collect/system-metrics.md | 2 +- docs/configure/common-changes.md | 2 +- docs/configure/secure-nodes.md | 2 +- docs/contributing/contributing-documentation.md | 4 +- docs/contributing/style-guide.md | 2 +- docs/dashboard/customize.mdx | 2 +- docs/dashboard/dimensions-contexts-families.mdx | 2 +- docs/dashboard/import-export-print-snapshot.mdx | 2 +- docs/export/external-databases.md | 4 +- docs/getting-started.md | 236 --------------------- docs/guides/collect-unbound-metrics.md | 2 +- docs/guides/longer-metrics-storage.md | 2 +- docs/guides/monitor-cockroachdb.md | 2 +- docs/guides/monitor-hadoop-cluster.md | 5 +- docs/guides/monitor/kubernetes-k8s-netdata.md | 2 +- docs/guides/monitor/lamp-stack.md | 2 +- docs/guides/monitor/pi-hole-raspberry-pi.md | 4 +- docs/guides/monitor/statsd.md | 4 +- docs/guides/monitor/stop-notifications-alarms.md | 2 +- docs/guides/python-collector.md | 2 +- docs/guides/step-by-step/step-00.md | 2 +- docs/guides/step-by-step/step-05.md | 2 +- docs/guides/step-by-step/step-99.md | 2 +- docs/guides/using-host-labels.md | 2 +- .../enable-streaming.mdx | 4 +- docs/monitor/configure-alarms.md | 2 +- docs/monitor/enable-notifications.md | 2 +- docs/quickstart/infrastructure.md | 2 +- 30 files changed, 36 insertions(+), 273 deletions(-) delete mode 100644 docs/getting-started.md (limited to 'docs') diff --git a/docs/anonymous-statistics.md b/docs/anonymous-statistics.md index 75e586bd4..82c018e1b 100644 --- a/docs/anonymous-statistics.md +++ b/docs/anonymous-statistics.md @@ -30,7 +30,7 @@ You can opt-out from sending anonymous statistics to Netdata through three diffe ## Agent Dashboard - PostHog JavaScript -When you kick off an Agent dashboard session by visiting `http://NODE:19999`, Netdata will initialiszes a PostHog session and masks various event attributes. +When you kick off an Agent dashboard session by visiting `http://NODE:19999`, Netdata initializes a PostHog session and masks various event attributes. _Note_: You can see the relevant code in the [dashboard repository](https://github.com/netdata/dashboard/blob/master/src/domains/global/sagas.ts#L107) where the `window.posthog.register()` call is made. @@ -91,7 +91,7 @@ update. You can also export the environment variable `DO_NOT_TRACK` with a non-z When using Docker, **set your `DO_NOT_TRACK` environment variable to `1`.** You can set this variable with the following command: `export DO_NOT_TRACK=1`. When creating a container using Netdata's [Docker -image](/packaging/docker/README.md#run-the-agent-with-the-docker-command) for the first time, this variable will disable +image](/packaging/docker/README.md#create-a-new-netdata-agent-container) for the first time, this variable will disable the anonymous statistics script inside of the container. Each of these opt-out processes does the following: diff --git a/docs/collect/application-metrics.md b/docs/collect/application-metrics.md index fbc0ae249..4fb9ed6ab 100644 --- a/docs/collect/application-metrics.md +++ b/docs/collect/application-metrics.md @@ -29,7 +29,7 @@ Our most popular application collectors: rows in less than half a second. - [MySQL](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/mysql/): Collect database global, replication, and per-user statistics. -- [Redis](/collectors/python.d.plugin/redis/): Monitor database status by reading the server's response to the `INFO` +- [Redis](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/redis): Monitor database status by reading the server's response to the `INFO` command. - [Apache](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/apache/): Collect Apache web server performance metrics via the `server-status?auto` endpoint. diff --git a/docs/collect/system-metrics.md b/docs/collect/system-metrics.md index 599d6f583..14e2cc2aa 100644 --- a/docs/collect/system-metrics.md +++ b/docs/collect/system-metrics.md @@ -30,7 +30,7 @@ eBPF collector to analyze how and when a process accesses files, when it makes s creating zombie processes, and more. While the above plugins and associated collectors are the most important for system metrics, there are many others. You -can find all system collectors in our [supported collectors list](/collectors/COLLECTORS.md#system-metrics). +can find all system collectors in our [supported collectors list](/collectors/COLLECTORS.md#system-collectors). ## Collect Windows system metrics diff --git a/docs/configure/common-changes.md b/docs/configure/common-changes.md index 6749384ac..cf2e5d78a 100644 --- a/docs/configure/common-changes.md +++ b/docs/configure/common-changes.md @@ -31,7 +31,7 @@ section](/daemon/config/README.md#global-section-options) of `netdata.conf`. ``` Read our doc on [increasing long-term metrics storage](/docs/store/change-metrics-storage.md) for details, including a -[calculator](/docs/store/change-metrics-storage.md#calculate-the-system-resources-RAM-disk-space-needed-to-store-metrics) +[calculator](/docs/store/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics) to help you determine the exact settings for your desired retention period. ### Reduce the data collection frequency diff --git a/docs/configure/secure-nodes.md b/docs/configure/secure-nodes.md index 180ffe357..02057ab9e 100644 --- a/docs/configure/secure-nodes.md +++ b/docs/configure/secure-nodes.md @@ -11,7 +11,7 @@ internet at large, anyone can access the dashboard and your node's metrics at `h so that the local dashboard was immediately accessible to users, and so that we don't dictate how professionals set up and secure their infrastructures. -Despite this design decision, your [data](/docs/netdata-security.md#your-data-are-safe-with-netdata) and your +Despite this design decision, your [data](/docs/netdata-security.md#your-data-is-safe-with-netdata) and your [systems](/docs/netdata-security.md#your-systems-are-safe-with-netdata) are safe with Netdata. Netdata is read-only, cannot do anything other than present metrics, and runs without special/`sudo` privileges. Also, the local dashboard only exposes chart metadata and metric values, not raw data. diff --git a/docs/contributing/contributing-documentation.md b/docs/contributing/contributing-documentation.md index 22df9fc3e..76fc609d5 100644 --- a/docs/contributing/contributing-documentation.md +++ b/docs/contributing/contributing-documentation.md @@ -18,7 +18,7 @@ The Netdata team aggregates and publishes all documentation at [learn.netdata.cl ## Before you get started Anyone interested in contributing to documentation should first read the [Netdata style -guide](/docs/contributing/style-guide.md) and the [Netdata Community Code of Conduct](/CODE_OF_CONDUCT.md). +guide](/docs/contributing/style-guide.md) and the [Netdata Community Code of Conduct](https://learn.netdata.cloud/contribute/code-of-conduct). Netdata's documentation uses Markdown syntax. If you're not familiar with Markdown, read the [Mastering Markdown](https://guides.github.com/features/mastering-markdown/) guide from GitHub for the basics on creating @@ -92,7 +92,7 @@ request based on the changes you made in the new branch of your fork. ## Making a pull request -Pull requests (PRs) should be concise and informative. See our [PR guidelines](/CONTRIBUTING.md#pr-guidelines) for +Pull requests (PRs) should be concise and informative. See our [PR guidelines](https://learn.netdata.cloud/contribute/handbook#pr-guidelines) for specifics. - The title must follow the [imperative mood](https://en.wikipedia.org/wiki/Imperative_mood) and be no more than ~50 diff --git a/docs/contributing/style-guide.md b/docs/contributing/style-guide.md index 625237bc0..025b45f64 100644 --- a/docs/contributing/style-guide.md +++ b/docs/contributing/style-guide.md @@ -421,7 +421,7 @@ In Markdown, use the standard image syntax, `![]()`, and place the alt text betw using our logo: ```markdown -![The Netdata logo](../../web/gui/images/netdata-logomark.svg) +![The Netdata logo](/web/gui/static/img/netdata-logomark.svg) ``` Reference in-product text, code samples, and terminal output with actual text content, not screen captures or other diff --git a/docs/dashboard/customize.mdx b/docs/dashboard/customize.mdx index 2c82a1c50..d20337911 100644 --- a/docs/dashboard/customize.mdx +++ b/docs/dashboard/customize.mdx @@ -25,7 +25,7 @@ Here are a few popular settings: ### Change chart legend position Find this setting under the **Visual** tab. By default, Netdata places the [legend of -dimensions](/docs/dashboard/dimensions-contexts-families.mdx#dimensions) _below_ charts. Click this toggle to +dimensions](/docs/dashboard/dimensions-contexts-families.mdx#dimension) _below_ charts. Click this toggle to move the legend to the _right_ of charts. ### Change theme diff --git a/docs/dashboard/dimensions-contexts-families.mdx b/docs/dashboard/dimensions-contexts-families.mdx index da9aad78f..0c6dd2adc 100644 --- a/docs/dashboard/dimensions-contexts-families.mdx +++ b/docs/dashboard/dimensions-contexts-families.mdx @@ -26,7 +26,7 @@ utilization is represented as a percentage, disk I/O as `MiB/s`, and available R Beneath every chart (or on the right-side if you configure the dashboard) is a legend of dimensions. When there are multiple dimensions, you'll see a different entry in the legend for each dimension. -The **Apps CPU Time** chart (with the [context](#contexts) `apps.cpu`), which visualizes CPU utilization of +The **Apps CPU Time** chart (with the [context](#context) `apps.cpu`), which visualizes CPU utilization of different types of processes/services/applications on your node, always provides a vibrant example of a chart with multiple dimensions. diff --git a/docs/dashboard/import-export-print-snapshot.mdx b/docs/dashboard/import-export-print-snapshot.mdx index 7e94a52c8..1333efc2b 100644 --- a/docs/dashboard/import-export-print-snapshot.mdx +++ b/docs/dashboard/import-export-print-snapshot.mdx @@ -17,7 +17,7 @@ timeframe](/docs/dashboard/visualization-date-and-time-controls.mdx) when the al colleague for further analysis. Or, send the Netdata team a snapshot of your dashboard when [filing a bug -report](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2C+needs+triage&template=bug_report.md) on +report](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml) on GitHub. ![The export, import, and print diff --git a/docs/export/external-databases.md b/docs/export/external-databases.md index 309b03a87..6f7f488b6 100644 --- a/docs/export/external-databases.md +++ b/docs/export/external-databases.md @@ -51,7 +51,7 @@ documentation and the [enabling a connector](/docs/export/enable-connector.md) d - **KairosDB**: [Graphite](/exporting/graphite/README.md), [OpenTSDB](/exporting/opentsdb/README.md) - **M3DB**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md) - **MetricFire**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md) -- **MongoDB**: [MongoDB](/exporting/mongodb/) +- **MongoDB**: [MongoDB](/exporting/mongodb/README.md) - **New Relic**: [Prometheus remote write](/exporting/prometheus/remote_write/README.md) - **OpenTSDB**: [OpenTSDB](/exporting/opentsdb/README.md), [Prometheus remote write](/exporting/prometheus/remote_write/README.md) @@ -70,7 +70,7 @@ documentation and the [enabling a connector](/docs/export/enable-connector.md) d Can't find your preferred external time-series database? Ask our [community](https://community.netdata.cloud/) for solutions, or file an [issue on -GitHub](https://github.com/netdata/netdata/issues/new?labels=bug%2C+needs+triage&template=bug_report.md). +GitHub](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml). ## What's next? diff --git a/docs/getting-started.md b/docs/getting-started.md deleted file mode 100644 index 2d1f3de6d..000000000 --- a/docs/getting-started.md +++ /dev/null @@ -1,236 +0,0 @@ - - -# Get started guide - -Thanks for trying the Netdata Agent! In this getting started guide, we'll quickly walk you through the first steps you -should take after installing the Agent. - -The Agent can collect thousands of metrics in real-time and use its database for long-term metrics storage without any -configuration, but there are some valuable things to know to get the most out of Netdata based on your needs. - -We'll skip right into some technical details, so if you're brand-new to monitoring the health and performance of systems -and applications, our [**step-by-step guide**](/docs/guides/step-by-step/step-00.md) might be a better fit. - -> If you haven't installed Netdata yet, visit the [installation instructions](/packaging/installer/README.md) for -> details, including our one-liner script, which automatically installs Netdata on almost all Linux distributions. - -## Access the dashboard - -Open up your web browser of choice and navigate to `http://NODE:19999`, replacing `NODE` with the IP address or hostname -of your Agent. Hit **Enter**. Welcome to Netdata! - -![Animated GIF of navigating to the -dashboard](https://user-images.githubusercontent.com/1153921/80825153-abaec600-8b94-11ea-8b17-1b770a2abaa9.gif) - -**What's next?**: - -- Read more about the [standard Netdata dashboard](/web/gui/). -- Learn all the specifics of [using charts](/web/README.md#using-charts) or the differences between [charts, - context, and families](/web/README.md#charts-contexts-families). - -## Configuration basics - -Netdata primarily uses the `netdata.conf` file for custom configurations. - -On most systems, you can find that file at `/etc/netdata/netdata.conf`. - -> Some operating systems will place your `netdata.conf` at `/opt/netdata/etc/netdata/netdata.conf`, so check there if -> you find nothing at `/etc/netdata/netdata.conf`. - -The `netdata.conf` file is broken up into various sections, such as `[global]`, `[web]`, `[registry]`, and more. By -default, most options are commented, so you'll have to uncomment them (remove the `#`) for Netdata to recognize your -change. - -Once you save your changes, [restart Netdata](#start-stop-and-restart-netdata) to load your new configuration. - -**What's next?**: - -- [Change how long Netdata stores metrics](#change-how-long-netdata-stores-metrics) by changing the `page cache size` - and `dbengine disk space` settings in `netdata.conf`. -- Move Netdata's dashboard to a [different port](/web/server/) or enable TLS/HTTPS - encryption. -- See all the `netdata.conf` options in our [daemon configuration documentation](/daemon/config/). -- Run your own [registry](/registry/README.md#run-your-own-registry). - -## Change how long Netdata stores metrics - -Netdata can store long-term, historical metrics out of the box. A custom database uses RAM to store recent metrics, -ensuring dashboards and API queries are extremely responsive, while "spilling" historical metrics to disk. This -configuration keeps RAM usage low while allowing for long-term, on-disk metrics storage. - -You can tweak this custom _database engine_ to store a much larger dataset than your system's available RAM, -particularly if you allow Netdata to use slightly more RAM and disk space than the default configuration. - -Read our guide on [changing how long Netdata stores metrics](/docs/store/change-metrics-storage.md) to learn more and -use our the embedded database engine to figure out the exact settings you'll need to store historical metrics right in -the Agent's database. - -**What's next?**: - -- Learn more about the [memory requirements for the database - engine](/database/engine/README.md#memory-requirements) to understand how much RAM/disk space you should commit - to storing historical metrics. - -## Collect data from more sources - -When Netdata _starts_, it auto-detects dozens of **data sources**, such as database servers, web servers, and more. To -auto-detect and collect metrics from a service or application you just installed, you need to [restart -Netdata](#start-stop-and-restart-netdata). - -> There is one exception: When Netdata is running on the host (as in not in a container itself), it will always -> auto-detect containers and VMs. - -However, auto-detection only works if you installed the source using its standard installation procedure. If Netdata -isn't collecting metrics after a restart, your source probably isn't configured correctly. Look at the [external plugin -documentation](/collectors/plugins.d/) to find the appropriate module for your source. Those pages will contain -more information about how to configure your source for auto-detection. - -Some modules, like `chrony`, are disabled by default and must be enabled manually for auto-detection to work. - -Once Netdata detects a valid source of data, it will continue trying to collect data from it. For example, if -Netdata is collecting data from an Nginx web server, and you shut Nginx down, Netdata will collect new data as soon as -you start the web server back up—no restart necessary. - -### Configure plugins - -Even if Netdata auto-detects your service/application, you might want to configure what, or how often, Netdata is -collecting data. - -Netdata uses **internal** and **external** plugins to collect data. Internal plugins run within the Netdata dæmon, while -external plugins are independent processes that send metrics to Netdata over pipes. There are also plugin -**orchestrators**, which are external plugins with one or more data collection **modules**. - -You can configure both internal and external plugins, along with the individual modules. There are many ways to do so: - -- In `netdata.conf`, `[plugins]` section: Enable or disable internal or external plugins with `yes` or `no`. -- In `netdata.conf`, `[plugin:XXX]` sections: Each plugin has a section for changing collection frequency or passing - options to the plugin. -- In `.conf` files for each external plugin: For example, at `/etc/netdata/python.d.conf`. -- In `.conf` files for each module : For example, at `/etc/netdata/python.d/nginx.conf`. - -It's complex, so let's walk through an example of the various `.conf` files responsible for collecting data from an -Nginx web server using the `nginx` module and the `python.d` plugin orchestrator. - -First, you can enable or disable the `python.d` plugin entirely in `netdata.conf`. - -```conf -[plugins] - # Enabled - python.d = yes - # Disabled - python.d = no -``` - -You can also configure the entire `python.d` external plugin via the `[plugin:python.d]` section in `netdata.conf`. -Here, you can change how often Netdata uses `python.d` to collect metrics or pass other command options: - -```conf -[plugin:python.d] - update every = 1 - command options = -``` - -The `python.d` plugin has a separate configuration file at `/etc/netdata/python.d.conf` for enabling and disabling -modules. You can use the `edit-config` script to edit the file, or open it with your text editor of choice: - -```bash -sudo /etc/netdata/edit-config python.d.conf -``` - -Finally, the `nginx` module has a configuration file called `nginx.conf` in the `python.d` folder. Again, use -`edit-config` or your editor of choice: - -```bash -sudo /etc/netdata/edit-config python.d/nginx.conf -``` - -In the `nginx.conf` file, you'll find additional options. The default works in most situations, but you may need to make -changes based on your particular Nginx setup. - -**What's next?**: - -- Look at the [full list of data collection modules](/collectors/COLLECTORS.md) - to configure your sources for auto-detection and monitoring. -- Improve the [performance](/docs/guides/configure/performance.md) of Netdata on low-memory systems. -- Configure `systemd` to expose [systemd services - utilization](/collectors/cgroups.plugin/README.md#monitoring-systemd-services) metrics automatically. -- [Reconfigure individual charts](/daemon/config/README.md#per-chart-configuration) in `netdata.conf`. - -## Health monitoring and alarms - -Netdata comes with hundreds of health monitoring alarms for detecting anomalies on production servers. If you're running -Netdata on a workstation, you might want to disable Netdata's alarms. - -Edit your `/etc/netdata/netdata.conf` file and set the following: - -```conf -[health] - enabled = no -``` - -If you want to keep health monitoring enabled, but turn email notifications off, edit your `health_alarm_notify.conf` -file with `edit-config`, or with the text editor of your choice: - -```bash -sudo /etc/netdata/edit-config health_alarm_notify.conf -``` - -Find the `SEND_EMAIL="YES"` line and change it to `SEND_EMAIL="NO"`. - -**What's next?**: - -- Follow the [health quickstart](/health/QUICKSTART.md) to locate and edit existing health entities, and then - create your own. -- See all the alarm options via the [health configuration reference](/health/REFERENCE.md). -- Add a new notification method, like [Slack](/health/notifications/slack/). - -## Monitor multiple systems with Netdata Cloud - -If you have the Agent installed on multiple nodes, you can use Netdata Cloud in two ways: Monitor the health and -performance of an entire infrastructure via the Netdata Cloud web application, or use the Visited Nodes menu that's -built into every dashboard. - -![The War Room -Overview](https://user-images.githubusercontent.com/1153921/102651377-b1f4b100-4129-11eb-8e60-d2995d258c16.png) - -You can use these features together or separately—the decision is up to you and the needs of your infrastructure. - -**What's next?**: - -- Sign up for [Netdata Cloud](https://app.netdata.cloud). -- Read the [infrastructure monitoring quickstart](/docs/quickstart/infrastructure.md). -- Better understand how the Netdata Agent connects securely to Netdata Cloud with [connection process](/claim/README.md) and - [Agent-Cloud link](/aclk/README.md) documentation. - -## Start, stop, and restart Netdata - -When you install Netdata, it's configured to start at boot, and stop and restart/shutdown. You shouldn't need to start -or stop Netdata manually, but you will probably need to restart Netdata at some point. - -- To **start** Netdata, open a terminal and run `sudo systemctl start netdata`. -- To **stop** Netdata, run `sudo systemctl stop netdata`. -- To **restart** Netdata, run `sudo systemctl restart netdata`. - -See our doc on [starting, stopping, and restarting](/docs/configure/start-stop-restart.md) the Netdata Agent for -details. - -## What's next? - -Even after you've configured `netdata.conf`, tweaked alarms, learned the basics of performance troubleshooting, and -connected all your systems in Netdata Cloud or added them to the Visited nodes menu, you've just gotten started with -Netdata. - -Take a look at some more advanced features and configurations: - -- Centralize Netdata metrics from many systems with [streaming](/streaming/README.md) -- Enable long-term archiving of Netdata metrics via [exporting engine](/exporting/README.md) to time-series databases. -- Improve security by putting Netdata behind an [Nginx proxy with SSL](/docs/Running-behind-nginx.md). - -Or, learn more about how you can contribute to [Netdata core](/CONTRIBUTING.md) or our -[documentation](/docs/contributing/contributing-documentation.md)! - -[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Fgetting-started&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) diff --git a/docs/guides/collect-unbound-metrics.md b/docs/guides/collect-unbound-metrics.md index a6a4de02f..5709c872c 100644 --- a/docs/guides/collect-unbound-metrics.md +++ b/docs/guides/collect-unbound-metrics.md @@ -134,7 +134,7 @@ file](https://github.com/netdata/go.d.plugin/blob/master/config/go.d/unbound.con Now that you're collecting metrics from your Unbound servers, let us know how it's working for you! There's always room for improvement or refinement based on real-world use cases. Feel free to [file an -issue](https://github.com/netdata/netdata/issues/new?labels=bug%2C+needs+triage&template=bug_report.md) with your +issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml) with your thoughts. [![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2Fguides%2Funbound-metrics&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) diff --git a/docs/guides/longer-metrics-storage.md b/docs/guides/longer-metrics-storage.md index 85b397f6d..b682125f5 100644 --- a/docs/guides/longer-metrics-storage.md +++ b/docs/guides/longer-metrics-storage.md @@ -57,7 +57,7 @@ compressed metrics. The default settings retain about two day's worth of metrics every second. [**See our database engine -calculator**](/docs/store/change-metrics-storage.md#calculate-the-system-resources-RAM-disk-space-needed-to-store-metrics) +calculator**](/docs/store/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics) to help you correctly set `dbengine multihost disk space` based on your needs. The calculator gives an accurate estimate based on how many child nodes you have, how many metrics your Agent collects, and more. diff --git a/docs/guides/monitor-cockroachdb.md b/docs/guides/monitor-cockroachdb.md index 0307381e3..327237836 100644 --- a/docs/guides/monitor-cockroachdb.md +++ b/docs/guides/monitor-cockroachdb.md @@ -115,7 +115,7 @@ guide](/health/QUICKSTART.md). Now that you're collecting metrics from your CockroachDB databases, let us know how it's working for you! There's always room for improvement or refinement based on real-world use cases. Feel free to [file an -issue](https://github.com/netdata/netdata/issues/new?labels=bug%2C+needs+triage&template=bug_report.md) with your +issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml) with your thoughts. Also, be sure to check out these useful resources: diff --git a/docs/guides/monitor-hadoop-cluster.md b/docs/guides/monitor-hadoop-cluster.md index dce56b7c7..69f2bc8e3 100644 --- a/docs/guides/monitor-hadoop-cluster.md +++ b/docs/guides/monitor-hadoop-cluster.md @@ -73,8 +73,7 @@ The JSON result for a DataNode's `/jmx` endpoint is slightly different: ```json { "beans" : [ { - "name" : "Hadoop:service=DataNode,name=DataNodeActivity-dev-slave-01.dev.loc -al-9866", + "name" : "Hadoop:service=DataNode,name=DataNodeActivity-dev-slave-01.dev.local-9866", "modelerType" : "DataNodeActivity-dev-slave-01.dev.local-9866", "tag.SessionId" : null, "tag.Context" : "dfs", @@ -192,7 +191,7 @@ documentation](/health/README.md). If you're having issues with Netdata auto-detecting your HDFS/Zookeeper servers, or want to help improve how Netdata collects or presents metrics from these services, feel free to [file an -issue](https://github.com/netdata/netdata/issues/new?labels=bug%2C+needs+triage&template=bug_report.md). +issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml). - Read up on the [HDFS configuration file](https://github.com/netdata/go.d.plugin/blob/master/config/go.d/hdfs.conf) to understand how to configure diff --git a/docs/guides/monitor/kubernetes-k8s-netdata.md b/docs/guides/monitor/kubernetes-k8s-netdata.md index 5d4886e68..bd893ede6 100644 --- a/docs/guides/monitor/kubernetes-k8s-netdata.md +++ b/docs/guides/monitor/kubernetes-k8s-netdata.md @@ -1,6 +1,6 @@