├── runtime.txt ├── requirements.txt ├── netlify.toml ├── pt ├── docs │ ├── README.md │ ├── a-github-star-is-important.md │ ├── Donations-netdata-has-received.md │ └── Demo-Sites.md └── packaging │ └── installer │ └── README.md ├── zh ├── docs │ ├── a-github-star-is-important.md │ ├── Running-behind-caddy.md │ ├── Donations-netdata-has-received.md │ ├── Running-behind-lighttpd.md │ ├── why-netdata │ │ └── 1s-granularity.md │ ├── tutorials │ │ └── longer-metrics-storage.md │ ├── Demo-Sites.md │ ├── Running-behind-nginx.md │ ├── getting-started.md │ ├── Running-behind-haproxy.md │ └── terms-of-use.md └── packaging │ ├── installer │ ├── UNINSTALL.md │ ├── UPDATE.md │ └── README.md │ ├── makeself │ └── README.md │ └── maintainers │ └── README.md ├── kr └── docs │ ├── a-github-star-is-important.md │ ├── Running-behind-caddy.md │ ├── Running-behind-lighttpd.md │ ├── Donations-netdata-has-received.md │ ├── why-netdata │ └── 1s-granularity.md │ ├── Demo-Sites.md │ ├── Running-behind-nginx.md │ ├── Running-behind-haproxy.md │ └── getting-started.md ├── README.md └── LICENSE /runtime.txt: -------------------------------------------------------------------------------- 1 | 3.6 2 | -------------------------------------------------------------------------------- /requirements.txt: -------------------------------------------------------------------------------- 1 | mkdocs>=1.0.1 2 | mkdocs-material 3 | -------------------------------------------------------------------------------- /netlify.toml: -------------------------------------------------------------------------------- 1 | # Settings in the [build] context are global and are applied to all contexts 2 | # unless otherwise overridden by more specific contexts. 3 | [build] 4 | # Directory to change to before starting a build. 5 | # base = "." 6 | 7 | # Directory (relative to root of your repo) that contains the deploy-ready 8 | # HTML files and assets generated by the build. 9 | publish = "netdata/docs/generator/build" 10 | 11 | # Default build command. 12 | command = "./buildhtml.sh" 13 | -------------------------------------------------------------------------------- /pt/docs/README.md: -------------------------------------------------------------------------------- 1 | # Leia nossa documentação em 2 | # Read documentation on 3 | 4 | Bem-vindo a documentação do Netdata! Embora você possa ler a documentação do Netdata aqui ou em todo o repositório do Netdata, nossa intenção é que essas páginas sejam lidas em [docs.netdata.cloud](https://docs.netdata.cloud). 5 | 6 | Os links entre as páginas de documentação funcionarão bem aqui, mas a formatação pode não ser perfeita, pois nosso site de documentação usa alguns recursos extras do Markdown aos quais o GitHub não suporta nativamente. Outras coisas podem estar faltando ou parecer menos perfeitas. 7 | 8 | Agora vá lá e construa uma infraestrutura excepcional. 9 | -------------------------------------------------------------------------------- /zh/docs/a-github-star-is-important.md: -------------------------------------------------------------------------------- 1 | # 在 GitHub 上支持我们是非常重要的 2 | 3 | 如果你**在 GitHub 上支持我们**，那么这将会扩大 Netdata 的影响范围，在社区里，这会更加吸引那些愿意为 Netdata 做出贡献的人。 4 | 5 | 与第一个版本相比，Netdata 现在的更新速度是**原来的两倍**，几乎所有错误都得到了妥善的解决，功能也更加完善了。这是因为很多人发现 Netdata 非常有用，每天他们都会在家里或在工作中使用它，**依赖 Netdata **并**帮助 Netdata 发展**。 6 | 7 | **在 GitHub 支持我们**也会继续**激励**我们。如果您说您认为我们的工作**很有用**。这会继续激励我们更加努力工作，让 **Netdata 变得更好**。 8 | 所以，麻烦您在本页的右上角点击一下，**给 Netdata 一个鼓励**， 9 | 10 | 谢谢您！ 11 | 12 | Costa Tsaousis 13 | 14 | [![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%2Fa-github-star-is-important&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 15 | -------------------------------------------------------------------------------- /kr/docs/a-github-star-is-important.md: -------------------------------------------------------------------------------- 1 | # A GitHub star는 중요합니다 2 | 3 | **GitHub stars** 를 통해 Netdata를 더 널리 알리고, 커뮤니티를 활성화시키며 Netdata에 기여할 능력있는 사람들을 더 불러 모을 수 있습니다. 4 | 5 | 첫 번째 릴리스와 비교하면 Netdata는 **두 배 가량** 빨라졌고 모든 버그가 해결되었으며, 다양한 기능들이 추가되었습니다. 많은 사람들이 직장이나 집에서 Netdata를 항상 이용하고 유용하다 여기며, Netdata를 필요로 하고, Netdata에 기여하기 때문에 Netdata는 발전할 수 있었습니다. 6 | 7 | **GitHub stars** 는 우리에게 동기를 부여합니다. **Github star**를 통해 사용자는 우리의 작업이 **유용하다**는 것을 표현할 수 있습니다. 그것은 우리에게 이 일을 계속해서 진행할 힘을 주고 더 열심히 작업하게 만들며, 더 나은 프로젝트가 되도록 합니다. 8 | 9 | 그러니, Netdata를 유용히 사용하셨다면 이 페이지의 좌측 상단에 있는 star 버튼을 눌러 Netdata에 **Github star**를 주세요. 10 | 11 | 감사합니다! 12 | 13 | Costa Tsaousis 14 | 15 | [![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%2Fa-github-star-is-important&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 16 | -------------------------------------------------------------------------------- /zh/docs/Running-behind-caddy.md: -------------------------------------------------------------------------------- 1 | # Netdata via Caddy 2 | 3 | #通过Caddy运行Netdata 4 | 5 | 要通过[Caddy的代理](https://caddyserver.com/docs/proxy)运行Netdata，需要设置Caddyfile： 6 | 7 | ```caddyfile 8 | netdata.domain.tld { 9 | proxy / localhost:19999 10 | } 11 | ``` 12 | 13 | 可以根据需要在大括号之间添加其他命令。 14 | 15 | 在子文件夹中运行 Netdata： 16 | 17 | ```caddyfile 18 | netdata.domain.tld { 19 | proxy /netdata/ localhost:19999 { 20 | without /netdata 21 | } 22 | } 23 | ``` 24 | 25 | ##限制直接访问 Netdata 26 | 27 | 你还需要指定 Netdata 仅监听 `127.0.0.1` 或者 `::1`。 28 | 29 | 要限制仅从本地主机访问 Netdata，请设置`/etc/netdata/netdata.conf`中的 `bind socket to IP = 127.0.0.1`或`bind socket to IP = ::1`。 30 | 31 | [![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%2FRunning-behind-caddy&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 32 | -------------------------------------------------------------------------------- /kr/docs/Running-behind-caddy.md: -------------------------------------------------------------------------------- 1 | # Caddy를 통한 Netdata 2 | 3 | [Caddy의 프록시 기능](https://caddyserver.com/docs/proxy)을 이용해 Netdata를 작동시키기 위해 아래와 같이 Caddyfile을 설정하세요. 4 | 5 | ```caddyfile 6 | netdata.domain.tld { 7 | proxy / localhost:19999 8 | } 9 | ``` 10 | 11 | 필요에 따라 다른 지시문을 중괄호 간에 추가할 수 있습니다. 12 | 13 | 하위 폴더에서 Netdata를 실행시키려면 아래를 참고하세요. 14 | 15 | ```caddyfile 16 | netdata.domain.tld { 17 | proxy /netdata/ localhost:19999 { 18 | without /netdata 19 | } 20 | } 21 | ``` 22 | 23 | ## Netdata에 직접 접근 제한 24 | 25 | `127.0.0.1`이나 `::1`에서만 Netdata에 접근 가능하도록 지시할 수 있습니다. 26 | 27 | localhost에서만 Netdata를 접속 가능하게 제한하기 위해 `/etc/netdata/netdata.conf` 파일에서 `bind socket to IP = 127.0.0.1`로 설정하거나 `bind socket to IP = ::1`로 설정하십시오. 28 | 29 | [![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%2FRunning-behind-caddy&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 30 | -------------------------------------------------------------------------------- /zh/packaging/installer/UNINSTALL.md: -------------------------------------------------------------------------------- 1 | ## 卸载Netdata 2 | 3 | Netdata包含了自动卸载程序，它可以把Netdata从您的服务器中完整地删除。卸载程序仅需要“.environment”文件，这个文件是被安装程序创建的，它应在${NETDATA_USER_CONFIG_DIR} 中(其默认位置应为： /etc/netdata/.environment)。此文件包含一些安装程序留下的参数，这些参数在卸载过程中是必需的。其主要有两个参数： 4 | ``` 5 | NETDATA_PREFIX 6 | NETDATA_ADDED_TO_GROUPS 7 | ``` 8 | 9 | 卸载流程如下： 10 | 11 | 1. 找到你的“.environment”文件 12 | 2. 如果您找不到该文件，请创建包含以下内容的新文件： 13 | ``` 14 | NETDATA_PREFIX="" # put what you used as a parameter to shell installed `--install` flag. Otherwise it should be empty 15 | NETDATA_ADDED_TO_GROUPS="" # Additional groups for a user running netdata process 16 | ``` 17 | 3. 运行： ./packaging/installer/netdata-uninstaller.sh --yes --env 18 | 4. 卸载完成 19 | 20 | 注意：此卸载方法是为“使用netdata-installer.sh或kickstart脚本进行安装”的用户而编写的。如果您使用的是包管理器来安装Netdata，使用这一方法可能无法成功地卸载。 21 | 22 | 译者注：请以英语原版为准 23 | 24 | [![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%2Finstaller%2FUNINSTALL&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 25 | -------------------------------------------------------------------------------- /pt/docs/a-github-star-is-important.md: -------------------------------------------------------------------------------- 1 | # Uma estrela no Github é importante 2 | # A GitHub star is important 3 | 4 | **Estrela no Github** permite o Netdata a expandir seu alcance, sua comunidade, atraindo especialmente pessoas com habilidades dispostas a contribuir. 5 | 6 | Comparada com sua primeira versão, o Netdata é agora **duas vezes mais rápido**, tendo todos os seus bugs resolvidos com muito mais funcionalidades. Isso aconteceu porque muitas pessoas o acham útil, usam diariamente em casa e no trabalho, **confiam nele** e **contribuem para ele**. 7 | 8 | **Estrela no Github** também nos **motivam**. Elas afirmam que você acha nosso trabalho **útil**. Elas nos dão força para continuar, trabalhar **mais** para torná-lo ainda **melhor**. 9 | 10 | Então, dê ao Netdata uma **Estrela no Github**, no canto superior direito desta página. 11 | 12 | Muito obrigado! 13 | 14 | Costa Tsaousis 15 | 16 | [![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%2Fa-github-star-is-important&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 17 | -------------------------------------------------------------------------------- /zh/packaging/makeself/README.md: -------------------------------------------------------------------------------- 1 | # 构建Netdata静态二进制分发包 2 | 3 | 要构建Netdata静态二进制64位分发包，请运行： 4 | 5 | ```bash 6 | $ cd /path/to/netdata.git 7 | $ ./packaging/makeself/build-x86_64-static.sh 8 | ``` 9 | 10 | 这个脚本会进行以下工作: 11 | 12 | 1. 使用Alpine Linux设置一个新的Docker容器 13 | 2. 安装所需的alpine包（构建环境，依赖等） 14 | 3. 下载并编译与Netdata一同打包的第三方应用程序（包括但不限于`bash`，`curl`） 15 | 4. 编译Netdata 16 | 17 | 当其完成后，一个名为`netdata-vX.X.X-gGITHASH-x86_64-DATE-TIME.run`的文件将会在当前目录中被创建。这是Netdata的二进制包，它可以在其他计算机上安装Netdata。 18 | 19 | --- 20 | 21 | ## 使用调试信息构建二进制静态分发包 22 | 23 | 要使用调试/跟踪信息构建Netdata二进制静态分发包，请使用以下命令： 24 | 25 | ```bash 26 | $ cd /path/to/netdata.git 27 | $ ./packaging/makeself/build-x86_64-static.sh debug 28 | ``` 29 | 30 | 这些二进制文件没有进行过优化（它们的运行速度较慢），且它们的某些功能被禁用了（如日志溢出保护），但是，它的其他功能启用（如`debug flags`）并不会被剥离（注意：二进制文件较大，因为它包括了源代码跟踪信息）。 31 | 32 | #### 调试Netdata二进制文件 33 | 34 | 一旦您安装了包含调试信息的二进制分发包，您就必须安装`valgrind`并运行此命令来启动Netdata： 35 | 36 | ```bash 37 | PATH="/opt/netdata/bin:${PATH}" valgrind --undef-value-errors=no /opt/netdata/bin/srv/netdata -D 38 | ``` 39 | 40 | 上面的这条命令，将会在`valgrind`下运行Netdata。即使Netdata在`valgrind`下运行，但是速度还是会慢10倍并且会占用更多的内存。 41 | 42 | 如果Netdata崩溃，`valgrind`将输出问题的堆栈跟踪。请您打开一个Github问题让我们知道这一问题的发生。 43 | 44 | 要在`valgrind`下停止运行netdata，请在控制台上按Control-C。 45 | 46 | > 如果您在valgrind中省略了参数`--undef-value-errors = no`，您将会获得有关依赖未初始化的数百个错误。这是正常的。Valgrind具有启发式功能，它可以防止系统库打印此类错误，但对于静态Netdata二进制文件，所有必需的库都已经内置于Netdata中。因此，valgrind无法应用其启发式功能。 47 | 48 | [![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%2Fmakeself%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 49 | -------------------------------------------------------------------------------- /zh/packaging/installer/UPDATE.md: -------------------------------------------------------------------------------- 1 | # 如何在安装后更新Netdata？ 2 | 3 | ![image8](https://cloud.githubusercontent.com/assets/2662304/14253735/536f4580-fa95-11e5-9f7b-99112b31a5d7.gif) 4 | 5 | 我们强烈建议您使用最新的版本，因为我们正在不断地开发并完善它。 6 | 7 | 更新方法取决于你如何安装的Netdata： 8 | 9 | ## 如果你是使用Git从我们的GitHub储存库中下载安装的 10 | 11 | ### 手动更新 12 | 13 | 在`v1.12.0-rc2-52`版本前，我们使用`netdata-updater.sh`脚本以获取更新，但它现在已被弃用了。现在我们使用`netdata-installer.sh`脚本。安装程序会保留您的设置，并在用户配置目录下的`.environment`文件中更新安装信息。 14 | 15 | ```sh 16 | # 转到下载目录 17 | cd /path/to/git/downloaded/netdata 18 | 19 | # 下载最新的版本 20 | git pull 21 | 22 | # 运行Netdata安装程序 23 | sudo ./netdata-installer.sh 24 | ``` 25 | 26 | _Netdata将会以最新的版本为你服务_ 27 | 28 | 请注意：Netdata现在可能有新的功能，或者某些旧的功能现在表现不同。在更新后请注意这些变化。 29 | 30 | ### 手动获取每日更新 31 | 32 | 如果运行如下命令，`kickstart.sh`one-liner将对最新的每日更新进行一次性更新： 33 | ``` 34 | bash <(curl -Ss https://my-netdata.io/kickstart.sh) --no-updates 35 | ``` 36 | 37 | ### 自动升级 38 | 39 | _请您慎重考虑自动更新的风险。有些事情或许会出错。请密切关注它，如果自动更新出现了故障，请手动进行更新。_ 40 | 41 | 如果你运行`netdata-installer.sh`脚本并带上`--auto-update`或`-u`参数时，它会在`/etc/cron.daily/`或`/etc/periodic/daily/`处生成`netdata-updater`脚本。每当`netdata-updater`被执行时，它会检查是否有更新的每日更新，然后下载并安装它们。 42 | 43 | 请注意，2019年1月之后，`kickstart.sh`one liner` bash<（curl-ss https://my netdata.io/kickstart.sh）`使用自动更新选项调用`netdata installer.sh`。因此，如果你只运行了一次没有参数的命令，你的Netdata仍将保持自动更新。 44 | 45 | ## 如果是您使用二进制包安装的 46 | 47 | 如果您使用二进制包安装了Netdata，最好的方法是从分发商中**获取一个更新的**安装副本（注意：这包括通过`kickstart-base64.sh`进行的二进制安装，它需要被再次执行）。 48 | 49 | 如果您从源代码中找不到更新版本的Netdata，我们建议您卸载您现在的版本，并按照[安装文档](README.md)中的说明安装新版本的Netdata。 50 | 51 | 译者注：请以英语原版为准 52 | 53 | [![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%2Finstaller%2FUPDATE&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 54 | -------------------------------------------------------------------------------- /zh/docs/Donations-netdata-has-received.md: -------------------------------------------------------------------------------- 1 | # 赞助 2 | 3 | 这是我们收到的 Netdata 赞助名单（按姓名字母顺序排序）： 4 | 5 | 赞助了什么|相关链接|赞助人（公司）|赞助描述 6 | ----:|:-----:|:---:|:----------- 7 | Packages Distribution|-|**[PackageCloud.io](https://packagecloud.io/)**|**PackageCloud.io** 赞助了他们的 Package Distribution 服务 8 | Cross Browser Testing|-|**[BrowserStack.com](https://www.browserstack.com/)**|**BrowserStack.com**赞助了他们的 Browser Testing 服务(包括Live, Screenshots, Responsive) 9 | 云服务器|[cdn77.my-netdata.io](http://cdn77.my-netdata.io)|**[CDN77.com](https://www.cdn77.com/)**|**CDN77.com**赞助了一台带有 CDN 服务的云服务器（2 CPU cores, 4GB RAM and 20GB HD） 10 | Localization Management|[netdata localization project](https://crowdin.com/project/netdata) (check issue [#279](https://github.com/netdata/netdata/issues/279))|**[Crowdin.com](https://crowdin.com/)**|**Crowdin.com**赞助了一个 Localization Management Platform 的开源许可证 11 | 云服务器|[london.my-netdata.io](https://london.my-netdata.io) (Several VMs)|**[DigitalOcean.com](https://www.digitalocean.com/)**|**DigitalOcean.com**捐赠了 1000 美元的优惠券（云计算服务）。感谢 [Justin Paine](https://github.com/xxdesmus) 12 | 开发IDE|-|**[JetBrains.com](https://www.jetbrains.com/)**|**JetBrains.com**为 4 位开发人员提供了 IDE 的 1 年开源许可证 13 | 云服务器|[octopuscs.my-netdata.io](https://octopuscs.my-netdata.io)|**[OctopusCS.com](https://octopuscs.com/)**|**OctopusCS.com**赞助了一台云服务器（4 CPU cores, 16GB RAM and 50GB HD） 14 | 云服务器|[ventureer.my-netdata.io](https://ventureer.my-netdata.io)|**[Ventureer.com](https://ventureer.com/)**|**Ventureer.com**赞助了一台云服务器（4 CPU cores, 8GB RAM and 50GB HD） 15 | 云服务器|[stackscale.my-netdata.io](https://stackscale.my-netdata.io)|**[stackscale.com](https://www.stackscale.com/)**|**StackScale.com**赞助了一台云服务器（4 CPU cores, 16GB RAM and 100GB HD） 16 | 17 | 感谢有你 18 | 19 | --- 20 | 21 | **您想要赞助我们吗**我们希望改善 Netdata 的在线服务。我们还在尝试构建一个演示站点（VM）网络，用于展示 Netdata 的全部潜力。 22 | 23 | 请通过电子邮件 costa@tsaousis.gr 与我取得联系。 24 | 25 | [![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%2FDonations-netdata-has-received&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 26 | -------------------------------------------------------------------------------- /zh/docs/Running-behind-lighttpd.md: -------------------------------------------------------------------------------- 1 | # Netdata via lighttpd v1.4.x 2 | 3 | 通过lighttpd v1.4.x运行Netdata 4 | 5 | 这是用于通过lighttpd 1.4.46及更高版本访问子URL中的Netdata的配置： 6 | 7 | ```txt 8 | $HTTP["url"] =~ "^/netdata/" { 9 | proxy.server = ( "" => ("netdata" => ( "host" => "127.0.0.1", "port" => 19999 ))) 10 | proxy.header = ( "map-urlpath" => ( "/netdata/" => "/") ) 11 | } 12 | ``` 13 | 14 | 如果你使用的是较旧的lighttpd，则必须使用链路（例如bellow），如[在stackoverflow解答中所述](http://stackoverflow.com/questions/14536554/lighttpd-configuration-to-proxy-rewrite-from-one-domain-to-another)。 15 | 16 | ```txt 17 | $HTTP["url"] =~ "^/netdata/" { 18 | proxy.server = ( "" => ("" => ( "host" => "127.0.0.1", "port" => 19998 ))) 19 | } 20 | 21 | $SERVER["socket"] == ":19998" { 22 | url.rewrite-once = ( "^/netdata(.*)$" => "/$1" ) 23 | proxy.server = ( "" => ( "" => ( "host" => "127.0.0.1", "port" => 19999 ))) 24 | } 25 | ``` 26 | 27 | --- 28 | 29 | 如果服务器通过Web公开的唯一内容是Netdata（因此不需要重写子URL），那么你就可以不用写 30 | 31 | ``` 32 | proxy.server = ( "" => ( ( "host" => "127.0.0.1", "port" => 19999 ))) 33 | ``` 34 | 35 | 但是，如果它是公开的，则可能需要在其上进行身份验证。 htdigest支持如下的配置： 36 | 37 | ``` 38 | auth.backend = "htdigest" 39 | auth.backend.htdigest.userfile = "/etc/lighttpd/lighttpd.htdigest" 40 | auth.require = ( "" => ( "method" => "digest", 41 | "realm" => "netdata", 42 | "require" => "valid-user" 43 | ) 44 | ) 45 | ``` 46 | 47 | 其他身份验证方法以及有关htdigest的更多信息，可以在lighttpd的[mod_auth docs](http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModAuth)中找到。 48 | 49 | --- 50 | 51 | 似乎lighttpd（或其某些版本）无法代理压缩的Web响应。要解决此问题，请在Netdata中禁用Web响应压缩。 52 | 53 | 打开`/etc/netdata/netdata.conf` 并设置[global]\: 54 | 55 | ``` 56 | enable web responses gzip compression = no 57 | ``` 58 | 59 | ##限制直接访问Netdata 60 | 61 | 你还需要指示Netdata仅监听`127.0.0.1`或`:: 1`。 62 | 63 | 要限制仅从本地主机访问Netdata，请将`/etc/netdata/netdata.conf`中的`bind socket to IP = 127.0.0.1`或`bind socket to IP = :: 1`设置。 64 | 65 | [![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%2FRunning-behind-lighttpd&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 66 | -------------------------------------------------------------------------------- /kr/docs/Running-behind-lighttpd.md: -------------------------------------------------------------------------------- 1 | # lighttpd v1.4.x를 이용한 Netdata 2 | 3 | 이번 장은 lighttpd 1.4.46 버전과 그 이상의 버전으로 하위 URL로 Netdata에 접근하기 위한 설정을 설명합니다.: 4 | 5 | ```txt 6 | $HTTP["url"] =~ "^/netdata/" { 7 | proxy.server = ( "" => ("netdata" => ( "host" => "127.0.0.1", "port" => 19999 ))) 8 | proxy.header = ( "map-urlpath" => ( "/netdata/" => "/") ) 9 | } 10 | ``` 11 | 12 | 1.4.46 이전 버전의 lighttpd를 사용 중 이라면 [at this stackoverflow answer](http://stackoverflow.com/questions/14536554/lighttpd-configuration-to-proxy-rewrite-from-one-domain-to-another)에 설명된 것을 따라 아래와 같이 chain을 사용해야 합니다. 13 | 14 | ```txt 15 | $HTTP["url"] =~ "^/netdata/" { 16 | proxy.server = ( "" => ("" => ( "host" => "127.0.0.1", "port" => 19998 ))) 17 | } 18 | 19 | $SERVER["socket"] == ":19998" { 20 | url.rewrite-once = ( "^/netdata(.*)$" => "/$1" ) 21 | proxy.server = ( "" => ( "" => ( "host" => "127.0.0.1", "port" => 19999 ))) 22 | } 23 | ``` 24 | 25 | --- 26 | 27 | 서버가 웹을 통해 노출하는 컨텐츠가 Netdata 뿐이라면 (하위 경로를 다시 쓸 필요가 없는 경우라면) 작성할 필요가 없습니다. 28 | 29 | ``` 30 | proxy.server = ( "" => ( ( "host" => "127.0.0.1", "port" => 19999 ))) 31 | ``` 32 | 33 | 하지만 Netdata가 공개적인 경우 인증이 필요할 수 있습니다. htdigest 지원은 아래와 같습니다: 34 | 35 | ``` 36 | auth.backend = "htdigest" 37 | auth.backend.htdigest.userfile = "/etc/lighttpd/lighttpd.htdigest" 38 | auth.require = ( "" => ( "method" => "digest", 39 | "realm" => "netdata", 40 | "require" => "valid-user" 41 | ) 42 | ) 43 | ``` 44 | 45 | 다른 인증 방식이나 htdigest에 대한 더 많은 정보는 lighttpd의 [mod_auth docs](http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModAuth) 에서 찾아볼 수 있습니다. 46 | 47 | --- 48 | 49 | lighttpd (전체 혹은 일부 버전)에서 압축된 웹 응답을 프록시 하는데 실패하는 것 같습니다. 50 | 이 문제를 해결하려면 Netdata에서 웹 응답 압축을 비활성화 하십시오. 51 | 52 | `/etc/netdata/netdata.conf`를 열어 다음과 같이 [global]을 설정하십시오.: 53 | 54 | ``` 55 | enable web responses gzip compression = no 56 | ``` 57 | 58 | ## Netdata에 직접 접근 제한 59 | 60 | `127.0.0.1`나 `::1`를 통해서만 Netdata에 접근하도록 할 수 있습니다. 61 | 62 | localhost에서만 Netdata에 접근 가능하도록 제한하려면, `/etc/netdata/netdata.conf` 파일을 `bind socket to IP = 127.0.0.1` 나 `bind socket to IP = ::1`와 같이 설정하십시오. 63 | 64 | [![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%2FRunning-behind-lighttpd&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 65 | -------------------------------------------------------------------------------- /zh/docs/why-netdata/1s-granularity.md: -------------------------------------------------------------------------------- 1 | # 数据采集精度 2 | 3 | 为了更好地监测系统并诊断应用运行中出现的问题，在数据统计时使用更高的时间精度是非常有必要的。 4 | 5 | ## 为什么要选择Netdata？ 6 | 7 | - 世界正在不断地发展。如今，客户的体验受到服务器响应时间的影响，因此，SLA比以往更加紧凑。因此，使用刷新率为10秒的监控器来监控2秒的SLA是不切实际的。 8 | 9 | - IT服务正在变得虚拟化。与真实硬件不同，虚拟机环境不是稳定的，也不可以被预测。当你的服务需要资源时，你不能指望资源马上可用。虚拟环境的延迟受许多因素的影响，其中大多数的因素我们都无法控制，例如：主机托管商的维护策略，运行在相同物理服务器上的虚拟机的工作负载以及资源分配和限制虚拟机之间的策略，主机提供商供应的系统等。 10 | 11 | ## 其他服务商为什么不这样做？ 12 | 13 | 那么，为什么大多数监控平台和 SaaS 提供商都不提供高刷新率的监控指标？ 14 | 15 | 他们想这样做，但他们无法这样做，至少不是大规模的推广。 16 | 17 | 其原因在于他们的设计： 18 | 19 | 1. 时间序列数据库（prometheus，graphite，opentsdb，Influxdb等）集中了所有的监控指标。从规模上看，这些数据库很容易成为整个基础架构的瓶颈。 20 | 21 | 2. SaaS 提供商将其业务模型建立在指标的基础之上。除了时间序列数据库的瓶颈之外，它们还增加了带宽的成本。因此，大规模的支持高刷新率指标将会破坏他们的商业模式。 22 | 23 | 当然，大多数的服务商已经解决了这些问题：不是按比例放大，横向扩展。也就是说，他们不是通过投资更好的硬件，而是通过将服务分散，以便通过向其添加更多更小的节点来扩展它。 24 | 25 | 现在已经有许多服务商尝试解决这个问题。但到目前为止，所有的解决方案都需要集中的测试。因此，虽然问题以某种方式得到解决，但它仍然是所有监控平台的关键问题，也是监控成本增加的关键原因之一。 26 | 27 | 另一个重要的因素是运行时数据有效的收集方式。大多数的解决方案都无法完美地完成。数据收集会在运行时消耗大量的系统资源，在很大程度上影响受监控的系统和应用程序。 28 | 29 | 最后，收集每秒的数据是很困难的。繁忙的虚拟环境有 [大约100ms的固定延迟，随机分布到所有数据源](https://docs.google.com/presentation/d/18C8bCTbtgKDWqPa57GXIjB2PbjjpjsUNkLtZEz6YK8s/edit#slide=id.g422e696d87_0_57)。如果未正确地收集数据，则此延迟会引入上下 10％ 的随机误差，这对于监控系统而言是非常重要的。 30 | 31 | 因此，监控行业未能大规模提供高刷新率的指标，主要有以下三个原因： 32 | 33 | 1. 指标的集中化收集使得监控成本在该刷新率中效率低下。 34 | 2. 数据的收集方式需要优化，否则会显著影响被监控的系统或程序。 35 | 3. 数据的收集很困难，特别是在繁忙的虚拟环境中。 36 | 37 | ## Netdata有什么同的做法？ 38 | 39 | Netdata 把监控分散了。每个 Netdata 节点都是独立的。它在本地收集指标，在本地存储它们，然后对它们进行检查并在本地发出警报，从而为仪表板提供 API 使数据可视化。这允许 Netdata 被无限地扩展。 40 | 41 | 当然，Netdata 可以在需要时集中储存指标。例如，在分散节点上保存数据是不切实际的。对于这些情况来说，Netdata 实时地收集、传输数据，从分散节点传输到附近的一个或多个中心节点。这些数据会在集中后被再次分发。在大型的基础设施上，可能存在着许多个中心点。 42 | 43 | 为了消除繁忙的虚拟环境中数据收集延迟导致的误差，Netdata 会对收集的指标进行插值。它使用每秒数据源的微秒时序来执行此操作，提供错误率为 0.0001% 的测量。当 Netdata 运行时，其会收集每个数据点，并确保数据库正常工作并具有可接受的精确度（参考文档：[在调试模式下，Netdata 会计算这个误差率](https://github.com/netdata/netdata/blob/36199f449852f8077ea915a3a14a33fa2aff6d85/database/rrdset.c#L1070-L1099)）。 44 | 45 | 最后，Netdata 的运行速度非常地快。优化是本产品的核心任务。在现代的硬件上，Netdata 每秒可以收集每个核心超过1万个指标（包括所有内容，比如：解析数据源，插入数据，数据库的读/写等）。但是，对于每个节点每秒几万个的数据，Netdata 却仅仅需要可以忽略不计的CPU资源（仅占用每个核心的 1% ~ 2％）。 46 | 47 | Netdata的设计旨在： 48 | - 解决集中化数据监控的问题。 49 | - 替代控制台进行性能故障排除。 50 | 51 | 因此，对于 Netdata 来说，做到以秒级单位的数据监控是非常容易的，这是也很自然的结果。 52 | 53 | [![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%2Fwhy-netdata%2F1s-granularity&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 54 | -------------------------------------------------------------------------------- /kr/docs/Donations-netdata-has-received.md: -------------------------------------------------------------------------------- 1 | # 기부 2 | 3 | Netdata를 위해 기부 받은 기부 목록입니다. (목록은 알파벳 순으로 정렬되었음): 4 | 5 | | 기부 내용|관련 링크| 기부자|해당 기부에 대한 설명| 6 | |-----------:|:-----------:|:---------:|:--------------------------| 7 | | Packages Distribution|-|**[PackageCloud.io](https://packagecloud.io/)**|**PackageCloud.io** donated to a free open-source subscription to their awesome Package Distribution services.| 8 | | Cross Browser Testing|-|**[BrowserStack.com](https://www.browserstack.com/)**|**BrowserStack.com** donated a free subscription to their awesome Browser Testing services (all three of them: Live, Screenshots, Responsive).| 9 | | Cloud VM|[cdn77.my-netdata.io](http://cdn77.my-netdata.io)|**[CDN77.com](https://www.cdn77.com/)**|**CDN77.com** donated a VM with 2 CPU cores, 4GB RAM and 20GB HD, on their excellent CDN network.| 10 | | Localization Management|[Netdata localization project](https://crowdin.com/project/netdata) (check issue [#279](https://github.com/netdata/netdata/issues/279))|**[Crowdin.com](https://crowdin.com/)**|**Crowdin.com** donated an open source license to their Localization Management Platform.| 11 | | Cloud VMs|[london.my-netdata.io](https://london.my-netdata.io) (Several VMs)|**[DigitalOcean.com](https://www.digitalocean.com/)**|**DigitalOcean.com** donated 1000 USD to be used in their excellent Cloud Computing services. Many thanks to [Justin Paine](https://github.com/xxdesmus) for making this happen.| 12 | | Development IDE|-|**[JetBrains.com](https://www.jetbrains.com/)**|**JetBrains.com** donated an open source license for 4 developers for 1 year, to their excellent IDEs.| 13 | | Cloud VM|[octopuscs.my-netdata.io](https://octopuscs.my-netdata.io)|**[OctopusCS.com](https://octopuscs.com/)**|**OctopusCS.com** donated a VM with 4 CPU cores, 16GB RAM and 50GB HD in their excellent Cloud Computing services.| 14 | | Cloud VM|[ventureer.my-netdata.io](https://ventureer.my-netdata.io)|**[Ventureer.com](https://ventureer.com/)**|**Ventureer.com** donated a VM with 4 CPU cores, 8GB RAM and 50GB HD in their excellent Cloud Computing services.| 15 | | Cloud VM|[stackscale.my-netdata.io](https://stackscale.my-netdata.io)|**[stackscale.com](https://www.stackscale.com/)**|**StackScale.com** donated a VM with 4 CPU cores, 16GB RAM and 100GB HD in their excellent Cloud Computing services.| 16 | 17 | 감사합니다! 18 | 19 | --- 20 | 21 | **기부를 원하시나요?** 우리는 Netdata를 개선하는데 도움이 될 온라인 서비스가 필요합니다. 22 | 또한 Netdata의 모든 잠재력을 보여줄 수 있도록 데모 사이트 네트워크(VM)를 구축하려 합니다. 23 | 24 | 다음 이메일로 연락바랍니다. costa@tsaousis.gr. 25 | 26 | [![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%2FDonations-netdata-has-received&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 27 | -------------------------------------------------------------------------------- /zh/packaging/maintainers/README.md: -------------------------------------------------------------------------------- 1 | # 软件包维护者 2 | 3 | 此页面记录了各个操作系统和版本的Netdata软件包维护者。 4 | 5 | > 这个文档是随时更新的，以便反映最新的（最真实的）状态。 6 | 7 | 8 | --- 9 | 10 | ## 官方Linux发行版 11 | 12 | | Linux发行版 | Netdata版本 | 维护者 | 相关链接 | 13 | | :-: | :-: | :-: | :-- | 14 | | Arch Linux | Release | @svenstaro | [netdata @ Arch Linux](https://www.archlinux.org/packages/community/x86_64/netdata/) | 15 | | Arch Linux AUR | Git | @sanskritfritz | [netdata @ AUR](https://aur.archlinux.org/packages/netdata-git/) | 16 | | Gentoo Linux | Release + Git | @candrews | [netdata @ gentoo](https://github.com/gentoo/gentoo/tree/master/net-analyzer/netdata) | 17 | | Debian | Release | @lhw @FedericoCeratto | [netdata @ debian](http://salsa.debian.org/debian/netdata) | 18 | | Slackware | Release | @willysr | [netdata @ slackbuilds](https://slackbuilds.org/repository/14.2/system/netdata/) 19 | | Ubuntu | | | | 20 | | Red Hat / Fedora / Centos | | | | 21 | | SuSe / openSuSe | | | | 22 | 23 | --- 24 | ## FreeBSD 25 | 26 | | 系统 | 最初的公关 | 核心开发者 | 软件包维护者 27 | |:-:|:-:|:-:|:-:| 28 | FreeBSD|#1321|@vlvkobal|@mmokhi 29 | 30 | --- 31 | ## MacOS 32 | 33 | | 系统 | 相关链接 | 核心开发者 | 软件包维护者 34 | |:-:|:-:|:-:|:-:| 35 | MacOS Homebrew Formula|[link](https://github.com/Homebrew/homebrew-core/blob/master/Formula/netdata.rb)|@vlvkobal|@rickard-von-essen 36 | 37 | --- 38 | ## 非官方Linux软件包 39 | 40 | | Linux发行版 | Netdata版本 | 维护者 | 相关链接 | 41 | | :-: | :-: | :-: | :-- | 42 | | Ubuntu | Release | @gslin | [netdata @ gslin ppa](https://launchpad.net/~gslin/+archive/ubuntu/netdata) https://github.com/netdata/netdata/issues/69#issuecomment-217458543 | 43 | 44 | --- 45 | ## 嵌入式Linux 46 | 47 | | 嵌入式Linux | Netdata版本 | 维护者 | 相关链接 | 48 | | :-: | :-: | :-: | :-- | 49 | | ASUSTOR NAS | ? | William Lin | https://www.asustor.com/apps/app_detail?id=532 | 50 | | OpenWRT | Release | @nitroshift | [openwrt package](https://github.com/openwrt/packages/tree/master/admin/netdata) | 51 | | ReadyNAS | Release | @NAStools | https://github.com/nastools/netdata | 52 | | QNAP | Release | QNAP_Stephane | https://forum.qnap.com/viewtopic.php?t=121518 | 53 | | DietPi | Release | @Fourdee | https://github.com/Fourdee/DietPi | 54 | 55 | --- 56 | ## Linux容器 57 | 58 | | 容器 | Netdata版本 | 维护者 | 相关链接 | 59 | | :-: | :-: | :-: | :-- | 60 | | Docker | Git | @titpetric | https://github.com/titpetric/netdata | 61 | 62 | --- 63 | ## 自动化系统 64 | 65 | | 自动化系统 | Netdata版本 | 维护者 | 相关链接 | 66 | | :-: | :-: | :-: | :-- | 67 | | Ansible | git | @jffz | https://galaxy.ansible.com/jffz/netdata/ | 68 | | Chef | ? | @sergiopena | https://github.com/sergiopena/netdata-cookbook | 69 | 70 | --- 71 | ## 来自repology.org的软件包摘要 72 | 73 | [![Packaging status](https://repology.org/badge/vertical-allrepos/netdata.svg)](https://repology.org/metapackage/netdata/versions) 74 | 75 | [![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%2Fpackaging%2Fmaintainers%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 76 | -------------------------------------------------------------------------------- /pt/docs/Donations-netdata-has-received.md: -------------------------------------------------------------------------------- 1 | # Doações 2 | # Donations 3 | 4 | Essa é uma lista das doações que recebemos para o Netdata (classificados em ordem alfabética pelo nome): 5 | 6 | | O que doou|links relacionados|quem doou|descrição da doação| 7 | |-----------:|:-----------:|:---------:|:--------------------------| 8 | | Distribuição de Pacotes|-|**[PackageCloud.io](https://packagecloud.io/)**|**PackageCloud.io** doou uma assinatura de código-aberto para seus incríveis serviços de Distribuição de Pacotes.| 9 | | Teste entre Navegadores|-|**[BrowserStack.com](https://www.browserstack.com/)**|**BrowserStack.com** doou uma assinatura de código-aberto para seus incríveis serviços de Teste de Navegador (todos os três: Ao vivo, Capturas de tela, Responsivo).| 10 | | VM na Nuvem|[cdn77.my-netdata.io](http://cdn77.my-netdata.io)|**[CDN77.com](https://www.cdn77.com/)**|**CDN77.com** doou uma VM com 2 núcleos de CPU, 4GB RAM e 20GB HD, em sua excelente rede de CDN.| 11 | | Gerenciamento de Localização|[Projeto de localização do Netdata](https://crowdin.com/project/netdata) (veja a issue [#279](https://github.com/netdata/netdata/issues/279))|**[Crowdin.com](https://crowdin.com/)**|**Crowdin.com** doou uma assinatura de código aberto para sua Plataforma de Gerenciamento de Localização.| 12 | | VMs na Nuvem|[london.my-netdata.io](https://london.my-netdata.io) (Diversos VMs)|**[DigitalOcean.com](https://www.digitalocean.com/)**|**DigitalOcean.com** doou 1000 dólares para ser usado em seus incríveis serviços de Computação em Nuvem. Muito obrigado a [Justin Paine](https://github.com/xxdesmus) por fazer isso acontecer.| 13 | | IDE de Desenvolvimento|-|**[JetBrains.com](https://www.jetbrains.com/)**|**JetBrains.com** doou uma licença de código aberto para 4 desenvolvedores por 1 ano, para suas incríveis IDEs.| 14 | | VM na Nuvem|[octopuscs.my-netdata.io](https://octopuscs.my-netdata.io)|**[OctopusCS.com](https://octopuscs.com/)**|**OctopusCS.com** doou uma VM com 4 núcleos de CPU, 16GB RAM e 50GB HD nos seus incríveis serviços de Computação em Nuvem.| 15 | | VM na Nuvem|[ventureer.my-netdata.io](https://ventureer.my-netdata.io)|**[Ventureer.com](https://ventureer.com/)**|**Ventureer.com** doou uma VM com 4 núcleos de CPU, 8GB RAM e 50GB HD nos seus incríveis serviços de Computação em Nuvem.| 16 | | VM na Nuvem|[stackscale.my-netdata.io](https://stackscale.my-netdata.io)|**[stackscale.com](https://www.stackscale.com/)**|**StackScale.com** doou uma VM com 4 núcleos de CPU, 16GB RAM e 100GB HD nos seus incríveis serviços de Computação em Nuvem.| 17 | 18 | Muito obrigado! 19 | 20 | --- 21 | 22 | **Você quer fazer uma doação?** Temos sede de serviços on-line que podem nos ajudar a melhorar o Netdata. Também tentamos criar uma rede de sites de demonstração (VMs) que podem nos ajudar a mostrar todo o potencial do Netdata. 23 | 24 | Por favor, entre em contato com costa@tsaousis.gr. 25 | 26 | [![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%2FDonations-netdata-has-received&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 27 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Localization 2 | 3 | This project contains translation files for the Netdata HTML documentation. 4 | All contributions will be made via GitHub Pull Requests. 5 | 6 | ## Add translations for a new language 7 | 8 | Under the root directory, you will need to add a subdirectory with the language abbreviation as shown at https://squidfunk.github.io/mkdocs-material/getting-started/#localization. If your language does not appear in the `mkdocs-material` translations table, you will see a link that lets you provide a new translation in 5 minutes. Once your language is included in a release of `mkdocs-material`, let us know, so we can ensure our build mechanism uses the version that contains your language. 9 | 10 | Underneath your directory you will add markdown files, using the precise structure of the `netdata/netdata`project directory tree. You can translate as many files as you like. The files you provide will be is used to override the existing English markdown file in the localized version. Of course the names of the files need to match precisely. 11 | 12 | For example, to provide a Chinese translation on how to update Netdata, the file should be `zh/packaging/installer/UPDATE.md`. 13 | 14 | When you do a pull request with your PR, you will see that a Netlify check is automatically executed for your language as well. If you click on deploy preview, the HTML documentation at https://docs.netdata.cloud will also be available under `https://docs.netdata.cloud/[abbreviation]`, with only the files you provided translated. For the previous example, the translated page would be available at `https://docs.netdata.cloud/zh/packaging/installer/UPDATE.md`. 15 | 16 | The generated documentation has a language switcher tool, which we will extend with your language, once your PR is successfully merged. 17 | You may submit a PR yourself, by adding [an option for your language](https://github.com/netdata/netdata/blob/master/docs/generator/custom/themes/material/partials/header.html#L95). 18 | You can see an example in [PR 7004 of project netdata/netdata](https://github.com/netdata/netdata/pull/7004). 19 | 20 | ## Translate more documents 21 | 22 | If you already see your language in https://docs.netdata.cloud, you will notice that many files are still shown in English. Pressing the 'edit' file will lead you to an invalid location, because no one had added a translation for that file. To provide one yourself: 23 | - Find the relevant .md document in the `netdata/netdata` repo. 24 | - Copy it to the exact same location under `netdata/localization/[abbreviation]`. 25 | - Translate it and create a PR. 26 | 27 | ## Caution regarding header translations 28 | 29 | Headers in markdown documents have a dual use as a section description and a link to a specific part of the document. 30 | When you translate a header, you will need to find where else in the documentation that header is referenced and change 31 | that reference as well. 32 | An alternative workaround to modifying all links to a section is to keep the original, English headers as well. 33 | This will result in duplicate headings, one in English and one in your language, so it's not a proper solution. 34 | 35 | As soon as [the issue with the build process](https://github.com/netdata/localization/issues/17) is resolved, the check 36 | for broken links will be done for you by the build process (`checklinks.sh`). 37 | So you'll be able to easily find the additional files that need to be modified, in order to get a successful build. 38 | -------------------------------------------------------------------------------- /kr/docs/why-netdata/1s-granularity.md: -------------------------------------------------------------------------------- 1 | # 초 단위의 높은 데이터 세분성 2 | 3 | 효과적인 모니터링과 문제 해결 시스템, 응용 프로그램을 위해서는 고 해상도의 측정치가 필요합니다. 4 | 5 | ## Why? 6 | 7 | - 세상는 갈수록 실시간에 가까워지고 있습니다. 최신의 고객 경험은 응답시간에 영향을 크게 받으므로 SLA는 전과 다르게 더 엄격해졌습니다. 이제 10초 단위의 측정치와 2초 단위의 SLA 모니터링은 충분하지 않습니다. 8 | 9 | - IT는 가상화를 향해 가고있습니다. 실제 하드웨어와 다르게 가상 환경은 선형적이지 않고, 예측 가능하지 않습니다. 응용 프로그램이 필요한 만큼의 자원을 사용할 수 있도록 예측하는 것은 힘듭니다. 물론 자원은 요구량 만큼 주어지겠지만 그것들이 필요한 순간 곧바로 주어지지는 않을겁니다. 가상 환경의 지연 시간은 '호스팅 공급 업체의 유지 정책, 자원 할당, 쓰로틀링 정책과 관련 있는 동일한 물리적 서버에서 동작하는 타사의 가상 머신에서 비롯된 작업 부하, 호스팅 공급 업체의 프로비저닝 시스템 등'과 같은 우리가 제어할 수 없는 범위에서 발생하는 여러 요인들로부터 영향을 받습니다. 10 | 11 | ## Netdata가 아닌 다른 곳은 어떻습니까? 12 | 13 | 왜 다른 SaaS 공급 업체나 모니터링 플랫폼은 고해상도의 측정치를 제공하지 않을까요? 14 | 15 | 그렇게 하고싶지만 하지 못하고 있습니다. 최소한 대규모로는 말입니다. 16 | 17 | 그 이유는 디자인 결정에 있습니다.: 18 | 19 | 1. 시계열 데이터베이스 (prometheus, graphite, opentsdb, influxdb 등)은 모든 측정치를 중앙 집중화합니다. 규모에 따라서 이러한 데이터베이스는 전체 인프라에서 병목 현상이 쉽게 발생할 수 있습니다. 20 | 21 | 2. SaaS 공급 업체는 모든 측정치를 중앙 집중화하는 비즈니스 모델을 기반으로 합니다. 시분할 데이터베이스의 병목현상 외에도 대역폭 비용이 증가하는 문제 또한 존재합니다. 따라서 고 해상도의 측정치를 대규모로 지원하면 비즈니스 모델이 파괴됩니다. 22 | 23 | 물론 수십 년이 흐르는 동안 규모에서 발생되는 이런 문제들은 해결되었습니다. 성능을 증가(Scale up)시키는 대신 확장(Scale out)하는 방식으로 말입니다. 즉 매우 큰 중앙 장치에 투자하는 것이 아니라, 애플리케이션을 분산시켜 작은 노드를 더 추가하여 확장할 수 있도록 합니다. 24 | 25 | 이러한 모니터링의 문제를 해결하기 위한 수많은 시도들이 있었습니다. 하지만 모든 해결책은 측정치를 중앙 집중화해야 했으며 이러한 점은 고성능을 필요로 했습니다. 이러한 이유로 이 문제는 어떻게든 관리되는 것 같지만, 여전히 모든 모니터링 플랫폼의 주요 문제이며 모니터링 비용을 증가시키는 주요 요인 중 하나가 되었습니다. 26 | 27 | 다른 중요한 요소는 초 단위로 실행시 어떻게 효율적으로 자원 효율적인 데이터 수집이 가능한 지에 대한 것입니다. 대부분의 해결책은 제대로 작동하지 않습니다. 데이터 수집 에이전트는 초 단위로 모니터링할 경우 상당한 시스템 자원을 소비하여 모니터링 시스템과 응용 프로그램에 상당한 영향을 미칩니다. 28 | 29 | 결론적으로, 초 단위로 데이터를 수집하는 것은 무척 어렵습니다. 바쁘게 동작 중인 가상 환경은 [100ms 일정한 지연 시간을 가지며, 모든 데이터 소스에 무작위로 분산됩니다.](https://docs.google.com/presentation/d/18C8bCTbtgKDWqPa57GXIjB2PbjjpjsUNkLtZEz6YK8s/edit#slide=id.g422e696d87_0_57). 데이터 수집이 제대로 구현되지 않으면 이 지연 시간에 10% 안팎의 무작위 오류가 발생하며, 이는 모니터링 시스템에게 상당히 중요합니다. 30 | 31 | 정리하자면 모니터링 사업은 주로 3가지의 이유로 대규모의 고 해상도 측정치를 제공하지 않습니다. 32 | 33 | 1. 측정치를 중앙 집중화하면 모니터링 비용은 비효율적이게 됩니다. 34 | 2. 데이터 수집은 최적화가 필요합니다. 그렇지 않으면 모니터링 시스템이 중대한 영향을 미치게 됩니다. 35 | 3. 바쁘게 동작 중인 가상 환경에서 특히 더 데이터 수집이 어렵습니다. 36 | 37 | ## 어떤 점에서 Netdata가 다른가요? 38 | 39 | Netdata는 모니터링을 완전히 분산화 시켰습니다. 각각의 Netdata 노드들은 자율적입니다. 로컬에서 측정치를 수집하며 로컬에 저장하고, 경보 발생을 위해 로컬에서 검사하며 대쉬 보드의 시각화를 위해 API를 제공합니다. 이는 Netdata를 무한대로 확장할 수 있게 합니다. 40 | 41 | 물론 Netdata도 필요에 따라 측정치를 중앙 집중화 할 수 있습니다. 예를 들어 임시 노드에 측정치를 저장하는 것은 실용적이지 않습니다. 이러한 경우 Netdata는 실시간으로 임시 노드에서 근처에 있는 한개 이상의 비임시 노드로 측정치를 스트리밍합니다. 이러한 중앙 집중화되고 나서는 다시 분산화가 이루어집니다. 대규모의 인프라에선 많은 중앙 집중화 노드가 있을 수 있습니다. 42 | 43 | 바쁘게 동작하는 가상환경에서 데이터 수집 지연 시간으로 발생한 오류를 해결하기 위해서, Netdata는 수집된 측정치를 보간합니다. 데이터 소스 당 마이크로 타이밍을 사용해 0.0001%의 오차율로 측정을 수행합니다. [디버그 모드로 동작 시, Netdata는 오차율 계산](https://github.com/netdata/netdata/blob/36199f449852f8077ea915a3a14a33fa2aff6d85/database/rrdset.c#L1070-L1099)을 수집된 모든 포인트에 대해 수행하여, 데이터베이스가 적절한 정확도에서 동작하도록 합니다. 44 | 45 | 마지막으로, Netdata는 정말 빠릅니다. 최적화는 핵심적인 기능입니다. 최신 하드웨어에서 Netdata는 각 코어에서 초당 100만 개의 측정치를 수집할 수 있습니다. (여기엔 파싱 데이터 소스나 보간 데이터, 시계열 데이터베이스에 저장된 데이터가 포함됩니다.) 따라서 노드 별 초 당 수 천개의 측정치를 위해서는 Netdata는 무시할만한 CPU 자원을 소비합니다. (싱글 코어에서 1~2% 정도) 46 | 47 | Netdata는 다음과 같이 설계되었습니다. 48 | 49 | - 모니터링의 중앙 집중화 문제를 해결 50 | - 성능 문제 해결을 위한 콘솔을 대체 51 | 52 | 따라서 Netdata에게 1초 단위의 데이터 세분성을 갖는 것은 쉽고 자연스러운 결과입니다... 53 | 54 | [![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%2Fwhy-netdata%2F1s-granularity&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 55 | -------------------------------------------------------------------------------- /kr/docs/Demo-Sites.md: -------------------------------------------------------------------------------- 1 | # 데모 사이트 2 | 3 | 다음 링크에서 Netdata의 라이브 데모 사이트를 확인하세요. **[https://www.netdata.cloud](https://www.netdata.cloud/#live-demo)**: 4 | 5 | | 위치|Netdata 데모 URL|60 분 간 reqs|다음 사이트에서 VM 기증 받음| 6 | |:------:|:--------------:|:----------:|:------------| 7 | | 런던 (영국)|**[london.my-netdata.io](https://london.my-netdata.io)**
(이 곳은 global Netdata **registry** 이며 and has **named** and **mysql** charts)|[![Requests Per Second](https://london.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://london.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 8 | | 애틀랜타 (미국)|**[cdn77.my-netdata.io](https://cdn77.my-netdata.io)**
(with **named** and **mysql** charts)|[![Requests Per Second](https://cdn77.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://cdn77.my-netdata.io)|[CDN77.com](https://www.cdn77.com/)| 9 | | 이스라엘|**[octopuscs.my-netdata.io](https://octopuscs.my-netdata.io)**|[![Requests Per Second](https://octopuscs.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://octopuscs.my-netdata.io)|[OctopusCS.com](https://www.octopuscs.com)| 10 | | 마드리드 (스페인)|**[stackscale.my-netdata.io](https://stackscale.my-netdata.io)**|[![Requests Per Second](https://stackscale.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://stackscale.my-netdata.io)|[StackScale Spain](https://www.stackscale.es/)| 11 | | 뱅갈루루 (인도)|**[bangalore.my-netdata.io](https://bangalore.my-netdata.io)**|[![Requests Per Second](https://bangalore.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://bangalore.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 12 | | 프랑크푸르트 (독일))|**[frankfurt.my-netdata.io](https://frankfurt.my-netdata.io)**|[![Requests Per Second](https://frankfurt.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://frankfurt.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 13 | | 뉴욕 (미국)|**[newyork.my-netdata.io](https://newyork.my-netdata.io)**|[![Requests Per Second](https://newyork.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://newyork.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 14 | | 샌프란시스코 (미국)|**[sanfrancisco.my-netdata.io](https://sanfrancisco.my-netdata.io)**|[![Requests Per Second](https://sanfrancisco.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://sanfrancisco.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 15 | | 싱가폴|**[singapore.my-netdata.io](https://singapore.my-netdata.io)**|[![Requests Per Second](https://singapore.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://singapore.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 16 | | 토론토 (캐나다)|**[toronto.my-netdata.io](https://toronto.my-netdata.io)**|[![Requests Per Second](https://toronto.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://toronto.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 17 | 18 | _Netdata 대쉬보드는 모바일과 터치 환경에 친화적입니다._ 19 | 20 | [![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%2FDemo-Sites&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 21 | -------------------------------------------------------------------------------- /zh/docs/tutorials/longer-metrics-storage.md: -------------------------------------------------------------------------------- 1 | # 更改Netdata存储指标的时间 2 | 3 | 4 | Netdata可帮助你每秒收集数千个系统和应用程序指标，但长期存储又如何呢？ 5 | 6 | 许多人认为Netdata只能存储大约一个小时的实时指标，但这只是当今的默认配置。通过正确的设置，Netdata能够有效地存储价值数小时或数天的每秒历史数据，而不必依赖[后端](https://github.com/trisasnava/netdata/blob/master/backends)。 7 | 8 | 本教程提供了两个选项，用于配置Netdata以存储更多指标。 **我们建议使用[默认的数据库引擎](https://github.com/trisasnava/netdata/blob/master/docs/tutorials/longer-metrics-storage.md#using-the-database-engine)**，但是如果你愿意，可以坚持使用或切换到循环数据库。 9 | 10 | 让我们开始吧。 11 | 12 | ## 使用数据库引擎 13 | 14 | 数据库引擎使用RAM来存储最新指标，同时还使用“溢出到磁盘”功能，该功能利用可用磁盘空间来长期存储指标。数据库引擎的此功能使你可以存储比系统可用RAM大得多的数据集。 15 | 16 | 当前，数据库引擎是存储指标的默认方法，但是如果不确定使用的是哪个数据库，请检查 `netdata.conf` 文件并查找 ` memory mode ` 设置： 17 | 18 | ``` 19 | [global] 20 | memory mode = dbengine 21 | ``` 22 | 23 | 如果将 `memory mode` 设置为 `dbengine` 以外的任何模式，请对其进行更改，然后使用标准命令重新启动Netdata以重新启动系统上的服务。你现在正在使用数据库引擎！ 24 | 25 | > 在我们的博客上了解有关我们如何实现数据库引擎及其未来愿景的更多信息：[如何以及为何将长期存储带入Netdata](https://blog.netdata.cloud/posts/db-engine/)。 26 | 27 | 是什么使数据库引擎高效？尽管其结构类似于传统数据库，但数据库引擎在RAM和磁盘之间拆分数据。数据库引擎在RAM上缓存和索引数据以保持较低的内存使用率，然后将较旧的指标压缩到磁盘上以进行长期存储。 28 | 29 | 当Netdata仪表板查询历史指标时，数据库引擎将使用存储在RAM中的缓存来返回相关指标以在图表中可视化。 30 | 31 | 现在，假设数据库引擎同时使用RAM和磁盘，则需要考虑其他两个设置：页面高速缓存大小和dbengine磁盘空间。 32 | 33 | ``` 34 | [global] 35 | page cache size = 32 36 | dbengine disk space = 256 37 | ``` 38 | 39 | ` page cache size ` 设置数据库引擎将用于缓存和索引的最大RAM量（以MiB为单位）。 `dbengine disk space` 设置数据库引擎将用于存储压缩指标的最大磁盘空间（同样在MiB中）。 40 | 41 | 根据我们的测试，当Netdata每秒收集大约4,000个指标时，这些默认设置将保留大约一天的指标。如果增加 ` page cache size ` 或 ` dbengine disk space `，Netdata将保留更多历史指标。 42 | 43 | 但是，在你过分地更改这些选项之前，请先阅读[数据库引擎的内存占用量](https://github.com/trisasnava/netdata/blob/master/database/engine/README.md#memory-requirements)。 44 | 45 | 在数据库引擎处于活动状态的情况下，你可以将 ` /var/cache/netdata/dbengine/ ` 文件夹备份到另一个位置以实现冗余。 46 | 47 | 现在你已经知道如何切换到数据库引擎，下面为那些尚未准备好采取行动的用户介绍默认的轮询数据库。 48 | 49 | ## 使用轮询数据库 50 | 51 | 52 | 在以前的版本中，Netdata使用循环数据库来存储1小时的每秒指标。 53 | 54 | 要查看你是否仍在使用该数据库，或者是否要切换到该数据库，请打开 ` netdata.conf ` 文件，然后查看是否将 ` memory mode ` 选项设置为 ` save `。 55 | 56 | ``` 57 | [global] 58 | memory mode = save 59 | ``` 60 | 61 | 如果将 ` memory mode ` 设置为 ` save `，那么你正在使用循环数据库。如果是这样，` history ` 选项将设置为3600，相当于3600秒或一小时。 62 | 63 | 要增加历史指标，可以将 ` history ` 增加到要存储的秒数： 64 | 65 | ``` 66 | [global] 67 | # 2 hours = 2 * 60 * 60 = 7200 seconds 68 | history = 7200 69 | # 4 hours = 4 * 60 * 60 = 14440 seconds 70 | history = 14440 71 | # 24 hours = 24 * 60 * 60 = 86400 seconds 72 | history = 86400 73 | ``` 74 | 75 | 等等。 76 | 77 | 接下来，检查Netdata在你的系统上收集了多少度量，以及使用了多少RAM。然后访问Netdata仪表板，查看界面的右下角。你会发现类似于以下内容的句子： 78 | 79 | > Netdata每秒收集1938个指标，将其显示在299个图表中，并通过81个警报进行监视。 Netdata在 **netdata-linux**上使用25 MB的内存以提供 1小时6分36秒的实时历史记录。 80 | 81 | 在此台式机系统上，使用Ryzen 5 1600和16GB RAM，循环数据库使用25 MB RAM来存储一个小时的数据，可用于近2,000个指标。 82 | 83 | 要增加 ` history ` 选项，你需要编辑 `netdata.conf` 文件并增加历史记录设置。在大多数安装中，可以在 `/etc/netdata/netdata.conf` 中找到它，但是某些操作系统将其放在 `/opt/netdata/etc/netdata/netdata.conf` 中。 84 | 85 | 使用 ` /etc/netdata/edit-config netdata.conf ` 或你喜欢的文本编辑器，将 `3600` 替换为你要存储的秒数。 86 | 87 | 你应该基于两件事来确定此数字：你的用例需要多少历史记录，以及你愿意为Netdata分配多少RAM。 88 | 89 | > 在生产系统上更改 ` history ` 选项时请多加注意。 Netdata配置为在系统开始用完RAM时停止其进程，但是永远不要太小心。 内存不足的情况非常糟糕。 90 | 91 | 较长的历史记录将使用多少RAM？ 让我们使用一些数学。 92 | 93 | Netdata收集的每个值循环数据库需要4个字节。 如果Netdata每秒收集一次指标，则每个指标每秒4个字节。 94 | 95 | ``` 96 | 4 bytes * X seconds * Y metrics = RAM使用量（以字节为单位） 97 | ``` 98 | 99 | 假设你的系统每秒收集1,000个指标。 100 | 101 | ``` 102 | 4 bytes * 3600 seconds * 1,000 metrics = 14400000 bytes = 14.4 MB RAM 103 | ``` 104 | 105 | 使用该公式，你可以计算更大历史记录设置的RAM使用率。 106 | 107 | ``` 108 | # 2小时,每秒1,000个指标 109 | 4 bytes * 7200 seconds * 1,000 metrics = 28800000 bytes = 28.8 MB RAM 110 | # 2小时,每秒2,000个指标 111 | 4 bytes * 7200 seconds * 2,000 metrics = 57600000 bytes = 57.6 MB RAM 112 | # 4小时，每秒2,000个指标 113 | 4 bytes * 14440 seconds * 2,000 metrics = 115520000 bytes = 115.52 MB RAM 114 | # 24小时，每秒1,000个指标 115 | 4 bytes * 86400 seconds * 1,000 metrics = 345600000 bytes = 345.6 MB RAM 116 | ``` 117 | 118 | ## 下一步是什么？ 119 | 120 | 121 | 现在，你已经配置了数据库引擎或循环数据库引擎来存储更多指标，你可能希望看到它的实际效果！ 122 | 123 | 有关如何平移图表以查看历史指标的更多信息，请参阅有关使用[图表](https://github.com/trisasnava/netdata/blob/master/web/README.md#using-charts)的文档。 124 | 125 | 而且，如果你现在想减少Netdata的资源使用，请查看我们的[性能指南](https://github.com/trisasnava/netdata/blob/master/docs/Performance.md)，以获取有关优化的最佳实践。 -------------------------------------------------------------------------------- /zh/docs/Demo-Sites.md: -------------------------------------------------------------------------------- 1 | # Netdata的示例网站 2 | 3 | Netdata 的在线Demo：**[https://my-netdata.io](https://my-netdata.io)** 4 | 5 | 位置 | Netdata演示URL | 1小时内的访问量 | VM捐赠者 6 | :-------:|:-----------------:|:----------:|:------------- 7 | 英国伦敦|**[london.my-netdata.io](https://london.my-netdata.io)**
（这是Netdata的**全局注册节点**，本演示中提供了**named**与**Mysql**的数据概览）|[![Requests Per Second](https://london.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://london.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745) 8 | 美国亚特兰大|**[cdn77.my-netdata.io](https://cdn77.my-netdata.io)**
（本演示中提供了**named**与**Mysql**的数据概览)|[![Requests Per Second](https://cdn77.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://cdn77.my-netdata.io)|[CDN77.com](https://www.cdn77.com/) 9 | 以色列|**[octopuscs.my-netdata.io](https://octopuscs.my-netdata.io)**|[![Requests Per Second](https://octopuscs.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://octopuscs.my-netdata.io)|[OctopusCS.com](https://www.octopuscs.com) 10 | 法国鲁贝|**[ventureer.my-netdata.io](https://ventureer.my-netdata.io)**|[![Requests Per Second](https://ventureer.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://ventureer.my-netdata.io)|[Ventureer.com](https://ventureer.com/) 11 | 西班牙马德里|**[stackscale.my-netdata.io](https://stackscale.my-netdata.io)**|[![Requests Per Second](https://stackscale.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://stackscale.my-netdata.io)|[StackScale Spain](https://www.stackscale.es/) 12 | 印度班加罗尔|**[bangalore.my-netdata.io](https://bangalore.my-netdata.io)**|[![Requests Per Second](https://bangalore.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://bangalore.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745) 13 | 法国法兰克福|**[frankfurt.my-netdata.io](https://frankfurt.my-netdata.io)**|[![Requests Per Second](https://frankfurt.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://frankfurt.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745) 14 | 美国纽约|**[newyork.my-netdata.io](https://newyork.my-netdata.io)**|[![Requests Per Second](https://newyork.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://newyork.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745) 15 | 美国旧金山|**[sanfrancisco.my-netdata.io](https://sanfrancisco.my-netdata.io)**|[![Requests Per Second](https://sanfrancisco.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://sanfrancisco.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745) 16 | 新加波|**[singapore.my-netdata.io](https://singapore.my-netdata.io)**|[![Requests Per Second](https://singapore.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://singapore.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745) 17 | 加拿大多伦多|**[toronto.my-netdata.io](https://toronto.my-netdata.io)**|[![Requests Per Second](https://toronto.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://toronto.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745) 18 | 19 | *Netdata的仪表板在手机上也可以很好的被显示出来* 20 | 21 | [![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%2FDemo-Sites&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 22 | -------------------------------------------------------------------------------- /pt/docs/Demo-Sites.md: -------------------------------------------------------------------------------- 1 | # Sites de demonstração 2 | # Demo sites 3 | 4 | As instalações de demonstrações ao vivo estão disponíveis em **[https://www.netdata.cloud](https://www.netdata.cloud/#live-demo)**: 5 | 6 | | Localização|URL da demonstração do Netdata|60 mins reqs|VM doada por| 7 | |:------:|:--------------:|:----------:|:------------| 8 | | Londres (UK)|**[london.my-netdata.io](https://london.my-netdata.io)**
(Esse é o gráfico global do Netdata **registry** e possui gráficos do **named** e **mysql**)|[![Requisições Por Segundo](https://london.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://london.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 9 | | Atlanta (USA)|**[cdn77.my-netdata.io](https://cdn77.my-netdata.io)**
(com gráficos **named** e **mysql**)|[![Requisições por segundo](https://cdn77.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://cdn77.my-netdata.io)|[CDN77.com](https://www.cdn77.com/)| 10 | | Israel|**[octopuscs.my-netdata.io](https://octopuscs.my-netdata.io)**|[![Requisições Por Segundo](https://octopuscs.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://octopuscs.my-netdata.io)|[OctopusCS.com](https://www.octopuscs.com)| 11 | | Madrid (Espanha)|**[stackscale.my-netdata.io](https://stackscale.my-netdata.io)**|[![Requisições Por Segundo](https://stackscale.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://stackscale.my-netdata.io)|[StackScale Spain](https://www.stackscale.es/)| 12 | | Bangalore (Índia)|**[bangalore.my-netdata.io](https://bangalore.my-netdata.io)**|[![Requisições Por Segundo](https://bangalore.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://bangalore.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 13 | | Frankfurt (Alemanha)|**[frankfurt.my-netdata.io](https://frankfurt.my-netdata.io)**|[![Requisições Por Segundo](https://frankfurt.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://frankfurt.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 14 | | Nova Iorque (USA)|**[newyork.my-netdata.io](https://newyork.my-netdata.io)**|[![Requisições Por Segundo](https://newyork.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://newyork.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 15 | | São Francisco (USA)|**[sanfrancisco.my-netdata.io](https://sanfrancisco.my-netdata.io)**|[![Requisições Por Segundo](https://sanfrancisco.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://sanfrancisco.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 16 | | Singapura|**[singapore.my-netdata.io](https://singapore.my-netdata.io)**|[![Requisições Por Segundo](https://singapore.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://singapore.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 17 | | Toronto (Canada)|**[toronto.my-netdata.io](https://toronto.my-netdata.io)**|[![Requisições Por Segundo](https://toronto.my-netdata.io/api/v1/badge.svg?chart=netdata.requests&dimensions=requests&after=-3600&options=unaligned&group=sum&label=reqs&units=empty&value_color=blue&precision=0&v42)](https://toronto.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745)| 18 | 19 | _Os painéis do Netdata são amigáveis aos dispositivos móveis e ao toque._ 20 | 21 | [![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%2FDemo-Sites&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 22 | -------------------------------------------------------------------------------- /zh/docs/Running-behind-nginx.md: -------------------------------------------------------------------------------- 1 | # 通过 Nginx 访问 Netdata 2 | 3 | 要通过 Nginx 访问 Netdata，请使用以下配置文件： 4 | 5 | ### 作为一个虚拟主机 6 | ### netdata via nginx 7 | 8 | ``` 9 | upstream backend { 10 | # the netdata server 11 | server 127.0.0.1:19999; 12 | keepalive 64; 13 | } 14 | 15 | server { 16 | # nginx listens to this 17 | listen 80; 18 | 19 | # the virtual host name of this 20 | server_name netdata.example.com; 21 | 22 | location / { 23 | proxy_set_header X-Forwarded-Host $host; 24 | proxy_set_header X-Forwarded-Server $host; 25 | proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 26 | proxy_pass http://backend; 27 | proxy_http_version 1.1; 28 | proxy_pass_request_headers on; 29 | proxy_set_header Connection "keep-alive"; 30 | proxy_store off; 31 | } 32 | } 33 | ``` 34 | 35 | ### 作为已有虚拟主机的一个子文件夹 36 | 37 | ``` 38 | upstream netdata { 39 | server 127.0.0.1:19999; 40 | keepalive 64; 41 | } 42 | 43 | server { 44 | listen 80; 45 | 46 | # the virtual host name of this subfolder should be exposed 47 | #server_name netdata.example.com; 48 | 49 | location = /netdata { 50 | return 301 /netdata/; 51 | } 52 | 53 | location ~ /netdata/(?.*) { 54 | proxy_redirect off; 55 | proxy_set_header Host $host; 56 | 57 | proxy_set_header X-Forwarded-Host $host; 58 | proxy_set_header X-Forwarded-Server $host; 59 | proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 60 | proxy_http_version 1.1; 61 | proxy_pass_request_headers on; 62 | proxy_set_header Connection "keep-alive"; 63 | proxy_store off; 64 | proxy_pass http://netdata/$ndpath$is_args$args; 65 | 66 | gzip on; 67 | gzip_proxied any; 68 | gzip_types *; 69 | } 70 | } 71 | ``` 72 | 73 | ### 通过一个 Nginx 访问多个 Netdata 服务器 74 | 75 | ``` 76 | upstream backend-server1 { 77 | server 10.1.1.103:19999; 78 | keepalive 64; 79 | } 80 | upstream backend-server2 { 81 | server 10.1.1.104:19999; 82 | keepalive 64; 83 | } 84 | 85 | server { 86 | listen 80; 87 | 88 | # the virtual host name of this subfolder should be exposed 89 | #server_name netdata.example.com; 90 | 91 | location ~ /netdata/(?.*)/(?.*) { 92 | proxy_set_header X-Forwarded-Host $host; 93 | proxy_set_header X-Forwarded-Server $host; 94 | proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 95 | proxy_http_version 1.1; 96 | proxy_pass_request_headers on; 97 | proxy_set_header Connection "keep-alive"; 98 | proxy_store off; 99 | proxy_pass http://backend-$behost/$ndpath$is_args$args; 100 | 101 | gzip on; 102 | gzip_proxied any; 103 | gzip_types *; 104 | } 105 | 106 | # make sure there is a trailing slash at the browser 107 | # or the URLs will be wrong 108 | location ~ /netdata/(?.*) { 109 | return 301 /netdata/$behost/; 110 | } 111 | } 112 | ``` 113 | 114 | 当然，你可以根据需要添加任意数量的后端服务器。使用上面的方法，你可以访问后端服务器上的 Netdata，下面是使用方法： 115 | 116 | - 通过链接 `http://nginx.server/netdata/server1/ `来访问 `backend-server1` 117 | - 通过链接 `http://nginx.server/netdata/server2/` 来访问 `backend-server2` 118 | 119 | 120 | ### 启用身份验证 121 | 122 | 创建身份验证文件以启用 Nginx 基本身份验证。不使用 SSL/TLS 时请不要使用身份验证！ 123 | 如果你没有这一个文件，你可以通过以下命令创建一个： 124 | 125 | ``` 126 | printf "yourusername:$(openssl passwd -apr1)" > /etc/nginx/passwords 127 | ``` 128 | 129 | 并在服务器配置文件中启用身份验证： 130 | 131 | ``` 132 | server { 133 | # ... 134 | auth_basic "Protected"; 135 | auth_basic_user_file passwords; 136 | # ... 137 | } 138 | ``` 139 | 140 | ## 限制直接访问 Netdata 141 | 142 | 如果你的 Nginx 在 `localhost` 上，你可以使用它来保护你的 Netdata： 143 | 144 | ``` 145 | [web] 146 | bind to = 127.0.0.1 ::1 147 | ``` 148 | 149 | --- 150 | 151 | 你还可以使用 unix 域套接字。 这也将提供 Nginx 和 Netdata 之间更快的路由： 152 | 153 | ``` 154 | [web] 155 | bind to = unix:/tmp/netdata.sock 156 | ``` 157 | _注意： Netdata v1.8+才支持 unix 域套接字_ 158 | 159 | 在 Nginx 端，使用类似的东西来使用相同的 unix 域套接字： 160 | 161 | ``` 162 | upstream backend { 163 | server unix:/tmp/netdata.sock; 164 | keepalive 64; 165 | } 166 | ``` 167 | 168 | --- 169 | 170 | 如果你的 Nginx 不在 `localhost` 上，你可以这样设置： 171 | 172 | ``` 173 | [web] 174 | bind to = * 175 | allow connections from = IP_OF_NGINX_SERVER 176 | ``` 177 | 178 | _注意：Netdata v1.9+ 才支持 `allow connections from` 的连接_ 179 | 180 | `allow connections from` 通过接受 [netdata simple patterns](../libnetdata/simple_pattern/) 来匹配连接的IP地址。 181 | 182 | ## 防止重复的 access.log 183 | 184 | Nginx 记录访问信息，Netdata 也会记录它们。你可以通过设置来防止 Netdata 产生访问日志 `/etc/netdata/netdata.conf`: 185 | 186 | ``` 187 | [global] 188 | access log = none 189 | ``` 190 | 191 | ## SELinux 192 | 193 | 如果你收到 502 网关错误提示，你应该检查你的 Nginx 错误日志： 194 | 195 | ```sh 196 | # cat /var/log/nginx/error.log: 197 | 2016/09/09 12:34:05 [crit] 5731#5731: *1 connect() to 127.0.0.1:19999 failed (13: Permission denied) while connecting to upstream, client: 1.2.3.4, server: netdata.example.com, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:19999/", host: "netdata.example.com" 198 | ``` 199 | 200 | 如果你看到类似上面的内容，则 SELinux 阻止了 Nginx 连接到后端服务器。 201 | 要解决这个问题，只需要执行命令：`setsebool -P httpd_can_network_connect true` 即可。 202 | 203 | [![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%2FRunning-behind-nginx&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 204 | -------------------------------------------------------------------------------- /zh/docs/getting-started.md: -------------------------------------------------------------------------------- 1 | # 入门指南 2 | 3 | 感谢你使用 Netdata ！在本指南中，我们将快速引导你完成获取后应采取的第一步已安装Netdata。 4 | 5 | Netdata无需任何配置即可实时收集数千个指标，但是有一些有价值的东西要知道根据你的需求充分利用Netdata。 6 | 7 | >如果尚未安装Netdata，请访问[安装说明](../packaging/installer)了解详细信息， 8 | >包括我们的单行脚本，该脚本会在几乎所有 Linux 发行版上自动安装 Netdata。 9 | 10 | ## 访问 Netdata 仪表板 11 | **** 12 | 打开你选择的Web浏览器，然后导航到http://YOUR-HOST:19999。欢迎使用 Netdata ！ 13 | 14 | ![导航到仪表板的GIF动画](https://user-images.githubusercontent.com/1153921/63463901-fcb9c800-c412-11e9-8f67-8fe182e8b0d2.gif) 15 | 16 | **下一步是什么？**: 17 | 18 | - 阅读有关[标准Netdata仪表板](../web/gui/)的更多信息。 19 | 20 | - 了解[使用图表](../web/README.md#using-charts)的所有细节或[图表，上下文和族谱](../web/README.md#charts-contexts-families) 21 | 22 | ##基本配置 23 | 24 | Netdata主要使用`netdata.conf`文件进行自定义配置。 25 | 26 | 在大多数系统上，你可以在`/etc/netdata/netdata.conf`中找到该文件。 27 | 28 | >有些操作系统会将你的`netdata.conf`放置在`/opt/netdata/etc/netdata/netdata.conf`中，因此请检查是否存在 29 | >你在`/etc/netdata/netdata.conf`中找不到任何内容。 30 | 31 | `netdata.conf`文件分为多个部分，例如`[global]`，`[web]`，`[registry]`等。 通过 32 | 默认情况下，大多数选项都带有注释，因此你必须取消注释（删除`＃`），Netdata 才能识别你的 33 | 更改。 34 | 35 | 保存更改后，请[重新启动 Netdata](#start-stop-and-restart-netdata)加载新配置。 36 | 37 | **下一步是什么？**： 38 | 39 | - 通过增加`历史记录`来[更改Netdata存储指标的时间](#change-how-long-netdata-stores-metrics)选项或切换到数据库引擎。 40 | - 将 Netdata 的仪表板移至[不同端口](https://docs.netdata.cloud/web/server/)或启用TLS / HTTPS加密。 41 | - 请参阅我们的[daemon配置文档](../daemon/config/)中的所有`netdata.conf`选项。 42 | - 运行自己的[注册表](../registry/README.md#run-your-own-registry)。 43 | 44 | ##从更多来源收集数据 45 | 46 | 当Netdata启动时，它将自动检测数十个`数据源`，例如数据库服务器，Web服务器等。 要从刚刚安装的服务或应用程序中自动检测并收集指标，你需要[重新启动Netdata](#start-stop-and-restart-netdata)。 47 | 48 | >有一个例外：Netdata在主机上运行时（例如不在容器本身中运行），它将始终自动检测容器和虚拟机。 49 | 50 | 但是，仅当你使用源的标准安装过程安装了源时，自动检测才有效。 如果是Netdata 51 | 重新启动后未收集指标，则你的来源可能配置不正确。 看一下[外部插件 52 | 文档](../collectors/plugins.d/)找到适合你的源代码的模块。 这些页面将包含更多 53 | 有关如何配置源以进行自动检测的信息。 54 | 55 | 某些模块（例如chrony）在默认情况下处于禁用状态，必须手动启用才能自动检测工作。 56 | 57 | Netdata一旦检测到有效的数据源，它将继续尝试从中收集数据。 例如，如果Netdata正在从Nginx Web服务器收集数据，并且你关闭了Nginx，则Netdata将在你启动Web服务器备份时立即收集新数据-无需重新启动。 58 | 59 | ###配置插件 60 | 61 | 即使Netdata自动检测你的服务/应用程序，你也可能需要配置Netdata的内容或频率 62 | 收集数据。 63 | 64 | Netdata使用**内部**和**外部**插件来收集数据。内部插件在Netdata守护进程中运行，而外部插件是独立的进程，可通过管道将指标发送到Netdata。还有一些插件**编排器**，它们是具有一个或多个数据收集**模块**的外部插件。 65 | 66 | 你可以同时配置内部和外部插件以及各个模块。 有很多方法可以做到这一点： 67 | 68 | - 在`netdata.conf`中的`[plugins]`部分,使用`yes`或`no`启用或禁用内部或外部插件。 69 | - 在`netdata.conf`中的[plugin:XXX]部分中，每个插件都有一个部分，用于更改收集频率或将选项传递给该插件。 70 | - 在每个外部插件的`.conf`文件中,例如:在`/etc/netdata/python.d.conf`中。 71 | - 在每个模块的`conf`文件中,例如：在`/etc/netdata/python.d/nginx.conf`中。 72 | 73 | 它很复杂，因此让我们来看一个示例。各个.conf文件负责使用nginx模块和python.d插件Orchestrator从Nginx Web服务器收集数据。 74 | 75 | 首先，你可以完全在`netdata.conf`中启用或禁用`python.d`插件。 76 | 77 | ```conf 78 | [plugins] 79 | # Enabled 80 | python.d = yes 81 | # Disabled 82 | python.d = no 83 | ``` 84 | 85 | 你还可以通过netdata.conf中的`[plugin:python.d]`部分来配置整个`python.d`外部插件。 86 | 在这里，你可以更改Netdata使用`python.d`收集度量标准或传递其他命令选项的频率： 87 | 88 | ```conf 89 | [plugin:python.d] 90 | update every = 1 91 | command options = 92 | ``` 93 | 94 | `python.d`插件在`/etc/netdata/python.d.conf`中具有一个单独的配置文件，用于启用和禁用模块。 你可以使用`edit-config`脚本来编辑文件，或者使用你选择的文本编辑器打开文件： 95 | 96 | ```bash 97 | sudo /etc/netdata/edit-config python.d.conf 98 | ``` 99 | 100 | 最后，nginx模块在`python.d`文件夹中有一个名为`nginx.conf`的配置文件。 同样，使用`edit-config`或你选择的编辑器： 101 | 102 | ```bash 103 | sudo /etc/netdata/edit-config python.d/nginx.conf 104 | ``` 105 | 106 | 在`nginx.conf`文件中，你会找到其他选项。 默认设置适用于大多数情况，但是你可能需要根据特定的Nginx设置进行更改。 107 | 108 | **下一步是什么？**： 109 | 110 | - 查看[数据收集模块的完整列表](Add-more-charts-to-netdata.md#available-data-collection-modules)，以配置用于自动检测和监视的源。 111 | - 提高Netdata在低内存系统上的[性能](Performance.md)。 112 | - 配置`systemd`以自动公开[系统服务利用率](../collectors/cgroups.plugin/README.md#monitoring-systemd-services) 指标。 113 | - `netdata.conf`中的[重新配置单个图表](../daemon/config/README.md#per-chart-configuration)。 114 | 115 | ##健康监控和警报 116 | 117 | Netdata带有数百种运行状况监视警报，用于检测生产服务器上的异常。 如果你在工作站上运行Netdata，则可能要禁用Netdata的警报。 118 | 119 | 编辑你的`/etc/netdata/netdata.conf`文件并设置以下内容： 120 | 121 | ```conf 122 | [health] 123 | enabled = no 124 | ``` 125 | 126 | 如果你想保持健康监控功能，但关闭电子邮件通知，请使用`edit-config`或你选择的文本编辑器编辑`health_alarm_notify.conf`文件： 127 | 128 | ```bash 129 | sudo /etc/netdata/edit-config health_alarm_notify.conf 130 | ``` 131 | 132 | 查找`SEND_EMAIL="YES"` 行将其改为`SEND_EMAIL="NO"`。 133 | 134 | **下一步是什么？**： 135 | 136 | - 使用[示例](../health/REFERENCE.md)编写你自己的健康警报。 137 | - 添加新的通知方法，例如[Slack](../health/notifications/slack/)。 138 | 139 | ## Change how long Netdata stores metrics 140 | ## 更改Netdata存储指标的时间 141 | 142 | 默认情况下，Netdata使用自定义数据库，该数据库同时使用RAM和磁盘来存储指标。 最近的度量标准存储在系统的RAM中，以保持快速访问，而历史度量标准则“堆积”到磁盘上，以保持较低的RAM使用率。 143 | 144 | 这个自定义数据库（我们称为_database engine_）使您可以存储比系统可用RAM大得多的数据集。 145 | 146 | 如果不确定使用数据库引擎还是要调整默认设置来存储更多历史指标，请查看我们的教程：[**更改Netdata存储指标的时间**](../docs/tutorials/longer-metrics-storage.md)。 147 | 148 | **What's next?**: 149 | 150 | - 了解有关[数据库引擎的内存要求](../database/engine/README.md#memory-requirements)的更多信息，以了解应承诺多少RAM或者磁盘空间来存储历史指标。 151 | - 阅读有关[循环数据库](../database/)的内存要求，或弄清楚您的系统是否启用了KSM，这可以[减少默认数据库的内存使用量](../database/README.md#ksm)的大约60％。 152 | 153 | ## 使用Netdata监视多个系统 154 | 155 | 如果您在多个系统上安装了Netdata，则可以将它们全部显示在仪表板左上角的**我的节点**菜单中。 156 | 157 | 要在该菜单中显示所有服务器，您需要[注册或登录](../docs/netdata-cloud/signing-in.md)到[Netdata Cloud](../docs/netdata-cloud/)。然后，每个系统将显示在“我的节点”菜单中，您可以使用该菜单在系统之间快速导航。 158 | 159 | ![的我的节点菜单中的GIF动画](https://user-images.githubusercontent.com/1153921/64389938-9aa7b800-cff9-11e9-9653-a77e791811ad.gif) 160 | 161 | 每当平移，缩放，突出显示，选择或暂停图表时，Netdata都会通过我的节点菜单将这些设置与您访问的任何其他代理进行同步。即使滚动位置也已同步，所以您将看到相同的图表和相应的数据，以便进行比较或根本原因分析。 162 | 163 | 现在，您可以无缝跟踪整个基础架构中的性能异常！ 164 | 165 | **下一步是什么？**： 166 | 167 | - 阅读有关[Netdata Cloud注册表的工作原理](../registry/)，以及它存储并发送到Web浏览器的数据类型的信息。 168 | - 熟悉[节点视图](../docs/netdata-cloud/nodes-view.md) 169 | 170 | ## Start, stop, and restart Netdata 171 | ## 启动，停止和重新启动Netdata 172 | 173 | 安装Netdata时，它被配置为在引导时启动，然后停止并重新启动/关闭。 您不需要手动启动或停止Netdata，但是您可能需要在某个时候重新启动Netdata。 174 | 175 | - 要**启动** Netdata，请打开一个终端并运行`service netdata start`。 176 | - 要**停止** Netdata，运行`service netdata stop`。 177 | - 要**重新启动** Netdata，请运行`service netdata restart`。 178 | 179 | `service`命令是一个包装器脚本，它尝试使用系统首选的基于系统启动或停止Netdata的方法。 但是，如果这些命令中的任何一个失败，请尝试对`systemd`和`init.d`使用等效命令： 180 | 181 | - **systemd**：`systemctl start netdata`，`systemctl stop netdata`，`systemctl restart netdata`。 182 | - **init.d**: `/etc/init.d/netdata start`, `/etc/init.d/netdata stop`, `/etc/init.d/netdata restart`。 183 | 184 | ##下一步是什么？ 185 | 186 | 即使您已经配置了`netdata.conf`，调整了警报，了解了性能疑难解答的基本知识并将所有系统添加到**我的节点**菜单中，您才刚刚开始使用Netdata。 187 | 188 | 看一些更高级的功能和配置： 189 | 190 | - 使用[流](../streaming)集中来自许多系统的Netdata指标 191 | - 通过[后端](../backends)到时间序列数据库启用Netdata指标的长期归档。 192 | - 通过将Netdata放在[带有SSL的Nginx代理](Running-behind-nginx.md)的后面来提高安全性。 193 | 194 | 或者，了解更多有关如何为[Netdata core](../CONTRIBUTING.md)或我们的[documentation](../docs/contributing/contributing-documentation.md)做出贡献的信息！ 195 | 196 | [![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%2FGettingStarted&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 197 | 198 | -------------------------------------------------------------------------------- /kr/docs/Running-behind-nginx.md: -------------------------------------------------------------------------------- 1 | # Nginx에서 Netdata 동작 2 | 3 | ## 서문 4 | 5 | [Nginx](https://nginx.org/en/)는 HTTP, 리버스 프록시 서버, 메일 프록시 서버 및 모든 크기의 응용 프로그램이나 웹 사이트를 호스팅 하는데 사용되는 generic TCP/UDP 프록시 서버입니다. 6 | 7 | 이 소프트웨어는 메모리 자원에 미치는 영향이 적고, 높은 확장성을 지니며, 안전하고 예측 가능한 성능을 제공할 수 있는 모듈식 이벤트 중심 아키텍처로 알려져 있습니다. 8 | 9 | ## 왜 Nginx를 사용해야 하는가 10 | 11 | - 기본적으로 Nginx는 빠르고 가볍습니다. 12 | 13 | - Nginx는 단일 서버에서 다른 Netdata 인스턴스에 접근하려는 경우 유용합니다. 14 | 15 | - Netdata 클라우드 로그인 메커니즘을 통해 분산 시스템이 적용될 때 까지 Netdata으로 접근할 때 비밀번호로 보호할 수 있습니다. 16 | 17 | - TLS(HTTPS)를 지원하는 Netdata v1.16.0 이전에는 Netdata에 대한 통신을 암호화 하기위해 프록시가 필수적이었습니다. 18 | 19 | ## Nginx 설정 파일 20 | 21 | 모든 Nginx 설정은 `/etc/nginx/` 디렉토리에서 찾을 수 있습니다. 기본 설정 파일은 `/etc/nginx/nginx.conf`입니다. 웹사이트나 앱 별 설정은 `/etc/nginx/site-available/` 디렉토리에서 찾을 수 있습니다. 22 | 23 | Nginx의 설정 옵션을 지시어(directives)라고 합니다. 지시어는 블록이나 컨텍스트와 같은 그룹으로 구성 되어있습니다. 두 용어는 서로 바꿔 사용할 수 있습니다. 24 | 25 | 설치 소스에 따라 예제 설정 파일이 `/etc/nginx/conf.d/default.conf`나 `etc/nginx/sites-enabled/default`에 위치해 있습니다. 경우에 따라 `sites-available`와 `sites-enabled` 디렉토리를 수동으로 생성해야할 수 있습니다. 26 | 27 | Nginx 설정 파일은 Nano, Vim이나 기타 선호하는 텍스트 에디터에서 편집할 수 있습니다. 28 | 29 | 설정 파일을 변경한 후에: 30 | 31 | - `nginx -t`를 입력하여 Nginx 설정을 테스트할 수 있습니다. 32 | 33 | - 변경 사항 적용을 위해 `/etc/init.d/nginx restart`나 `service nginx restart`를 입력하여 Nginx를 재시작하십시오. 34 | 35 | ## Nginx를 통한 Netdata 접근 36 | 37 | ### 가상 호스트로 38 | 39 | `SERVER_IP_ADDRESS:19999` 대신 아래의 방법을 이용하면 아래 설정의 `netdata.example.com`와 같이 사람이 읽을 수 있는 URL을 통해 Netdata 대쉬보드에 접속할 수 있습니다. 40 | 41 | ```conf 42 | upstream backend { 43 | # the Netdata server 44 | server 127.0.0.1:19999; 45 | keepalive 64; 46 | } 47 | 48 | server { 49 | # nginx listens to this 50 | listen 80; 51 | 52 | # the virtual host name of this 53 | server_name netdata.example.com; 54 | 55 | location / { 56 | proxy_set_header X-Forwarded-Host $host; 57 | proxy_set_header X-Forwarded-Server $host; 58 | proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 59 | proxy_pass http://backend; 60 | proxy_http_version 1.1; 61 | proxy_pass_request_headers on; 62 | proxy_set_header Connection "keep-alive"; 63 | proxy_store off; 64 | } 65 | } 66 | ``` 67 | 68 | ### 기존의 가상 호스트의 하위 폴더로 69 | 70 | 이 방법은 Netdata가 하위 폴더 (혹은 디렉토리)에서 제공될 때 권장합니다. 71 | 이 경우 가상 호스트 `netdata.example.com`가 이미 존재하여야 하며, Netdata는 `netdata.example.com/netdata/`를 통해 접속해야 합니다. 72 | 73 | ```conf 74 | upstream netdata { 75 | server 127.0.0.1:19999; 76 | keepalive 64; 77 | } 78 | 79 | server { 80 | listen 80; 81 | 82 | # the virtual host name of this subfolder should be exposed 83 | #server_name netdata.example.com; 84 | 85 | location = /netdata { 86 | return 301 /netdata/; 87 | } 88 | 89 | location ~ /netdata/(?.*) { 90 | proxy_redirect off; 91 | proxy_set_header Host $host; 92 | 93 | proxy_set_header X-Forwarded-Host $host; 94 | proxy_set_header X-Forwarded-Server $host; 95 | proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 96 | proxy_http_version 1.1; 97 | proxy_pass_request_headers on; 98 | proxy_set_header Connection "keep-alive"; 99 | proxy_store off; 100 | proxy_pass http://netdata/$ndpath$is_args$args; 101 | 102 | gzip on; 103 | gzip_proxied any; 104 | gzip_types *; 105 | } 106 | } 107 | ``` 108 | 109 | ### 1개의 Nginx를 통한 다수의 Netdata 서버의 하위 폴더로 110 | 111 | 이 방법은 한 개의 Nginx로 하위폴더를 통해 다수의 Netdata 서버를 관리할 떄 권장합니다. 112 | 113 | ```conf 114 | upstream backend-server1 { 115 | server 10.1.1.103:19999; 116 | keepalive 64; 117 | } 118 | upstream backend-server2 { 119 | server 10.1.1.104:19999; 120 | keepalive 64; 121 | } 122 | 123 | server { 124 | listen 80; 125 | 126 | # the virtual host name of this subfolder should be exposed 127 | #server_name netdata.example.com; 128 | 129 | location ~ /netdata/(?.*)/(?.*) { 130 | proxy_set_header X-Forwarded-Host $host; 131 | proxy_set_header X-Forwarded-Server $host; 132 | proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 133 | proxy_http_version 1.1; 134 | proxy_pass_request_headers on; 135 | proxy_set_header Connection "keep-alive"; 136 | proxy_store off; 137 | proxy_pass http://backend-$behost/$ndpath$is_args$args; 138 | 139 | gzip on; 140 | gzip_proxied any; 141 | gzip_types *; 142 | } 143 | 144 | # make sure there is a trailing slash at the browser 145 | # or the URLs will be wrong 146 | location ~ /netdata/(?.*) { 147 | return 301 /netdata/$behost/; 148 | } 149 | } 150 | ``` 151 | 152 | 원하는 만큼 백엔드 서버를 추가할 수 있습니다. 153 | 154 | 위의 경우 아래와 같이 백엔드 서버에서 Netdata에 접속합니다.: 155 | 156 | - `http://netdata.example.com/netdata/server1/` to reach `backend-server1` 157 | - `http://netdata.example.com/netdata/server2/` to reach `backend-server2` 158 | 159 | ### Nginx - Netdata 간의 통신 암호화 160 | 161 | Netdata의 웹서버가 [TLS를 사용하도록 설정](../web/server/#enabling-tls-support)된 경우 마지막 목적지(final destination)로 TLS를 사용하도록 Nginx 설정을 작성해야 합니다. 이를 위해서 `nginx.conf`에 다음과 같은 파라미터를 추가하십시오. : 162 | 163 | ```conf 164 | proxy_set_header X-Forwarded-Proto https; 165 | proxy_pass https://localhost:19999; 166 | ``` 167 | 168 | 선택적으로 [Nginx에서 TLS/SSL를 활성화](http://nginx.org/en/docs/http/configuring_https_servers.html)할 수 있습니다. 이렇게 하면 사용자는 Nginx - Netdata 간 통신의 암호화 뿐 아니라, Nginx - 사용자 간 통신 또한 암호화할 수 있습니다. 169 | 170 | 여기에 기술된 것 처럼 설정하지 않은 경우 `SSL_ERROR_RX_RECORD_TOO_LONG` 오류가 표시될 수 있습니다. 171 | 172 | ### 인증 활성화 173 | 174 | Nginx를 통한 기본 인증 활성화를 위한 인증 파일을 생성하면 Netdata 대쉬보드를 보호할 수 있습니다. 175 | 176 | 인증 파일이 없다면 아래의 명령어를 사용할 수 있습니다. : 177 | 178 | ```sh 179 | printf "yourusername:$(openssl passwd -apr1)" > /etc/nginx/passwords 180 | ``` 181 | 182 | 그 후 아래의 방법과 같이 서버 지시문 내의 인증을 활성화 하십시오. : 183 | 184 | ```conf 185 | server { 186 | # ... 187 | auth_basic "Protected"; 188 | auth_basic_user_file passwords; 189 | # ... 190 | } 191 | ``` 192 | 193 | ## Netdata에 직접 접근 제한 194 | 195 | 당신의 Nginx가 `localhost`에 있으면 Netdata 보호를 위해 아래와 같은 방법을 사용할 수 있습니다. : 196 | 197 | ``` 198 | [web] 199 | bind to = 127.0.0.1 ::1 200 | ``` 201 | 202 | --- 203 | 204 | 또한 유닉스 도메인 소켓을 사용할 수 있습니다. 유닉스 도메인 소켓은 Nginx - Netdata 간 더 빠른 루트를 제공합니다. 205 | 206 | ``` 207 | [web] 208 | bind to = unix:/var/run/netdata/netdata.sock 209 | ``` 210 | 211 | *note: Netdata v1.8+ 에서 unix domain sockets을 지원합니다.* 212 | 213 | Nginx 쪽에서 동일한 유닉스 도메인 소켓을 사용하기 위해 아래와 같이 설정하십시오. : 214 | 215 | ```conf 216 | upstream backend { 217 | server unix:/var/run/netdata/netdata.sock; 218 | keepalive 64; 219 | } 220 | ``` 221 | 222 | --- 223 | 224 | Nginx 서버가 localhost에 있지 않으면 다음과 같이 설정하십시오. : 225 | 226 | ``` 227 | [web] 228 | bind to = * 229 | allow connections from = IP_OF_NGINX_SERVER 230 | ``` 231 | 232 | *note: Netdata v1.9+ 에서 `allow connections from`를 지원합니다.* 233 | 234 | `allow connections from`은 연결 IP 주소와 일치하는 [Netdata simple patterns](../libnetdata/simple_pattern/)을 허용합니다. 235 | 236 | ## 이중 access.log 방지 237 | 238 | Nginx, Netdata 모두 엑세스를 기록합니다. `/etc/netdata/netdata.conf`에서 아래와 같이 설정하여 Netata가 엑세스 로그를 생성하지 않도록 막을 수 있습니다. : 239 | 240 | ``` 241 | [global] 242 | access log = none 243 | ``` 244 | 245 | ## SELinux 246 | 247 | 만약 502 Bad Gateway error가 발생한 경우 Nginx 에러 로그를 확인하십시오. : 248 | 249 | ```sh 250 | # cat /var/log/nginx/error.log: 251 | 2016/09/09 12:34:05 [crit] 5731#5731: *1 connect() to 127.0.0.1:19999 failed (13: Permission denied) while connecting to upstream, client: 1.2.3.4, server: netdata.example.com, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:19999/", host: "netdata.example.com" 252 | ``` 253 | 254 | 위와 같은 것이 보이면 SELinux가 Nginx를 백엔드 서버에 연결하지 못하도록 막고있을 가능성이 높습니다. 이를 해결하기 위해 `setsebool -P httpd_can_network_connect true` 정책을 사용하십시오. 255 | 256 | [![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%2FRunning-behind-nginx&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 257 | -------------------------------------------------------------------------------- /zh/docs/Running-behind-haproxy.md: -------------------------------------------------------------------------------- 1 | ＃通过HAProxy运行Netdata 2 | 3 | > HAProxy是一种免费，非常快速且可靠的解决方案，可提供高可用性，负载平衡，并代理基于TCP和HTTP的应用程序。它特别适合于流量很高的网站并为世界上访问量最大的国家提供支持。 4 | 5 | 如果 Netdata 在运行 HAProxy 的主机上运行，​​而不是从端口号，域名连接到 Netdata 6 | 可以指向 HAProxy，并且 HAProxy 可以将连接重定向到 Netdata 端口。这可以使 7 | 通过或连接到 Netdata ，这比更好。 8 | 9 | 要将[HAProxy](https://github.com/haproxy/haproxy)的请求代理到 Netdata，可以使用以下配置： 10 | 11 | ##默认配置 12 | 13 | 对于所有示例，将模式设置为`http` 14 | 15 | ```conf 16 | defaults 17 | mode http 18 | ``` 19 | 20 | ##简单配置 21 | 22 | 一个简单的示例，其中使用基本的URL(例如)而没有子路径： 23 | 24 | ###前端 25 | 26 | 创建一个前端来接收请求。 27 | 28 | ```conf 29 | frontend http_frontend 30 | ## HTTP ipv4 and ipv6 on all ips ## 31 | bind :::80 v4v6 32 | 33 | default_backend netdata_backend 34 | ``` 35 | 36 | ###后端 37 | 38 | 创建 Netdata 后端，该后端将向端口`19999`发送请求。 39 | 40 | ```conf 41 | backend netdata_backend 42 | option forwardfor 43 | server netdata_local 127.0.0.1:19999 44 | 45 | http-request set-header Host %[src] 46 | http-request set-header X-Forwarded-For %[src] 47 | http-request set-header X-Forwarded-Port %[dst_port] 48 | http-request set-header Connection "keep-alive" 49 | ``` 50 | 51 | ##配置子路径 52 | 53 | 将基本URL与子路径`/netdata/`结合使用的示例： 54 | 55 | ###前端 56 | 57 | 要使用子路径，请创建一个ACL，该ACL将基于子路径设置变量。 58 | 59 | ```conf 60 | frontend http_frontend 61 | ## HTTP ipv4 and ipv6 on all ips ## 62 | bind :::80 v4v6 63 | 64 | # URL begins with /netdata 65 | acl is_netdata url_beg /netdata 66 | 67 | # if trailing slash is missing, redirect to /netdata/ 68 | http-request redirect scheme https drop-query append-slash if is_netdata ! { path_beg /netdata/ } 69 | 70 | ## Backends ## 71 | use_backend netdata_backend if is_netdata 72 | 73 | # Other requests go here (optional) 74 | # put netdata_backend here if no others are used 75 | default_backend www_backend 76 | ``` 77 | 78 | ###后端 79 | 80 | 与简单示例相同，只是使用正则表达式删除`/netdata/`。 81 | 82 | ```conf 83 | backend netdata_backend 84 | option forwardfor 85 | server netdata_local 127.0.0.1:19999 86 | 87 | http-request set-path %[path,regsub(^/netdata/,/)] 88 | 89 | http-request set-header Host %[src] 90 | http-request set-header X-Forwarded-For %[src] 91 | http-request set-header X-Forwarded-Port %[dst_port] 92 | http-request set-header Connection "keep-alive" 93 | ``` 94 | 95 | ##使用TLS通讯 96 | 97 | 可以通过在前端添加端口443和证书来使用TLS。 98 | 如果主机匹配example.com（用你的域替换），则此示例将仅使用Netdata。 99 | 100 | ###前端 101 | 102 | 该前端使用证书列表。 103 | 104 | ```conf 105 | frontend https_frontend 106 | ## HTTP ## 107 | bind :::80 v4v6 108 | # Redirect all HTTP traffic to HTTPS with 301 redirect 109 | redirect scheme https code 301 if !{ ssl_fc } 110 | 111 | ## HTTPS ## 112 | # Bind to all v4/v6 addresses, use a list of certs in file 113 | bind :::443 v4v6 ssl crt-list /etc/letsencrypt/certslist.txt 114 | 115 | ## ACL ## 116 | # Optionally check host for Netdata 117 | acl is_example_host hdr_sub(host) -i example.com 118 | 119 | ## Backends ## 120 | use_backend netdata_backend if is_example_host 121 | # Other requests go here (optional) 122 | default_backend www_backend 123 | ``` 124 | 125 | 在证书列表文件中，放置从证书文件到所使用域的映射： 126 | 127 | `/etc/letsencrypt/certslist.txt`: 128 | 129 | ```txt 130 | example.com /etc/letsencrypt/live/example.com/example.com.pem 131 | ``` 132 | 133 | 文件`/etc/letsencrypt/live/example.com/example.com.pem`应该包含按顺序连接到`.pem`文件中的密钥和证书。 134 | 135 | ```sh 136 | cat /etc/letsencrypt/live/example.com/fullchain.pem \ 137 | /etc/letsencrypt/live/example.com/privkey.pem > \ 138 | /etc/letsencrypt/live/example.com/example.com.pem 139 | ``` 140 | 141 | ###后端 142 | 143 | 除了设置协议`https`之外，其他与简单相同。 144 | 145 | ```conf 146 | backend netdata_backend 147 | option forwardfor 148 | server netdata_local 127.0.0.1:19999 149 | 150 | http-request add-header X-Forwarded-Proto https 151 | http-request set-header Host %[src] 152 | http-request set-header X-Forwarded-For %[src] 153 | http-request set-header X-Forwarded-Port %[dst_port] 154 | http-request set-header Connection "keep-alive" 155 | ``` 156 | 157 | ##启用身份验证 158 | 159 | 要使用基本的HTTP身份验证，请创建一个身份验证列表： 160 | 161 | ```conf 162 | # HTTP Auth 163 | userlist basic-auth-list 164 | group is-admin 165 | # Plaintext password 166 | user admin password passwordhere groups is-admin 167 | ``` 168 | 169 | 你可以使用`mkpassword`实用程序创建一个哈希密码。 170 | 171 | ```sh 172 | printf "passwordhere" | mkpasswd --stdin --method=sha-256 173 | $5$l7Gk0VPIpKO$f5iEcxvjfdF11khw.utzSKqP7W.0oq8wX9nJwPLwzy1 174 | ``` 175 | 176 | 用hash替换`passwordhere`： 177 | 178 | ```conf 179 | user admin password $5$l7Gk0VPIpKO$f5iEcxvjfdF11khw.utzSKqP7W.0oq8wX9nJwPLwzy1 groups is-admin 180 | ``` 181 | 182 | 现在在后端顶部添加： 183 | 184 | ```conf 185 | acl devops-auth http_auth_group(basic-auth-list) is-admin 186 | http-request auth realm netdata_local unless devops-auth 187 | ``` 188 | 189 | ##完整示例 190 | 191 | 带有子路径的TLS上的HTTP身份验证的完整示例配置： 192 | 193 | ```conf 194 | global 195 | maxconn 20000 196 | 197 | log /dev/log local0 198 | log /dev/log local1 notice 199 | user haproxy 200 | group haproxy 201 | pidfile /run/haproxy.pid 202 | 203 | stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners 204 | stats timeout 30s 205 | daemon 206 | 207 | tune.ssl.default-dh-param 4096 # Max size of DHE key 208 | 209 | # Default ciphers to use on SSL-enabled listening sockets. 210 | ssl-default-bind-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:RSA+AESGCM:RSA+AES:!aNULL:!MD5:!DSS 211 | ssl-default-bind-options no-sslv3 212 | 213 | defaults 214 | log global 215 | mode http 216 | option httplog 217 | option dontlognull 218 | timeout connect 5000 219 | timeout client 50000 220 | timeout server 50000 221 | errorfile 400 /etc/haproxy/errors/400.http 222 | errorfile 403 /etc/haproxy/errors/403.http 223 | errorfile 408 /etc/haproxy/errors/408.http 224 | errorfile 500 /etc/haproxy/errors/500.http 225 | errorfile 502 /etc/haproxy/errors/502.http 226 | errorfile 503 /etc/haproxy/errors/503.http 227 | errorfile 504 /etc/haproxy/errors/504.http 228 | 229 | frontend https_frontend 230 | ## HTTP ## 231 | bind :::80 v4v6 232 | # Redirect all HTTP traffic to HTTPS with 301 redirect 233 | redirect scheme https code 301 if !{ ssl_fc } 234 | 235 | ## HTTPS ## 236 | # Bind to all v4/v6 addresses, use a list of certs in file 237 | bind :::443 v4v6 ssl crt-list /etc/letsencrypt/certslist.txt 238 | 239 | ## ACL ## 240 | # Optionally check host for Netdata 241 | acl is_example_host hdr_sub(host) -i example.com 242 | acl is_netdata url_beg /netdata 243 | 244 | http-request redirect scheme https drop-query append-slash if is_netdata ! { path_beg /netdata/ } 245 | 246 | ## Backends ## 247 | use_backend netdata_backend if is_example_host is_netdata 248 | default_backend www_backend 249 | 250 | # HTTP Auth 251 | userlist basic-auth-list 252 | group is-admin 253 | # Hashed password 254 | user admin password $5$l7Gk0VPIpKO$f5iEcxvjfdF11khw.utzSKqP7W.0oq8wX9nJwPLwzy1 groups is-admin 255 | 256 | ## Default server(s) (optional)## 257 | backend www_backend 258 | mode http 259 | balance roundrobin 260 | timeout connect 5s 261 | timeout server 30s 262 | timeout queue 30s 263 | 264 | http-request add-header 'X-Forwarded-Proto: https' 265 | server other_server 111.111.111.111:80 check 266 | 267 | backend netdata_backend 268 | acl devops-auth http_auth_group(basic-auth-list) is-admin 269 | http-request auth realm netdata_local unless devops-auth 270 | 271 | option forwardfor 272 | server netdata_local 127.0.0.1:19999 273 | 274 | http-request set-path %[path,regsub(^/netdata/,/)] 275 | 276 | http-request add-header X-Forwarded-Proto https 277 | http-request set-header Host %[src] 278 | http-request set-header X-Forwarded-For %[src] 279 | http-request set-header X-Forwarded-Port %[dst_port] 280 | http-request set-header Connection "keep-alive" 281 | ``` 282 | 283 | [![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%2FRunning-behind-haproxy&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) -------------------------------------------------------------------------------- /kr/docs/Running-behind-haproxy.md: -------------------------------------------------------------------------------- 1 | # HAProxy를 이용한 Netdata 2 | 3 | > HAProxy는 TCP, HTTP 기반의 응용 프로그램을 위한 고가용성, 로드 밸런싱, 프록시를제공하는 빠르고 안정적인 무료 솔루션입니다. 트래픽이 많은 웹 사이트에 적합합니다. 4 | 5 | HAProxy를 실행하는 호스트에서 Netdata를 실행 중인 경우 포트 번호를 Netdata에 연결하지 않고, 도메인 네임을 HAProxy에 연결하고 HAProxy가 Netdata 포트를 리다이렉션으로 연결시킬 수 있습니다. 이를 통해 Netdata를 와 같이 포트를 입력하여 접속할 필요 없이 나 와 같이 주소로 접속할 수 있게 됩니다. 6 | 7 | [HAProxy](https://github.com/haproxy/haproxy)에서 Netdata로 프록시 요청하기 위해, 다음 설정을 사용할 수 있습니다.: 8 | 9 | ## 기본 설정 10 | 11 | 모든 예제에서 모드는 `http`로 설정합니다. 12 | 13 | ```conf 14 | defaults 15 | mode http 16 | ``` 17 | 18 | ## 간단한 설정 19 | 20 | (와 같이) 하위 경로 없이 기본 URL로 사용하는 간단한 예제: 21 | 22 | ### 프론트엔드 23 | 24 | 요청을 받기 위해 프론트엔드를 생성하세요. 25 | 26 | ```conf 27 | frontend http_frontend 28 | ## HTTP ipv4 and ipv6 on all ips ## 29 | bind :::80 v4v6 30 | 31 | default_backend netdata_backend 32 | ``` 33 | 34 | ### 백엔드 35 | 36 | `19999`를 통해 요청을 보내기 위해 Netdata 백엔드를 생성하세요. 37 | 38 | ```conf 39 | backend netdata_backend 40 | option forwardfor 41 | server netdata_local 127.0.0.1:19999 42 | 43 | http-request set-header Host %[src] 44 | http-request set-header X-Forwarded-For %[src] 45 | http-request set-header X-Forwarded-Port %[dst_port] 46 | http-request set-header Connection "keep-alive" 47 | ``` 48 | 49 | ## 하위 경로를 사용하기 위한 설정 50 | 51 | 기본 URL에 `/netdata/`를 하위경로로 사용하는 예제: 52 | 53 | ### 프론트엔드 54 | 55 | 하위 경로를 사용하기 위해 하위 경로를 기반으로 변수를 설정하는 접근 제어 목록(ACL)을 생성하세요. 56 | 57 | ```conf 58 | frontend http_frontend 59 | ## HTTP ipv4 and ipv6 on all ips ## 60 | bind :::80 v4v6 61 | 62 | # URL begins with /netdata 63 | acl is_netdata url_beg /netdata 64 | 65 | # if trailing slash is missing, redirect to /netdata/ 66 | http-request redirect scheme https drop-query append-slash if is_netdata ! { path_beg /netdata/ } 67 | 68 | ## Backends ## 69 | use_backend netdata_backend if is_netdata 70 | 71 | # Other requests go here (optional) 72 | # put netdata_backend here if no others are used 73 | default_backend www_backend 74 | ``` 75 | 76 | ### 백엔드 77 | 78 | 정규식으로 `/netdata/`를 추가해주는 것을 제외하면 간단한 설정에서 했던 것과 동일합니다.: 79 | 80 | ```conf 81 | backend netdata_backend 82 | option forwardfor 83 | server netdata_local 127.0.0.1:19999 84 | 85 | http-request set-path %[path,regsub(^/netdata/,/)] 86 | 87 | http-request set-header Host %[src] 88 | http-request set-header X-Forwarded-For %[src] 89 | http-request set-header X-Forwarded-Port %[dst_port] 90 | http-request set-header Connection "keep-alive" 91 | ``` 92 | 93 | ## TLS 통신 사용 94 | 95 | `443`포트와 인증서를 프론트엔드에 추가하면 TLS를 사용할 수 있습니다. 96 | 이 예시는 당신의 도메인(아래 예시에서는 example.com)과 호스트가 일치하는 경우에만 사용합니다. 97 | 98 | ### 프론트엔드 99 | 100 | 이 프론트엔드에서는 인증서 목록을 사용합니다. 101 | 102 | ```conf 103 | frontend https_frontend 104 | ## HTTP ## 105 | bind :::80 v4v6 106 | # Redirect all HTTP traffic to HTTPS with 301 redirect 107 | redirect scheme https code 301 if !{ ssl_fc } 108 | 109 | ## HTTPS ## 110 | # Bind to all v4/v6 addresses, use a list of certs in file 111 | bind :::443 v4v6 ssl crt-list /etc/letsencrypt/certslist.txt 112 | 113 | ## ACL ## 114 | # Optionally check host for Netdata 115 | acl is_example_host hdr_sub(host) -i example.com 116 | 117 | ## Backends ## 118 | use_backend netdata_backend if is_example_host 119 | # Other requests go here (optional) 120 | default_backend www_backend 121 | ``` 122 | 123 | 인증서 목록 파일 안에서 인증서 파일에서 사용된 도메인으로 매핑을 배치해야합니다.: 124 | 125 | `/etc/letsencrypt/certslist.txt`: 126 | 127 | ```txt 128 | example.com /etc/letsencrypt/live/example.com/example.com.pem 129 | ``` 130 | 131 | `/etc/letsencrypt/live/example.com/example.com.pem`파일은 `.pem` 파일에 연결된 키와 인증서가 포함되어야 합니다.: 132 | 133 | ```sh 134 | cat /etc/letsencrypt/live/example.com/fullchain.pem \ 135 | /etc/letsencrypt/live/example.com/privkey.pem > \ 136 | /etc/letsencrypt/live/example.com/example.com.pem 137 | ``` 138 | 139 | ### 백엔드 140 | 141 | 프로토콜을 `https`로 설정하는 것을 제외하면 간단한 예제에서와 동일합니다. 142 | 143 | ```conf 144 | backend netdata_backend 145 | option forwardfor 146 | server netdata_local 127.0.0.1:19999 147 | 148 | http-request add-header X-Forwarded-Proto https 149 | http-request set-header Host %[src] 150 | http-request set-header X-Forwarded-For %[src] 151 | http-request set-header X-Forwarded-Port %[dst_port] 152 | http-request set-header Connection "keep-alive" 153 | ``` 154 | 155 | ## 인증 활성화 156 | 157 | 기본적인 HTTP 인증을 사용하기 위해 다음과 같이 인증 목록을 사용하십시오.: 158 | 159 | ```conf 160 | # HTTP Auth 161 | userlist basic-auth-list 162 | group is-admin 163 | # Plaintext password 164 | user admin password passwordhere groups is-admin 165 | ``` 166 | 167 | `mkpassword` 유틸리티를 이용하여 해시된 암호를 생성할 수 있습니다. : 168 | 169 | ```sh 170 | printf "passwordhere" | mkpasswd --stdin --method=sha-256 171 | $5$l7Gk0VPIpKO$f5iEcxvjfdF11khw.utzSKqP7W.0oq8wX9nJwPLwzy1 172 | ``` 173 | 174 | `passwordhere`를 해시로 바꾸십시오. : 175 | 176 | ```conf 177 | user admin password $5$l7Gk0VPIpKO$f5iEcxvjfdF11khw.utzSKqP7W.0oq8wX9nJwPLwzy1 groups is-admin 178 | ``` 179 | 180 | 이제 백엔드 상단에 추가히십시오. : 181 | 182 | ```conf 183 | acl devops-auth http_auth_group(basic-auth-list) is-admin 184 | http-request auth realm netdata_local unless devops-auth 185 | ``` 186 | 187 | ## 전체 예제 188 | 189 | 하위 경로가 있는 TLS를 통한 HTTP 인증을 사용하는 전체 설정 예제 : 190 | 191 | ```conf 192 | global 193 | maxconn 20000 194 | 195 | log /dev/log local0 196 | log /dev/log local1 notice 197 | user haproxy 198 | group haproxy 199 | pidfile /run/haproxy.pid 200 | 201 | stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners 202 | stats timeout 30s 203 | daemon 204 | 205 | tune.ssl.default-dh-param 4096 # Max size of DHE key 206 | 207 | # Default ciphers to use on SSL-enabled listening sockets. 208 | ssl-default-bind-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:RSA+AESGCM:RSA+AES:!aNULL:!MD5:!DSS 209 | ssl-default-bind-options no-sslv3 210 | 211 | defaults 212 | log global 213 | mode http 214 | option httplog 215 | option dontlognull 216 | timeout connect 5000 217 | timeout client 50000 218 | timeout server 50000 219 | errorfile 400 /etc/haproxy/errors/400.http 220 | errorfile 403 /etc/haproxy/errors/403.http 221 | errorfile 408 /etc/haproxy/errors/408.http 222 | errorfile 500 /etc/haproxy/errors/500.http 223 | errorfile 502 /etc/haproxy/errors/502.http 224 | errorfile 503 /etc/haproxy/errors/503.http 225 | errorfile 504 /etc/haproxy/errors/504.http 226 | 227 | frontend https_frontend 228 | ## HTTP ## 229 | bind :::80 v4v6 230 | # Redirect all HTTP traffic to HTTPS with 301 redirect 231 | redirect scheme https code 301 if !{ ssl_fc } 232 | 233 | ## HTTPS ## 234 | # Bind to all v4/v6 addresses, use a list of certs in file 235 | bind :::443 v4v6 ssl crt-list /etc/letsencrypt/certslist.txt 236 | 237 | ## ACL ## 238 | # Optionally check host for Netdata 239 | acl is_example_host hdr_sub(host) -i example.com 240 | acl is_netdata url_beg /netdata 241 | 242 | http-request redirect scheme https drop-query append-slash if is_netdata ! { path_beg /netdata/ } 243 | 244 | ## Backends ## 245 | use_backend netdata_backend if is_example_host is_netdata 246 | default_backend www_backend 247 | 248 | # HTTP Auth 249 | userlist basic-auth-list 250 | group is-admin 251 | # Hashed password 252 | user admin password $5$l7Gk0VPIpKO$f5iEcxvjfdF11khw.utzSKqP7W.0oq8wX9nJwPLwzy1 groups is-admin 253 | 254 | ## Default server(s) (optional)## 255 | backend www_backend 256 | mode http 257 | balance roundrobin 258 | timeout connect 5s 259 | timeout server 30s 260 | timeout queue 30s 261 | 262 | http-request add-header 'X-Forwarded-Proto: https' 263 | server other_server 111.111.111.111:80 check 264 | 265 | backend netdata_backend 266 | acl devops-auth http_auth_group(basic-auth-list) is-admin 267 | http-request auth realm netdata_local unless devops-auth 268 | 269 | option forwardfor 270 | server netdata_local 127.0.0.1:19999 271 | 272 | http-request set-path %[path,regsub(^/netdata/,/)] 273 | 274 | http-request add-header X-Forwarded-Proto https 275 | http-request set-header Host %[src] 276 | http-request set-header X-Forwarded-For %[src] 277 | http-request set-header X-Forwarded-Port %[dst_port] 278 | http-request set-header Connection "keep-alive" 279 | ``` 280 | 281 | [![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%2FRunning-behind-haproxy&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 282 | -------------------------------------------------------------------------------- /kr/docs/getting-started.md: -------------------------------------------------------------------------------- 1 | # 시작 가이드 2 | 3 | Netdata를 사용해 주셔서 감사합니다! 이 가이드에선 당신이 Netdata를 설치한 후 처음 해야할 일을 빠르게 안내합니다. 4 | 5 | Netdata는 별 다른 설정 없이 실시간으로 수천여개의 측정치를 수집할 수 있지만 필요에 따라 Netdata를 최대한 활용하기 위해 알아야 할 몇 가지 중요한 사항이 있습니다. 6 | 7 | > 아직 Netdata를 설치하기 전이라면, 대부분의 Linux 배포판에서 Netdata를 자동으로 설치시켜주는 One-line 스크립트와 세부 지침을 [설치 지침](../packaging/installer)에서 확인하세요. 8 | 9 | ## 대쉬보드에 접속 10 | 11 | 웹 브라우저을 열어 `http://YOUR-HOST:19999`에 접속하십시오. Netdata에 오신 것을 환영합니다! 12 | 13 | ![대쉬보드로 가기 위한 움직이는 gif](https://user-images.githubusercontent.com/1153921/63463901-fcb9c800-c412-11e9-8f67-8fe182e8b0d2.gif) 14 | 15 | **이후에 해야할 것은?**: 16 | 17 | - [standard Netdata dashboard](../web/gui/) 에 대하여 더 읽어보십시오. 18 | - [charts 사용](../web/README.md#using-charts)에 대한 모든 세부사항이나 [charts와 context, families](../web/README.md#charts-contexts-families)의 차이점에 대해 알아보십시오. 19 | 20 | ## 설정 기초 21 | 22 | Netdata는 설정을 변경하기 위해 주로 `netdata.conf` 파일을 사용합니다. 23 | 24 | 대부분의 운영체제에서 `netdata.conf` 파일은 `/etc/netdata/netdata.conf`에서 찾을 수 있습니다. 25 | 26 | > 일부 운영체제에선 `/etc/netdata/netdata.conf`에 `netdata.conf` 파일이 존재하지 않을 수 있습니다. 그럴 경우 `/opt/netdata/etc/netdata/netdata.conf`에서 찾아보십시오. 27 | 28 | `netdata.conf`파일은 `[global]`, `[web]`, `[registry]`등과 같은 다양한 섹션으로 나뉩니다. 기본값으로 대부분의 옵션이 주석처리 되어있습니다. 변경 사항을 적용시키기 위해 (`#`를 제거하여) 주석 처리를 해제해야합니다. 29 | 30 | 변경 사항을 저장한 후 [restart Netdata](#start-stop-and-restart-netdata)로 새로운 설정을 불러오십시오. 31 | 32 | **이후에 해야할 것은?**: 33 | 34 | - `history` 옵션을 증가시키거나 데이터베이스 엔진으로 전환하여 [Netdata가 측정치를 저장하는 기간을 변경하십시오.](#change-how-long-netdata-stores-metrics) 35 | - Netdata의 대쉬보드를 [다른 포트](https://docs.netdata.cloud/web/server/)로 이동시키거나 TLS/HTTPS 암호화를 활성화 시키십시오. 36 | - [daemon configuration documentation](../daemon/config/)에서 `netdata.conf`의 모든 옵션을 확인하십시오. 37 | - 당신의 [registry](../registry/README.md#run-your-own-registry)를 실행시키십시오. 38 | 39 | ## 더 많은 소스에서 데이터 수집 40 | 41 | Netdata가 _시작될 때_ 프로그램은 데이터베이스 서버나 웹 서버 등과 같은 수십개의 **데이터 소스**를 자동 감지합니다. 방금 설치한 서비스나 응용 프로그램에서 측정치를 수집하거나 자동 감지 하기위해 [Netdata를 재시작](#start-stop-and-restart-netdata)해야합니다. 42 | 43 | > 한가지 예외가 있습니다! : Netdata가 (컨테이너 자체가 아닌) 호스트에서 실행 중인 경우에는 항상 컨테이너와 VM을 자동 감지할 것 입니다. 44 | 45 | 그러나 표준 설치 절차를 따라 소스를 설치한 경우에만 자동 감지가 작동합니다. 재시작 후 Netdata가 측정치를 수집하지 않는다면 당신의 소스는 아마 올바르게 설정되지 않았을 수 있습니다. [외부 플러그인 문서](../collectors/plugins.d/) 에서 당신의 소스에 적당한 모듈을 찾으세요. 해당 문서에는 자동 감지를 위해 소스를 설정하는 방법에 대해 자세한 정보를 포함하고있습니다. 46 | 47 | `chrony`같은 일부 모듈은 기본값으로 비활성화되어 있습니다. 자동 감지를 동작시키기 위해 수동으로 활성화 시켜야 합니다. 48 | 49 | Netdata가 유효한 데이터 소스를 감지하면 감지한 소스에서 계속 데이터를 수집하려고 시도합니다. 예를 들어 Netdata가 Nginx 웹 서버에서 데이터를 수집하고 있을 때 당신이 Nginx를 종료시키면 Netdata는 당신이 Nginx를 다시 동작시켰을 때 Netdata를 재시작하지 않아도 새로운 데이터를 수집합니다. 50 | 51 | ### 플러그인 설정 52 | 53 | Netdata가 서비스/응용 프로그램을 자동 감지하더라도, Netdata가 어떤 데이터를 얼마나 자주 수집할 지 설정할 수 있습니다. 54 | 55 | Netdata는 **내부**, **외부**플러그인을 사용하여 데이터를 수집합니다. 내부 플러그인은 Netdata daemon과 함께 작동합니다. 반면 외부 플러그인은 파이프를 통해 Netdata에 측정치를 보내는 독립적인 프로세스입니다. 하나 이상의 데이터 수집 **모듈**이 있는 외부 플러그인인 **오케스트레이터**도 있습니다. 56 | 57 | 개별 모듈과 함께 내, 외부 플러그인을 설정할 수 있습니다. 설정을 위한 다음과 같은 방법이 있습니다. 58 | 59 | 60 | - `netdata.conf`의 `[plugins]` 섹션 : `yes` or `no`로 내, 외부 플러그인을 활성화/비활성화 시키십시오. 61 | - `netdata.conf`의 `[plugin:XXX]` 섹션 : 각 플러그인에는 수집 빈도수를 변경하거나 플러그인에 옵션을 전달하는 섹션이 있습니다. 62 | - 각 외부 플러그인의 `.conf` 파일 : `/etc/netdata/python.d.conf`에서 예시를 참고하세요. 63 | - 각 모듈의 `.conf` 파일 : `/etc/netdata/python.d/nginx.conf`에서 예시를 참고하세요. 64 | 65 | 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. 66 | 67 | 이 과정은 복잡하기 때문에 `nginx` 모듈과 `python.d` 플러그인 오케스트레이터를 사용하여 Nginx 웹서버 68 | 69 | 먼저 `netdata.conf`에서 `python.d` 플러그인을 전부 활성화/비활성화 할 수 있습니다. 70 | 71 | ```conf 72 | [plugins] 73 | # Enabled 74 | python.d = yes 75 | # Disabled 76 | python.d = no 77 | ``` 78 | 79 | `netdata.conf`파일의 `[plugin:python.d]` 섹션에서도 `python.d` 외부 플러그인을 설정할 수 있습니다. 여기서 측정치를 수집하거나 다른 커맨드 옵션을 전달하기 위해 Netdata가 `python.d`를 사용하는 빈도를 변경할 수 있습니다. 80 | 81 | ```conf 82 | [plugin:python.d] 83 | update every = 1 84 | command options = 85 | ``` 86 | `python.d` 플러그인은 `/etc/netdata/python.d.conf`에 위치한 분리된 설정 파일에서 모듈을 활성화/비활성화 할 수 있습니다. `edit-config` 스크립트를 사용하여 파일을 편집하거나 텍스트 에디터로 파일을 열 수 있습니다. 87 | 88 | ```bash 89 | sudo /etc/netdata/edit-config python.d.conf 90 | ``` 91 | 92 | 마지막으로 `nginx` 모듈은 `python.d`폴더에 `nginx.conf`라는 설정 파일을 가지고 있습니다. 마찬가지로 `edit-config`를 사용하거나 텍스트 에디터로 파일을 열 수 있습니다. 93 | 94 | ```bash 95 | sudo /etc/netdata/edit-config python.d/nginx.conf 96 | ``` 97 | 98 | `nginx.conf` 파일에 추가적인 옵션이 존재합니다. 기본값은 대부분의 상황에서 동작하지만 특정 Nginx 설정에 따라 값을 변경해야할 수 있습니다. 99 | 100 | **이후에 해야할 것은?**: 101 | 102 | - 자동 감지와 모니터링을 위한 소스를 설정하기 위해 [data collection modules의 모든 리스트](Add-more-charts-to-netdata.md#available-data-collection-modules)를 확인하십시오. 103 | - 저 메모리 시스템에서의 Netdata의 [performance](Performance.md)을 향상시키십시오. 104 | - [systemd services utilization](../collectors/cgroups.plugin/README.md#monitoring-systemd-services) 측정치를 자동적으로 드러내기 위해 `systemd`를 설정하십시오. 105 | - `netdata.conf`의 [개별 차트를 재구성](../daemon/config/README.md#per-chart-configuration)하십시오. 106 | 107 | ## 상태 모니터링 및 경보 108 | 109 | Netdata는 프로덕션 서버(실제로 서비스를 운용중인 서버)의 이상 상태를 감지하기 위해 수백가지의 상태 모니터링 경보가 제공됩니다. 워크스테이션에서 실행되는 Netdata의 경우 Netdata 경보를 비활성화 할 수 있습니다. 110 | Netdata on a workstation, you might want to disable Netdata's alarms. 111 | 112 | `/etc/netdata/netdata.conf`을 열어 아래를 따라 설정하세요. 113 | 114 | ```conf 115 | [health] 116 | enabled = no 117 | ``` 118 | 119 | 상태 모니터링을 활성화한 상태에서 이메일 알림만 끄고 싶다면 `edit-config`를 사용하거나 텍스트 에디터를 사용해 `health_alarm_notify.conf`를 편집하세요. 120 | 121 | ```bash 122 | sudo /etc/netdata/edit-config health_alarm_notify.conf 123 | ``` 124 | 125 | `SEND_EMAIL="YES"` 라인을 찾아 `SEND_EMAIL="NO"`로 바꾸면 됩니다. 126 | 127 | **이후에 해야할 것은?**: 128 | 129 | - [health quickstart](../health/QUICKSTART.md)를 따라 기존의 상태 entities를 찾아 편집하여 당신의 상태 entities를 만드세요. 130 | - [health configuration reference](../health/REFERENCE.md)에서 모든 경보 옵션을 확인하세요. 131 | - [Slack](../health/notifications/slack/)과 같은 새로운 알람 방법을 추가해보세요. 132 | 133 | ## Netdata가 측정치를 저장하는 기간을 변경 134 | ## Change how long Netdata stores metrics 135 | 136 | Netedata는 RAM과 디스크를 모두 사용하는 커스텀 데이터베이스를 사용하여 측정치를 저장하도록 기본 값이 설정되어 있습니다. 최신의 측정치는 빠른 접근 속도를 위해 RAM에 저장되고 기록 측정치는 RAM 사용량을 낮추기 위해 디스크에 저장됩니다. 137 | 138 | _database engine_ 이라는 이름의 이러한 커스텀 데이터베이스에선 시스템의 가용 RAM보다 더 큰 데이터셋을 저장할 수 있습니다. 139 | 140 | 당신이 database engine을 사용하고 있는지 확실하지 않거나 기록 측정치를 더 저장하기 위해 기본 설정을 조정하려면 다음의 튜토리얼을 확인하십시오 : [**Changing how long Netdata stores metrics**](../docs/tutorials/longer-metrics-storage.md). 141 | 142 | **이후에 해야할 것은?**: 143 | 144 | - [database engine의 메모리 요구 사항](../database/engine/README.md#memory-requirements)을 더 알아보시면 기록 측정치 저장을 위해 얼마나 많은 RAM/디스크 공간을 확보해야 하는지 이해할 수 있습니다. 145 | - [round-robin database](../database/)의 메모리 요구 사항을 읽어보거나 시스템에 KSM이 활성화되어 있는지 확인하여 약 60% 정도 [기본 데이터베이스의 메모리 사용량을 감소](../database/README.md#ksm)시킬 수 있습니다. 146 | 147 | ## Netdata로 다중의 시스템 모니터링 148 | 149 | Netdata를 다중의 시스템에 설치한 경우, 대시보드의 상단 좌측 코너에 있는 **My nodes** 메뉴에서 모두 표시 할 수 있습니다. 150 | 151 | 해당 메뉴에서 모든 서버를 표시하기 위해 152 | To show all your servers in that menu, 각 시스템 마다 [Netdata Cloud](../docs/netdata-cloud/)에 [회원가입이나 로그인](../docs/netdata-cloud/signing-in.md)을 해야합니다. 그러면 각 시스템이 **My nodes** 메뉴에 나타나 당신이 다중의 시스템을 더 빠르게 탐색하도록 사용할 수 있습니다. 153 | 154 | ![Animated GIF of the My Nodes menu in 155 | action](https://user-images.githubusercontent.com/1153921/64389938-9aa7b800-cff9-11e9-9653-a77e791811ad.gif) 156 | 157 | 차트를 이동, 확대, 강조표시, 선택이나 일시 정시 할 때마다 Netdata는 My nodes 메뉴를 통해 당신이 방문한 다른 에이전트와 해당 설정을 동기화합니다. 스크롤 위치 또한 동기화되므로 근본 원인 분석이나 쉬운 비교를 위해 동일한 차트의 각각의 데이터를 확인 할 수 있습니다. 158 | 159 | 이제 전체 인프라에서 성능 이상을 완벽하게 추적할 수 있습니다. 160 | 161 | **이후에 해야할 것은?**: 162 | 163 | - Read up on how the [Netdata Cloud registry works](../registry/), and what kind of data it stores and sends to your web browser. 164 | - Familiarize yourself with the [Nodes View](../docs/netdata-cloud/nodes-view.md) 165 | 166 | ## Netdata 시작, 정지, 재시작 167 | ## Start, stop, and restart Netdata 168 | 169 | Netdata를 설치하면 기본적으로 부팅 시 Netdata가 시작되고, 시스템 종료시 중지, 재시작되도록 설정되어 있습니다. Netdata를 직접 시작하거나 중지할 필요가 없지만 Netdata를 재시작해야할 경우도 있습니다. 170 | 171 | - Netdata를 **start** 하기 위해, 터미널을 켜고 `service netdata start`를 입력하십시오. 172 | - Netdata를 **stop** 하기 위해, 터미널을 켜고 `service netdata stop`를 입력하십시오. 173 | - Netdata를 **restart** 하기 위해, 터미널을 켜고 `service netdata restart`를 입력하십시오. 174 | 175 | `service` 명령는 시스템 기반의 Netdata를 시작 또는 중지하는 시스템의 기본 방법을 사용하는 래퍼 스크립트입니다. 그러나 이러한 명령 중 하나라도 실패하면 `systemd` 혹은 `init.d` 명령어를 사용해보십시오. 176 | 177 | - **systemd**: `systemctl start netdata`, `systemctl stop netdata`, `systemctl restart netdata` 178 | - **init.d**: `/etc/init.d/netdata start`, `/etc/init.d/netdata stop`, `/etc/init.d/netdata restart` 179 | 180 | ## 이후에 해야할 것은? 181 | 182 | `netdata.conf` 설정을 마치고, 경보를 수정하고, 성능 상 문제 해결의 기본을 배우고, **My nodes** 메뉴에 모든 시스템을 올리면 본격적으로 Netdata를 시작할 준비를 마쳤습니다. 183 | 184 | 아래에서 더 고급 기능과 설정을 확인해보세요. 185 | 186 | - [streaming](../streaming)을 이용해 다중의 시스템에서 Netdata 측정치를 중앙 집중화 해보세요. 187 | - [backends](../backends)을 통해 시계열 데이터베이스에 Netdata 지표를 장기간 저장해보세요. 188 | - Netdata를 [Nginx proxy with SSL](Running-behind-nginx.md) 뒤에 배치시키면 보안을 향상시킬 수 있습니다. 189 | 190 | 혹은 [Netdata core](../CONTRIBUTING.md)나 Netdata의 [documentation](../docs/contributing/contributing-documentation.md)!에 기여하는 법을 더 알아보세요! 191 | 192 | [![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)](<>) 193 | -------------------------------------------------------------------------------- /zh/packaging/installer/README.md: -------------------------------------------------------------------------------- 1 | # 安装Netdata 2 | 3 | Netdata是一个**服务器状态监控显示器**。它可以在所有的系统上安装和运行，包括**物理**和**虚拟**服务器，**Docker容器**，甚至是**物联网（IoT）**中。 4 | 5 | 安装Netdata的最佳方法是脚本安装。我们的**自动安装程序**将安装任何需要的系统软件包，并在您的系统上编译Netdata。 6 | 7 | !!! 注意 8 | 您可以找到由第三方分发的Netdata软件安装包。但是在大多数情况下，这些安装包太旧或不完整。因此，我们强烈建议您按照本说明来安装Netdata。 9 |      **我们正在努力为所有的Linux发行版提供Netdata的二进制包。** 敬请期待      10 | 11 | ## Installation 12 | 13 | 1. [自动安装](#自动安装)，从源代码中安装， **这是默认的安装方法** 14 | 2. [在64位的Linux上安装预构建的静态二进制文件](#linux-64bit-pre-built-static-binary) 15 | 3. [在Docker容器中运行Netdata](#run-netdata-in-a-docker-container) 16 | 4. [手动安装](#install-netdata-on-linux-manually) 17 | 5. [在FreeBSD系统上安装](#freebsd) 18 | 6. [在pfSense系统上安装](#pfsense) 19 | 7. [在FreeNAS Corral中启用](#freenas) 20 | 8. [在macOS (OS X)上安装](#macos) 21 | 9. [Install on a Kubernetes cluster](https://github.com/netdata/helmchart#netdata-helm-chart-for-kubernetes-deployments) 22 | 10. [Install using binary packages](#binary-packages) 23 | 24 | 另请参阅ASUSTOR NAS，OpenWRT，ReadyNAS等的Netdata软件包维护者列表（它应该在../maintainers）。 25 | 26 | --- 27 | 28 | ## 自动安装 29 | ## Automatic one-line installation script 30 | 31 | > 这种方法在**所有的Linux发行版上都是自动的**。 在首次安装Netdata之前，FreeBSD和MacOS系统需要提前做一些准备工作。有关详细信息，请查看[FreeBSD](#freebsd)和[MacOS](#macos)部分。 32 | 33 | 要从源代码中安装Netdata并使其自动保持最新，请运行以下命令： 34 | 35 | ```bash 36 | bash <(curl -Ss https://my-netdata.io/kickstart.sh) 37 | ``` 38 | 39 | *（无须使用`sudo`命令头，它会根据需要自动执行）* 40 | 41 | ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.requests_per_url&options=unaligned&dimensions=kickstart&group=sum&after=-3600&label=last+hour&units=installations&value_color=orange&precision=0) ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.requests_per_url&options=unaligned&dimensions=kickstart&group=sum&after=-86400&label=today&units=installations&precision=0) 42 | 43 |
单击以获取更多信息 44 | 45 |  
46 | Verify the integrity of the script with this: 47 | 48 | ```bash 49 | [ "b66c99c065abe1cf104c11236d4e8747" = "$(curl -Ss https://my-netdata.io/kickstart.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID" 50 | ``` 51 | *It should print `OK, VALID` if the script is the one we ship.* 52 | 53 | The `kickstart.sh` script: 54 | 55 | - detects the Linux distro and **installs the required system packages** for building Netdata (will ask for confirmation) 56 | - downloads the latest Netdata source tree to `/usr/src/netdata.git`. 57 | - installs Netdata by running `./netdata-installer.sh` from the source tree. 58 | - installs `netdata-updater.sh` to `cron.daily`, so your Netdata installation will be updated daily (you will get a message from cron only if the update fails). 59 | - For QA purposes, this installation method lets us know if it succeed or failed. 60 | 61 | The `kickstart.sh` script passes all its parameters to `netdata-installer.sh`, so you can add more parameters to change the installation directory, enable/disable plugins, etc (check below). 62 | 63 | For automated installs, append a space + `--dont-wait` to the command line. You can also append `--dont-start-it` to prevent the installer from starting Netdata. Example: 64 | 65 | ```bash 66 | bash <(curl -Ss https://my-netdata.io/kickstart.sh) --dont-wait --dont-start-it 67 | ``` 68 | 69 |
 
70 | 71 | 当你安装完成，请前往：[开始使用](../../docs/getting-started.md) 72 | 73 | --- 74 | 75 | ## 使用Linux 64的预构建静态二进制文件安装 76 | ## Linux 64bit pre-built static binary 77 | 78 | 您可以在任何Intel/AMD平台上的64位Linux系统上使用预编译静态二进制文件安装Netdata 79 | （即使是那些没有包管理器的系统，也可以使用这一方法来安装，如CoreOS，CirrOS，busybox等）。 80 | 您还可以在具有损坏或不受支持的包管理器的系统上使用这些程序包。 81 | 82 | 要在Linux的发行版上使用二进制包来安装Netdata，对于** Intel/AMD 64位 **的服务器来说，请运行以下命令： 83 | 84 | 85 | ```bash 86 | bash <(curl -Ss https://my-netdata.io/kickstart-static64.sh) 87 | ``` 88 | 89 | *(没用必要使用`sudo`这个命令头，它会根据需要自动执行；如果服务器没有安装`bash`，请参阅下面的说明：如何在没有`bash`的情况下运行安装程序）* 90 | 91 | ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.requests_per_url&options=unaligned&dimensions=kickstart64&group=sum&after=-3600&label=last+hour&units=installations&value_color=orange&precision=0) ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.requests_per_url&options=unaligned&dimensions=kickstart64&group=sum&after=-86400&label=today&units=installations&precision=0) 92 | 93 | > The static builds install Netdata at **`/opt/netdata`** 94 | 95 |
单击以获取更多信息 96 | 97 |  
98 | Verify the integrity of the script with this: 99 | 100 | ```bash 101 | [ "8e6df9b6f6cc7de0d73f6e5e51a3c8c2" = "$(curl -Ss https://my-netdata.io/kickstart-static64.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, 102 | INVALID" 103 | ``` 104 | 105 | *It should print `OK, VALID` if the script is the one we ship.* 106 | 107 | For automated installs, append a space + `--dont-wait` to the command line. You can also append `--dont-start-it` to prevent the installer from starting Netdata. 108 | 109 | Example: 110 | 111 | ```bash 112 | 113 | bash <(curl -Ss https://my-netdata.io/kickstart-static64.sh) --dont-wait --dont-start-it 114 | 115 | ``` 116 | 117 | If your shell fails to handle the above one liner, do this: 118 | 119 | ```bash 120 | # download the script with curl 121 | curl https://my-netdata.io/kickstart-static64.sh >/tmp/kickstart-static64.sh 122 | 123 | # or, download the script with wget 124 | wget -O /tmp/kickstart-static64.sh https://my-netdata.io/kickstart-static64.sh 125 | 126 | # run the downloaded script (any sh is fine, no need for bash) 127 | sh /tmp/kickstart-static64.sh 128 | ``` 129 | 130 | - The static binary files are kept in repo [binary-packages](https://github.com/netdata/binary-packages). You can download any of the `.run` files, and run it. These files are self-extracting shell scripts built with [makeself](https://github.com/megastep/makeself). 131 | - The target system does **not** need to have bash installed. 132 | - The same files can be used for updates too. 133 | - For QA purposes, this installation method lets us know if it succeed or failed. 134 | 135 |
 
136 | 137 | 当你安装完成，请前往：[开始使用](../../docs/getting-started.md) 138 | 139 | --- 140 | 141 | ## 在Docker容器上运行Netdata 142 | ## Run netdata in a docker container 143 | 144 | 你可以[在Docker上安装Netdata](../docker/#install-netdata-with-docker). 145 | 146 | --- 147 | 148 | ## 在Linux系统中手动安装Netdata 149 | ## Install netdata on Linux manually 150 | 151 | 要安装最新的Netdata git版本，请按照以下两个步骤操作： 152 | 153 | 1. [为你的系统作准备](#为你的系统做准备) 154 | 155 | 在你的系统中安装Netdata所需的软件包 156 | 157 | 2. [安装Netdata](#install-netdata) 158 | 159 | 下载并安装Netdata。您还可以同样的方法来更新Netdata。 160 | 161 | --- 162 | 163 | ### 为你的系统做准备 164 | 165 | 试试我们的新版安装程序（不要求为root用户）。它会尝试查找已在系统上安装的软件包以编译和运行Netdata。这个程序支持2010年后发布的大多数Linux发行版（如下）： 166 | 167 | - **Alpine** Linux及其衍生产品（在使用安装程序之前必须自己安装`bash`） 168 | - **Arch** Linux及其衍生产品 169 | - **Gentoo** Linux及其衍生产品 170 | - **Debian** Linux及其衍生产品（包括 **Ubuntu**, **Mint**） 171 | - **Fedora** 和它的衍生产品 （包括 **Red Hat Enterprise Linux**, **CentOS**, **Amazon Machine Image**） 172 | - **SuSe** Linux及其衍生产品（包括 **openSuSe**） 173 | - **SLE12** 必须让您的系统在Suse客户中心注册或拥有DVD。请参阅[#1162]（https://github.com/netdata/netdata/issues/1162） 174 | 175 | 请注意：安装包是**基本的Netdata安装**（系统监控和许多应用程序监控，它没有`mysql` /`mariadb`，`postgres`，`named`，`硬件监控`和`SNMP`），请执行以下命令： 176 | 177 | ```sh 178 | curl -Ss 'https://raw.githubusercontent.com/netdata/netdata-demo-site/master/install-required-packages.sh' >/tmp/kickstart.sh && bash /tmp/kickstart.sh -i netdata 179 | ``` 180 | 181 | 如果你想安装**Netdata的完整版本**，请执行以下命令： 182 | 183 | ```sh 184 | curl -Ss 'https://raw.githubusercontent.com/netdata/netdata-demo-site/master/install-required-packages.sh' >/tmp/kickstart.sh && bash /tmp/kickstart.sh -i netdata-all 185 | ``` 186 | 187 | 如果上述内容对您不起作用，请 [提问](https://github.com/netdata/netdata/issues/new?title=packages%20installer%20failed&labels=installation%20help&body=The%20experimental%20packages%20installer%20failed.%0A%0AThis%20is%20what%20it%20says:%0A%0A%60%60%60txt%0A%0Aplease%20paste%20your%20screen%20here%0A%0A%60%60%60) 请附上您在屏幕上看到提示消息。我们正试图让Netdata在任何地方都能运行（这也是提问成功与否 [例子](https://github.com/netdata/netdata/issues/2054) 的原因)。 188 | 189 | --- 190 | 191 | 如何在不同的系统中手动完成准备工作？ 192 | 193 | ```sh 194 | # 在Debian/Ubuntu系统中 195 | apt-get install zlib1g-dev uuid-dev libmnl-dev gcc make git autoconf autoconf-archive autogen automake pkg-config curl 196 | 197 | # 在Fedora系统中 198 | dnf install zlib-devel libuuid-devel libmnl-devel gcc make git autoconf autoconf-archive autogen automake pkgconfig curl findutils 199 | 200 | # 在CentOS/Red Hat Enterprise Linux系统中 201 | yum install autoconf automake curl gcc git libmnl-devel libuuid-devel lm_sensors make MySQL-python nc pkgconfig python python-psycopg2 PyYAML zlib-devel 202 | 203 | ``` 204 | 205 | 请注意，在RHEL/CentOS系统中，您还可能需要[EPEL](http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/). 206 | 207 | 编译Netdata后，要运行它，需要以下软件包（它们应该已经使用上述命令安装）： 208 | 209 | 软件包名|描述 210 | :-----:|----------- 211 | `libuuid`|用于GUID管理的`util-linux`一部分 212 | `zlib`|Netdata Web内部服务器的Gzip压缩软件包 213 | 214 | *如果没用这些软件包，Netdata将无法启动* 215 | 216 | Netdata插件和Netdata的其他一些方面可以在安装时启用或禁用（它们是可选的）： 217 | 218 | 软件包名|描述 219 | :-----:|----------- 220 | `bash`|用于Shell插件和**警报通知** 221 | `curl`|用于Shell插件和**警报通知** 222 | `iproute` 或 `iproute2`|用于监控** Linux流量QoS **
如果`iproute`提示不可用或已过时，请使用`iproute2` 223 | `python`|这对于大多数外部插件来说都是必须的 224 | `python-yaml`|用于监控**beanstalkd** 225 | `python-beanstalkc`|用于监控**beanstalkd** 226 | `python-dnspython`|用于监控DNS的查询时间 227 | `python-ipaddress`|用于监控** DHCPd **
只有Python V2才需要此软件包。Python V3已经嵌入了此功能 228 | `python-mysqldb`
或
`python-pymysql`|用于监控**mysql**或**mariadb** 数据库
`python-mysqldb`会运行地更快，所以它是首选 229 | `python-psycopg2`|用于监控**postgresql**数据库 230 | `python-pymongo`|用于监控**mongodb**数据库 231 | `nodejs`|用于`node.js`插件来监控**named**和**SNMP**设备 232 | `lm-sensors`|用于监控**hardware sensors** 233 | `libmnl`|用于收集netfilter指标 234 | `netcat`|用于从远程系统中收集指标的Shell插件 235 | 236 | *如果安装了上述软件包，Netdata功能将大大增加，但如果没有它们，Netdata仍然可以正常工作。* 237 | 238 | --- 239 | 240 | ### 安装Netdata 241 | ### Install Netdata 242 | 243 | 运行以下命令来安装并运行Netdata： 244 | 245 | ```sh 246 | 247 | # 下载Netdata（同时创建netdata目录） 248 | git clone https://github.com/netdata/netdata.git --depth=100 249 | cd netdata 250 | 251 | # 运行具有root权限的脚本来编译安装Netdata并启动它 252 | ./netdata-installer.sh 253 | 254 | ``` 255 | 256 | * 如果您不想安装完成后启动Netdata，请添加`--dont-start-it`参数 257 | 258 | * 如果您不想在默认目录中安装Netdata，请按照这样来输入命令：`./netdata-installer.sh --install /opt`。这条命令会把Netdata安装在`/opt/netdata`中。 259 | 260 | 当安装完成，文件`/etc/netdata/netdata.conf`会被创建（如果您更改了安装目录，该配置文件也会出现在您指定的目录中）。 261 | 262 | 您可以编辑此文件以更改设置首选项。一个最常见被调整选项是`history`，它控制Netdata将使用的内存数据库大小。其默认情况下应为“3600”秒（图表中一小时的数据），这使得Netdata将使用大约10-15MB的RAM（取决于系统检测到的图表数量）。请检查**[内存要求]**。 263 | 264 | 要应用您所做的更改，您必须重新启动Netdata。 265 | 266 | --- 267 | 268 | ## 其他系统 269 | 270 | 271 | 272 | ##### FreeBSD 273 | 274 | 您可以从ports或packages中安装Netdata。 275 | 276 | 此命令会在FreeBSD上安装最新版的Netdata： 277 | 278 | ```sh 279 | # 安装依赖 280 | pkg install bash e2fsprogs-libuuid git curl autoconf automake pkgconf pidof 281 | 282 | # 下载Netdata 283 | git clone https://github.com/netdata/netdata.git --depth=100 284 | 285 | # 把Netdata安装在/opt/netdata中 286 | cd netdata 287 | ./netdata-installer.sh --install /opt 288 | ``` 289 | 290 | ##### pfSense 291 | 要在pfSense上安装Netdata，请运行以下命令（在Shell中或在pfSense Web界面中的Diagnostics/Command Prompt）。 292 | 293 | 根据您的环境更改平台（i386/amd64等）和FreeBSD版本（10/11等），并根据FreeSBD存储库中的最新版本更改Netdata版本（示例中为1.10.0）： 294 | 295 | 注意：前三个软件包是从pfSense存储库中下载的，用于保持与pfSense系统的兼容性，Netdata是从FreeBSD的存储库中下载的。 296 | ``` 297 | pkg install pkgconf 298 | pkg install bash 299 | pkg install e2fsprogs-libuuid 300 | pkg add http://pkg.freebsd.org/FreeBSD:11:amd64/latest/All/netdata-1.11.0.txz 301 | ``` 302 | 要运行Netdata，请手动运行这条命令：`service netdata onestart` 303 | 304 | 要把Netdata添加为启动项，请在pfSense Web界面中添加`service netdata start`为Shellcmd（在**Services/Shellcmd**下，您需要事先在**System/Package Manager/Available Packages**下安装）。 305 | Shellcmd Type应设置为`Shellcmd`。 306 | ![](https://user-images.githubusercontent.com/36808164/36930790-4db3aa84-1f0d-11e8-8752-cdc08bb7207c.png) 307 | 您可以在这里找到更多信息： https://doc.pfsense.org/index.php/Installing_FreeBSD_Packages ，通过命令行和脚本来实现相同的功能。 308 | 如果您在pfSense 2.3或更早版本中遇到`/usr/bin/install` absense问题，请更新pfSense或使用解决方法：[https://redmine.pfsense.org/issues/6643](https://redmine.pfsense.org/issues/6643) 309 | 310 | ##### FreeNAS 311 | 在FreeNAS-Corral-RELEASE（>=10.0.3）上Netdata已经被预先安装。 312 | 313 | 要使用Netdata，需要启用该服务并从FreeNAS中启动 **[CLI](https://github.com/freenas/cli)**. 314 | 315 | 启用Netdata服务： 316 | ``` 317 | service netdata config set enable=true 318 | ``` 319 | 320 | 运行Netdata服务： 321 | ``` 322 | service netdata start 323 | ``` 324 | 325 | ##### macOS 326 | 327 | macOS上的Netdata仅有一部分监控图表，但外部插件是被允许的。 328 | 329 | 您可以使用[Homebrew](https://brew.sh/)来安装Netdata 330 | 331 | ```sh 332 | brew install netdata 333 | ``` 334 | 335 | 或者从源中安装 336 | 337 | ```sh 338 | # 安装Xcode命令行工具 339 | xcode-select --install 340 | ``` 341 | 在软件更新弹出窗口中点击`Install`，然后 342 | ```sh 343 | # 安装HomeBrew包管理器 344 | /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" 345 | 346 | # 安装依赖 347 | brew install ossp-uuid autoconf automake pkg-config 348 | 349 | # 下载Netdata 350 | git clone https://github.com/netdata/netdata.git --depth=100 351 | 352 | # 把Netdata安装在/usr/local/netdata中 353 | cd netdata 354 | sudo ./netdata-installer.sh --install /usr/local 355 | ``` 356 | 357 | 安装程序还会自动配置plist以在Mac启动时自动启动Netdata。 358 | 359 | ##### Alpine 3.x 360 | 361 | 执行以下命令在Alpine Linux 3.x中安装Netdata： 362 | 363 | ``` 364 | # 安装依赖 365 | apk add alpine-sdk bash curl zlib-dev util-linux-dev libmnl-dev gcc make git autoconf automake pkgconfig python logrotate 366 | 367 | # 如果您打算运行node.js Netdata插件，请执行此命令，否则请跳过 368 | apk add nodejs 369 | 370 | # 下载Netdata（同时创建Netdata更目录） 371 | git clone https://github.com/netdata/netdata.git --depth=100 372 | cd netdata 373 | 374 | 375 | # 编译，安装，运行Netdata 376 | ./netdata-installer.sh 377 | 378 | 379 | # 将Netdata添加为自启项 380 | echo -e "#!/usr/bin/env bash\n/usr/sbin/netdata" >/etc/local.d/netdata.start 381 | chmod 755 /etc/local.d/netdata.start 382 | 383 | # 使Netdata在关机时自动停止 384 | echo -e "#!/usr/bin/env bash\nkillall netdata" >/etc/local.d/netdata.stop 385 | chmod 755 /etc/local.d/netdata.stop 386 | 387 | # 启用本地服务以自动启动 388 | rc-update add local 389 | ``` 390 | 391 | ##### Synology 392 | 393 | 该文档以前建议从Synology社区源中安装Debian Chroot包，然后在chroot中运行Netdata。然而，这不起作用，因为chroot环境无法访问`/proc`，所以Netdata几乎无法获取到任何指标。另外，[问题](https://github.com/SynoCommunity/spksrc/issues/2758)，在2018/06/24时被打开，表示Debian Chroot软件包不适用于DSM5以上，并且可能损坏系统库使NAS无法正常启动。 394 | 395 | 好消息是，如果您的NAS是amd64架构的，那么64位静态安装程序可以地正常工作。它会将内容安装到`/opt/netdata`中，以便将来删除地更加安全和简单。 396 | 397 | 首次安装Netdata时，它将以_root_用户运行。您可能不想这样做，您或许想使用_netdata_用户来运行，这需要一些额外的工作： 398 | 399 | 1. 通过Synology用户界面创建一个用户组`netdata`。但请不要给它任何权限。 400 | 2. 通过Synology用户界面创建用户`netdata`。但请让它无法访问任何内容和随机密码。请将此用户分配给`netdata`用户组。Netdata将会在运行时为这个用户提供帮助。 401 | 3. 更改以下目录的所有权（执行以下命令），如[Netdata安全](../../docs/netdata-security.md#security-design)中所配置的那样： 402 | 403 | ``` 404 | $ chown -R root:netdata /opt/netdata/usr/share/netdata 405 | $ chown -R netdata:netdata /opt/netdata/var/lib/netdata /opt/netdata/var/cache/netdata 406 | $ chown -R netdata:root /opt/netdata/var/log/netdata 407 | ``` 408 | 409 | 此外，从2018/06/24起，Netdata安装程序将无法识别DSM为一个操作系统，所以安装程序无法安装任何init脚本。因此，您必须手动执行这些操作： 410 | 411 | 1. 将[文件](https://gist.github.com/oskapt/055d474d7bfef32c49469c1b53e8225f)添加到`/etc/rc.netdata`中。然后用`chmod 0755 /etc/rc.netdata`命令给予它权限。 412 | 2. 编辑`/etc/rc.local`并在末尾添加一行调用：`/etc/rc.netdata`，使其在启动时可以自动启动： 413 | 414 | ``` 415 | # 使Netdata在开机时自动启动 416 | [ -x /etc/rc.netdata ] && /etc/rc.netdata start 417 | ``` 418 | 译者注：请以英语原版为准 419 | 420 | 421 | ## Binary Packages 422 | ![](https://raw.githubusercontent.com/netdata/netdata/master/web/gui/images/packaging-beta-tag.svg?sanitize=true) 423 | 424 | We provide our own flavour of binary packages for the most common operating systems that comply with .RPM and .DEB packaging formats. 425 | 426 | We have currently released packages following the .RPM format with version [1.16.0](https://github.com/netdata/netdata/releases/tag/v1.16.0). 427 | We have planned to release packages following the .DEB format with version [1.17.0](https://github.com/netdata/netdata/releases/tag/v1.17.0). 428 | Early adopters may experiment with our .DEB formatted packages using our nightly releases. Our current packaging infrastructure provider is [Package Cloud](https://packagecloud.io). 429 | 430 | Netdata is committed to support installation of our solution to all operating systems. This is a constant battle for Netdata, as we strive to automate and make things easier for our users. For the operating system support matrix, please visit our [distributions](../../packaging/DISTRIBUTIONS.md) support page. 431 | 432 | We provide two separate repositories, one for our stable releases and one for our nightly releases. 433 | 434 | 1. Stable releases: Our stable production releases are hosted in [netdata/netdata](https://packagecloud.io/netdata/netdata) repository of package cloud 435 | 2. Nightly releases: Our latest releases are hosted in [netdata/netdata-edge](https://packagecloud.io/netdata/netdata-edge) repository of package cloud 436 | 437 | Visit the repository pages and follow the quick set-up instructions to get started. 438 | 439 | 440 | ## Nightly vs. stable releases 441 | 442 | The Netdata team maintains two releases of the Netdata agent: **nightly** and **stable**. By default, Netdata's installation scripts will give you **automatic, nightly** updates, as that is our recommended configuration. 443 | 444 | **Nightly**: We create nightly builds every 24 hours. They contain fully-tested code that fixes bugs or security flaws, or introduces new features to Netdata. Every nightly release is a candidate for then becoming a stable release—when we're ready, we simply change the release tags on GitHub. That means nightly releases are stable and proven to function correctly in the vast majority of Netdata use cases. That's why nightly is the *best choice for most Netdata users*. 445 | 446 | **Stable**: We create stable releases whenever we believe the code has reached a major milestone. Most often, stable releases correlate with the introduction of new, significant features. Stable releases might be a better choice for those who run Netdata in *mission-critical production systems*, as updates will come more infrequently, and only after the community helps fix any bugs that might have been introduced in previous releases. 447 | 448 | **Pros of using nightly releases:** 449 | 450 | - Get the latest features and bugfixes as soon as they're available 451 | - Receive security-related fixes immediately 452 | - Use stable, fully-tested code that's always improving 453 | - Leverage the same Netdata experience our community is using 454 | 455 | **Pros of using stable releases:** 456 | 457 | - Protect yourself from the rare instance when major bugs slip through our testing and negatively affect a Netdata installation 458 | - Retain more control over the Netdata version you use 459 | 460 | 461 | ## Automatic updates 462 | 463 | By default, Netdata's installation scripts enable automatic updates for both nightly and stable release channels. 464 | 465 | If you would prefer to manually update your Netdata agent, you can disable automatic updates by using the `--no-updates` option when you install or update Netdata using the [one-line installation script](#automatic-one-line-installation-script). 466 | 467 | ```bash 468 | bash <(curl -Ss https://my-netdata.io/kickstart.sh) --no-updates 469 | ``` 470 | 471 | With automatic updates disabled, you can choose exactly when and how you [update Netdata](UPDATE.md). 472 | 473 | [![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%2Finstaller%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 474 | -------------------------------------------------------------------------------- /zh/docs/terms-of-use.md: -------------------------------------------------------------------------------- 1 | # Terms of use 2 | 3 | Netdata Terms of Use for the sites https://my-netdata.io and https://netdata.cloud and their subdomains. For the Netdata agent and the included redistributed software terms of use, refer to [Redistributed software](../REDISTRIBUTED.md) 4 | 5 | Effective as of 25 May 2018 6 | 7 | ## 1. General Information Regarding These Terms of Use 8 | 9 | Master terms: Welcome, and thank you for your interest in Netdata (“Netdata,” “ND,” “we,” “our,” or “us”). Unless otherwise noted on a particular site or service, these master terms of use (“Master Terms”) apply to your use of all of the websites that Netdata Corporation operates. These include https://my-netdata.io and https://netdata.cloud, together with all other subdomains thereof, (collectively, the “Websites”). The Master Terms also apply to all products, information, and services provided through the Websites, such as the NDID Login Service. 10 | 11 | Additional terms: In addition to the Master Terms, your use of any Services may also be subject to specific terms applicable to a particular Service (“Additional Terms”). If there is any conflict between the Additional Terms and the Master Terms, then the Additional Terms apply in relation to the relevant Service. 12 | 13 | Collectively, the Terms: The Master Terms, together with any Additional Terms, form a binding legal agreement between you and Netdata in relation to your use of the Services. Collectively, this legal agreement is referred to below as the “Terms.” 14 | 15 | Human-readable summary of Sec 1: These terms, together with any special terms for particular websites, create a contract between you and Netdata. The contract governs your use of all websites operated by Netdata, unless a particular website indicates otherwise. These human-readable summaries of each section are not part of the contract, but are intended to help you understand its terms. 16 | 17 | ## 2. Your Agreement to the Terms 18 | 19 | BY ACCESSING OR USING ANY OF THE SERVICES, YOU ACKNOWLEDGE THAT YOU HAVE READ, UNDERSTOOD, AND AGREED TO BE BOUND BY THE TERMS. By accessing or using any Services you also represent that you have the legal authority to accept the Terms on behalf of yourself and any party you represent in connection with your use of any Services. If you do not agree to the Terms, you are not authorized to use any Services. If you are an individual who is entering into these Terms on behalf of an entity, you represent and warrant that you have the power to bind that entity, and you hereby agree on that entity’s behalf to be bound by these Terms, with the terms “you,” and “your” applying to you, that entity, and other users accessing the Services on behalf of that entity. 20 | 21 | Human-readable summary of Sec 2: Please read these terms and only use our sites and services if you agree to them. 22 | 23 | ## 3. Changes to the Terms 24 | 25 | From time to time, Netdata may change, remove, or add to the Terms, and reserves the right to do so in its discretion. In that case, we will post updated Terms and indicate the date of revision. If we feel the modifications are material, we will make reasonable efforts to post a prominent notice on the relevant Website(s) and notify those of you with a current NDID Login Service account via email. All new and/or revised Terms take effect immediately and apply to your use of the Services from that date on, except that material changes will take effect 30 days after the change is made and identified as material. Your continued use of any Services after new and/or revised Terms are effective indicates that you have read, understood, and agreed to those Terms. 26 | 27 | Human-readable summary of Sec 3: These terms may change. When the changes are important, we will put a notice on the website. If you continue to use the sites after the changes are made, you agree to the changes. 28 | 29 | ## 4. No Legal Advice 30 | 31 | Netdata is not a law firm, does not provide legal advice, and is not a substitute for a law firm. Sending us an email or using any of the Services, including the licenses, public domain tools, and choosers, does not constitute legal advice or create an attorney-client relationship. 32 | 33 | Human-readable summary of Sec 4: Some of us are lawyers, but we aren’t your lawyer. Please consult your own attorney if you need legal advice. 34 | 35 | ## 5. Content Available through the Services 36 | 37 | Provided as-is: You acknowledge that Netdata does not make any representations or warranties about the material, data, and information, such as data files, text, computer software, code, music, audio files or other sounds, photographs, videos, or other images (collectively, the “Content”) which you may have access to as part of, or through your use of, the Services. Under no circumstances is Netdata liable in any way for any Content, including, but not limited to: any infringing Content, any errors or omissions in Content, or for any loss or damage of any kind incurred as a result of the use of any Content posted, transmitted, linked from, or otherwise accessible through or made available via the Services. You understand that by using the Services, you may be exposed to Content that is offensive, indecent, or objectionable. 38 | 39 | You agree that you are solely responsible for your reuse of Content made available through the Services, including providing proper attribution. You should review the terms of the applicable license before you use the Content so that you know what you can and cannot do. 40 | 41 | Licensing: ND-Owned Content: Other than the text of Netdata licenses, CC licenses, and other legal tools and the text of the deeds for all legal tools (all of which are made available under the CC Public Domain Dedication), Netdata trademarks (subject to the Trademark Policy), and the software code, all Content on the Websites is licensed under the Creative Commons Attribution 4.0 license, unless otherwise marked. See the ND Policies page for more information. 42 | 43 | ND-Owned Code: All of CC’s software code is free software; please check our code repository for the specific license on software you want to reuse. 44 | 45 | Search Tools: On some of its Websites, Netdata provides website search tools, including ND Search, which return Content based on any information our search tools are able to locate and interpret. Those search tools may return Content that is not ND licensed, and you should independently verify the terms of the license attached to any Content you intend to use. 46 | 47 | Human-readable summary of Sec 5: We try our best to have useful information on our sites, but we cannot promise that everything is accurate or appropriate for your situation. Content on the site is licensed under CC BY 4.0 unless it says it is available under different terms. If you find content through a link on our websites, be sure to check the license terms before using it. 48 | 49 | ## 6. Content Supplied by You 50 | 51 | Your responsibility: You represent, warrant, and agree that no Content posted or otherwise shared by you on or through any of the Services (“Your Content”), violates or infringes upon the rights of any third party, including copyright, trademark, privacy, publicity, or other personal or proprietary rights, breaches or conflicts with any obligation, such as a confidentiality obligation, or contains libelous, defamatory, or otherwise unlawful material. 52 | 53 | Licensing Your Content: You retain any copyright that you may have in Your Content. You hereby agree that Your Content: (a) is hereby licensed under the CC Attribution 4.0 License and may be used under the terms of that license or any later version of a CC Attribution License, or (b) is in the public domain (such as Content that is not copyrightable or Content you make available under CC0), or (c) if not owned by you, (i) is available under a CC Attribution 4.0 License or (ii) is a media file that is available under any CC license or that you are authorized by law to post or share through any of the Services, such as under the fair use doctrine, and that is prominently marked as being subject to third party copyright. All of Your Content must be appropriately marked with licensing (or other permission status such as fair use) and attribution information. 54 | 55 | Removal: Netdata may, but is not obligated to, review Your Content and may delete or remove Your Content (without notice) from any of the Services in its sole discretion. Removal of any of Your Content from the Services (by you or Netdata) does not impact any rights you granted in Your Content under the terms of a Netdata license. 56 | 57 | Human-readable summary of Sec 6: We do not take any ownership of your content when you post it on our sites. If you post content you own, you agree it can be used under the terms of CC BY 4.0 or any future version of that license. If you do not own the content, then you should not post it unless it is in the public domain or licensed CC BY 4.0, except that you may also post pictures and videos if you are authorized to use them under law (e.g. fair use) or if they are available under any CC license. You must note that information on the file when you upload it. You are responsible for any content you upload to our sites. 58 | 59 | ## 7. Prohibited Conduct 60 | 61 | You agree not to engage in any of the following activities: 62 | 63 | ### 1. Violating laws and rights: 64 | 65 | You may not (a) use any Service for any illegal purpose or in violation of any local, state, national, or international laws, (b) violate or encourage others to violate any right of or obligation to a third party, including by infringing, misappropriating, or violating intellectual property, confidentiality, or privacy rights. 66 | 67 | ### 2. Solicitation: 68 | 69 | You may not use the Services or any information provided through the Services for the transmission of advertising or promotional materials, including junk mail, spam, chain letters, pyramid schemes, or any other form of unsolicited or unwelcome solicitation. 70 | 71 | ### 3. Disruption: 72 | 73 | You may not use the Services in any manner that could disable, overburden, damage, or impair the Services, or interfere with any other party’s use and enjoyment of the Services; including by (a) uploading or otherwise disseminating any virus, adware, spyware, worm or other malicious code, or (b) interfering with or disrupting any network, equipment, or server connected to or used to provide any of the Services, or violating any regulation, policy, or procedure of any network, equipment, or server. 74 | 75 | ### 4. Harming others: 76 | 77 | You may not post or transmit Content on or through the Services that is harmful, offensive, obscene, abusive, invasive of privacy, defamatory, hateful or otherwise discriminatory, false or misleading, or incites an illegal act; 78 | You may not intimidate or harass another through the Services; and, you may not post or transmit any personally identifiable information about persons under 13 years of age on or through the Services. 79 | 80 | ### 5. Impersonation or unauthorized access: 81 | 82 | You may not impersonate another person or entity, or misrepresent your affiliation with a person or entity when using the Services; 83 | You may not use or attempt to use another’s account or personal information without authorization; and 84 | You may not attempt to gain unauthorized access to the Services, or the computer systems or networks connected to the Services, through hacking password mining or any other means. 85 | 86 | Human-readable summary of Sec 7: Play nice. Be yourself. Don’t break the law or be disruptive. 87 | 88 | ## 8. DISCLAIMER OF WARRANTIES 89 | 90 | TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, NETDATA OFFERS THE SERVICES (INCLUDING ALL CONTENT AVAILABLE ON OR THROUGH THE SERVICES) AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE SERVICES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. NETDATA DOES NOT WARRANT THAT THE FUNCTIONS OF THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, THAT CONTENT MADE AVAILABLE ON OR THROUGH THE SERVICES WILL BE ERROR-FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT ANY SERVERS USED BY ND ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. NETDATA DOES NOT WARRANT OR MAKE ANY REPRESENTATION REGARDING USE OF THE CONTENT AVAILABLE THROUGH THE SERVICES IN TERMS OF ACCURACY, RELIABILITY, OR OTHERWISE. 91 | 92 | Human-readable summary of Sec 8: ND does not make any guarantees about the sites, services, or content available on the sites. 93 | 94 | ## 9. LIMITATION OF LIABILITY 95 | 96 | TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL NETDATA BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY INCIDENTAL, DIRECT, INDIRECT, PUNITIVE, ACTUAL, CONSEQUENTIAL, SPECIAL, EXEMPLARY, OR OTHER DAMAGES, INCLUDING WITHOUT LIMITATION, LOSS OF REVENUE OR INCOME, LOST PROFITS, PAIN AND SUFFERING, EMOTIONAL DISTRESS, COST OF SUBSTITUTE GOODS OR SERVICES, OR SIMILAR DAMAGES SUFFERED OR INCURRED BY YOU OR ANY THIRD PARTY THAT ARISE IN CONNECTION WITH THE SERVICES (OR THE TERMINATION THEREOF FOR ANY REASON), EVEN IF NETDATA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 97 | 98 | TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, NETDATA IS NOT RESPONSIBLE OR LIABLE WHATSOEVER IN ANY MANNER FOR ANY CONTENT POSTED ON OR AVAILABLE THROUGH THE SERVICES (INCLUDING CLAIMS OF INFRINGEMENT RELATING TO THAT CONTENT), FOR YOUR USE OF THE SERVICES, OR FOR THE CONDUCT OF THIRD PARTIES ON OR THROUGH THE SERVICES. 99 | 100 | Certain jurisdictions do not permit the exclusion of certain warranties or limitation of liability for incidental or consequential damages, which means that some of the above limitations may not apply to you. IN THESE JURISDICTIONS, THE FOREGOING EXCLUSIONS AND LIMITATIONS WILL BE ENFORCED TO THE GREATEST EXTENT PERMITTED BY APPLICABLE LAW. 101 | 102 | Human-readable summary of Sec 9: ND is not responsible for the content on the sites, your use of our services, or for the conduct of others on our sites. 103 | 104 | ## 10. Indemnification 105 | 106 | To the extent authorized by law, you agree to indemnify and hold harmless Netdata, its employees, officers, directors, affiliates, and agents from and against any and all claims, losses, expenses, damages, and costs, including reasonable attorneys’ fees, resulting directly or indirectly from or arising out of (a) your violation of the Terms, (b) your use of any of the Services, and/or (c) the Content you make available on any of the Services. 107 | 108 | Human-readable summary of Sec 10: If something happens because you violate these terms, because of your use of the services, or because of the content you post on the sites, you agree to repay ND for the damage it causes. 109 | 110 | ## 11. Privacy Policy 111 | 112 | Netdata is committed to responsibly handling the information and data we collect through our Services in compliance with our Privacy Policy, which is incorporated by reference into these Master Terms. Please review the Privacy Policy so you are aware of how we collect and use your personal information. 113 | 114 | Human-readable summary of Sec 11: Please read our Privacy Policy. It is part of these terms, too. 115 | 116 | ## 12. Trademark Policy 117 | 118 | ND’s name, logos, icons, and other trademarks may only be used in accordance with our Trademark Policy, which is incorporated by reference into these Master Terms. Please review the Trademark Policy so you understand how ND’s trademarks may be used. 119 | 120 | Human-readable summary of Sec 12: Please read our Trademark Policy. It is part of these terms, too. 121 | 122 | ## 13. Copyright Complaints 123 | 124 | Netdata respects copyright, and we prohibit users of the Services from submitting, uploading, posting, or otherwise transmitting any Content on the Services that violates another person’s proprietary rights. 125 | 126 | To report allegedly infringing Content hosted on a website owned or controlled by ND, send a Notice of Infringing Materials to info@netdata.cloud. 127 | 128 | Please note that Netdata does not host the Content made available through ND Search. You should contact the web site or service hosting the Content to have it removed. 129 | 130 | Human-readable summary of Sec 13: Please let us know if you find infringing content on our websites. 131 | 132 | ## 14. Termination 133 | 134 | By Netdata: Netdata may modify, suspend, or terminate the operation of, or access to, all or any portion of the Services at any time for any reason. Additionally, your individual access to, and use of, the Services may be terminated by Netdata at any time and for any reason. 135 | 136 | By you: If you wish to terminate this agreement, you may immediately stop accessing or using the Services at any time. 137 | 138 | Automatic upon breach: Your right to access and use the Services (including use of your ND Login Service account) automatically upon your breach of any of the Terms. For the avoidance of doubt, termination of the Terms does not require you to remove or delete any reference to previously-applied ND legal tools from your own Content. 139 | 140 | Survival: The disclaimer of warranties, the limitation of liability, and the jurisdiction and applicable law provisions will survive any termination. The license grants applicable to Your Content are not impacted by the termination of the Terms and shall continue in effect subject to the terms of the applicable license. Your warranties and indemnification obligations will survive for one year after termination. 141 | 142 | Human-readable summary of Sec 14: If you violate these terms, you may no longer use our sites. 143 | 144 | ## 15. Miscellaneous Terms 145 | 146 | Choice of law: The Terms are governed by and construed by the laws of the State of Delaware in the United States, not including its choice of law rules. 147 | 148 | Dispute resolution: The parties agree that any disputes between Netdata and you concerning these Terms, and/or any of the Services may only brought in a federal or state court of competent jurisdiction sitting in the State of Delaware, and you hereby consent to the personal jurisdiction and venue of such court. 149 | 150 | If you are an authorized agent of a government or intergovernmental entity using the Services in your official capacity, including an authorized agent of the federal, state, or local government in the United States, and you are legally restricted from accepting the controlling law, jurisdiction, or venue clauses above, then those clauses do not apply to you. For any such U.S. federal government entities, these Terms and any action related thereto will be governed by the laws of the United States of America (without reference to conflict of laws) and, in the absence of federal law and to the extent permitted under federal law, the laws of the State of Delaware (excluding its choice of law rules). 151 | 152 | No waiver: Either party’s failure to insist on or enforce strict performance of any of the Terms will not be construed as a waiver of any provision or right. 153 | 154 | Severability: If any part of the Terms is held to be invalid or unenforceable by any law or regulation or final determination of a competent court or tribunal, that provision will be deemed severable and will not affect the validity and enforceability of the remaining provisions. 155 | 156 | No agency relationship: The parties agree that no joint venture, partnership, employment, or agency relationship exists between you and Netdata as a result of the Terms or from your use of any of the Services. 157 | 158 | Integration: These Master Terms and any applicable Additional Terms constitute the entire agreement between you and Netdata relating to this subject matter and supersede any and all prior communications and/or agreements between you and Netdata relating to access and use of the Services. 159 | 160 | Human-readable summary of Sec 15: If there is a lawsuit arising from these terms, it should be in Delaware and governed by Delaware law. We are glad you use our sites, but this agreement does not mean we are partners. 161 | 162 | [![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%2Fterms-of-use&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]() 163 | -------------------------------------------------------------------------------- /pt/packaging/installer/README.md: -------------------------------------------------------------------------------- 1 | # Installation 2 | 3 | Netdata é um **agente de monitoramento**. É projetado para ser instalado e rodar em todos os seus sistemas: servidores **físicos** e **virtuais**, **containers**, e até mesmo **IoT** (Internet das coisas). 4 | 5 | A melhor maneira de instalar o Netdata é diretamente pelo código-fonte. Nosso **instalador automático** irá instalar qualquer pacote necessário e compilar o Netdata diretamente no seu sistema. 6 | 7 | !!! Aviso 8 | Você pode encontrar os pacotes do Netdata distribuídos por terceiros. Em muitos casos, esses pacotes podem ser antigos ou está quebrados. Portanto, as maneiras sugeridas para instalar o Netdata estão descritas nessa página. 9 | 10 | 1. [Instalação automática de uma linha](#one-line-installation), instalação fácil a partir do código-fonte, **modo padrão** 11 | 2. [Instalação do binário estático pré-construído em qualquer Linux 64 bits](#linux-64bit-pre-built-static-binary) 12 | 3. [Executando Netdata em um container docker](#run-netdata-in-a-docker-container) 13 | 4. [Instalação manual, passo-a-passo](#install-netdata-on-linux-manually) 14 | 5. [Instalação no FreeBSD](#freebsd) 15 | 6. [Instalação no pfSense](#pfsense) 16 | 7. [Habilitando no FreeNAS Corral](#freenas) 17 | 8. [Instalação no macOS (OS X)](#macos) 18 | 9. [Instalação em um cluster Kubernetes](https://github.com/netdata/helmchart#netdata-helm-chart-for-kubernetes-deployments) 19 | 10. [Instalação usando pacotes binários](#binary-packages) 20 | 21 | Veja também a lista dos [mantenedores dos pacotes](../maintainers) para ASUSTOR NAS, OpenWRT, ReadyNAS, etc. 22 | 23 | Nota: A partir do Netdata v1.12, informaações anônimas de uso são coletadas por padrão e são enviadas ao Google Analytics. Para ler mais sobre quais informações são coletadas e como optar por não participar, acesse a [página de estatística anônima](../../docs/anonymous-statistics.md). 24 | 25 | --- 26 | 27 | ## Instalação automática de uma linha 28 | ## One-line installation 29 | 30 | ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.requests_per_url&options=unaligned&dimensions=kickstart&group=sum&after=-3600&label=last+hour&units=installations&value_color=orange&precision=0) ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.requests_per_url&options=unaligned&dimensions=kickstart&group=sum&after=-86400&label=today&units=installations&precision=0) 31 | 32 | Esse método é This method is **totalmente automático em todas as distribuições Linux**. FreeBSD e MacOS precisam de algumas preparações antes de instalar o Netdata pela primeira vez. Veja as seções [FreeBSD](#freebsd) e [MacOS](#macos) para mais informações. 33 | 34 | Para instalar o Netdata a partir do código-fonte, e mantê-lo atualizado com nossas **nightly releases** automaticamente, execute os seguntes passos: 35 | 36 | ```bash 37 | bash <(curl -Ss https://my-netdata.io/kickstart.sh) 38 | ``` 39 | 40 | !!! nota 41 | Não use `sudo` para o instalador automático de uma linha, ele escalará privilégios, se necessário. 42 | 43 | ``` 44 | Para aprender mais sobre os pós e contras das releases *noturnas* vs *estáveis*, veja nossa [nota sobre as duas opções](#nightly-vs-stable-releases). 45 | ``` 46 | 47 |
Clique aqui para mais informações e uso avançado do script de instalação de uma linha. 48 | 49 | Verifique a integridade do script com esse comando: 50 | 51 | ```bash 52 | [ "735e9966a4cf0187863e06a5282b34a7" = "$(curl -Ss https://my-netdata.io/kickstart.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID" 53 | ``` 54 | 55 | _Deverá imprimir a mensagem `OK, VALID` se o script for o que enviamos._ 56 | 57 | O script `kickstart.sh`: 58 | 59 | - detecta a distribuição Linux e **instala os pacotes de sistemas necessários** para construir o Netdata (esse passo pedirá confirmação) 60 | - baixa o código da última versão do Netdata para `/usr/src/netdata.git`. 61 | - instala o Netdata executando `./netdata-installer.sh` do código baixado. 62 | - instala `netdata-updater.sh` para `cron.daily`, assim sua instalação do netdata será atualizada diariamente (você receberá uma mensagem do cron apenas se a atualização falhar). 63 | - Para fins de controle de qualidade (QA), esse método de instalação nos informa se o processo foi bem-sucedido ou se falhou. 64 | 65 | O script `kickstart.sh` passa todos seus parâmetros para `netdata-installer.sh`, dessa maneira você pode adicionar mais parâmetros para customizar sua instalação. Aqui estão alguns parâmetros importantes: 66 | 67 | - `--dont-wait`: Habilita instalações automatizadas, não solicitando permissões para instalar quaisquer pacotes necessários. 68 | - `--dont-start-it`: Impede que o instalador inicie o Netdata automaticamente. 69 | - `--stable-channel`: Atualiza automaticamente somente no lançamento de novas versões principais. 70 | - `--no-updates`: Previne atualizações automáricas de qualquer tipo. 71 | - `--local-files`: Usado para instalações offline. Passe quatro caminhos de arquivo: o tarball do Netdata, o checksum, o tarball do plugin go.d e o tarball de configuração do plugin go.d, para forçar o kickstart a executar o processo usando esses arquivos. 72 | 73 | Exemplo utilizando todos os parâmetros acima: 74 | 75 | ```bash 76 | bash <(curl -Ss https://my-netdata.io/kickstart.sh) --dont-wait --dont-start-it --no-updates --stable-channel --local-files /tmp/my-selfdownloaded-tarball.tar.gz /tmp/checksums.txt /tmp/manually.downloaded.go.d.binary.tar.gz /tmp/manually.downloaded.go.d.config.tar.gz 77 | ``` 78 | Nota: `--stable-channel` e `--local-files` se sobrepõem, se você utilizar a opção com tarball, a opção stable-channel não será eficaz 79 |
80 | 81 | Uma vez que o Netdata está instalado, veja [Começando](../../docs/getting-started.md). 82 | 83 | --- 84 | 85 | ## Binário estatico pré-construido para Linux 64bit 86 | ## Linux 64bit pre-built static binary 87 | 88 | ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.requests_per_url&options=unaligned&dimensions=kickstart64&group=sum&after=-3600&label=last+hour&units=installations&value_color=orange&precision=0) ![](https://registry.my-netdata.io/api/v1/badge.svg?chart=web_log_nginx.requests_per_url&options=unaligned&dimensions=kickstart64&group=sum&after=-86400&label=today&units=installations&precision=0) 89 | 90 | Você pode instalar um binário estático pré-compilado do Netdata em qualquer sistema Linux Intel/AMD 64 bits (mesmo aqueles que não tem um gerenciador de pacotes, como CoreOS, CirrOS, sistemas baseados em busybox, etc). Você também pode utilizar esses pacotes em sistemas como gerenciadores de pacotes não suportados ou quebrados. 91 | 92 | Para instalar o Netdata a partir de um pacote binário em qualquer distribuição Linux e qualquer versão de kernel em sistemas **Intel/AMD 64bit**, e mantê-lo atualizado com nossas **nightly releases** automaticamente, execute o seguinte comando: 93 | 94 | ```bash 95 | bash <(curl -Ss https://my-netdata.io/kickstart-static64.sh) 96 | ``` 97 | 98 | !!! Nota 99 | Não use `sudo` para esse instalador — ele escalará privilégios, se necessário. 100 | 101 | ``` 102 | Para aprender mais sobre os pós e contras das releases *noturnas* vs *estáveis*, veja nossa [nota sobre as duas opções](#nightly-vs-stable-releases). 103 | 104 | Se seu sistema não possui o `bash` instalado, acesse `Mais informações e uso avançado do script kickstart-static64.sh` para instruções de como rodar o instalador sem `bash`. 105 | 106 | O script instala o Netdata em `/opt/netdata`. 107 | ``` 108 | 109 |
Clique aqui para mais informações e uso avançado desse comando. 110 | 111 | Verifique a integridade do script com o comando abaixo: 112 | 113 | ```bash 114 | [ "c529e4eb7ce201845cef605d450f8380" = "$(curl -Ss https://my-netdata.io/kickstart-static64.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID" 115 | ``` 116 | 117 | *Deverá imprimir a mensagem `OK, VALID` se o script for o que enviamos.* 118 | 119 | O script `kickstart-static64.sh` passa todos seus parâmetros para `netdata-installer.sh`, dessa maneira você pode adicionar mais parâmetros para personalizar sua instalação. Abaixo estão alguns parâmetros importantes: 120 | 121 | - `--dont-wait`: Habilita instalações automatizadas, não solicitando permissões para instalar quaisquer pacotes necessários. 122 | - `--dont-start-it`: Impede que o instalador inicie o Netdata automaticamente. 123 | - `--stable-channel`: Atualiza automaticamente somente no lançamento de novas versões principais. 124 | - `--no-updates`: Previne atualizações automáricas de qualquer tipo. 125 | - `--local-files`: Usado para instalações offline. Passe dois caminhos de arquivo: o tarball e o checsum do arquivo, para forçar o kickstart a executar o processo usando esses arquivos. 126 | 127 | Exemplo utilizando todos os parâmetros acima: 128 | 129 | ```sh 130 | bash <(curl -Ss https://my-netdata.io/kickstart-static64.sh) --dont-wait --dont-start-it --no-updates --stable-channel --local-files /tmp/my-selfdownloaded-tarball.tar.gz /tmp/checksums.txt 131 | ``` 132 | Nota: `--stable-channel` e `--local-files` se sobrepõem, se você utilizar a opção com tarball, a opção stable-channel não será eficaz 133 | 134 | Se o seu shell falhar em executar o comando da linha acima, faça: 135 | 136 | ```sh 137 | # download the script with curl 138 | curl https://my-netdata.io/kickstart-static64.sh >/tmp/kickstart-static64.sh 139 | 140 | # or, download the script with wget 141 | wget -O /tmp/kickstart-static64.sh https://my-netdata.io/kickstart-static64.sh 142 | 143 | # run the downloaded script (any sh is fine, no need for bash) 144 | sh /tmp/kickstart-static64.sh 145 | ``` 146 | 147 | - Os arquivos binários estáticos são mantidos no repositório [binary-packages](https://github.com/netdata/binary-packages). Você pode baixar qualquer um dos arquivos `.run` e executá-los. Esses arquivos são shell scripts auto-extraíveis construídos com [makeself](https://github.com/megastep/makeself). 148 | - O sistema alvo **não** precisa ter o bash instalado. 149 | - Os mesmos arquivos também podem ser utilizados para atualizações. 150 | - Para fins de controle de qualidade (QA), esse método de instalação nos informa se o processo foi bem-sucedido ou se falhou. 151 | 152 |
153 | 154 | Uma vez que o Netdata está instalado, veja [Começando](../../docs/getting-started.md). 155 | 156 | --- 157 | 158 | ## Executando o Netdata em um container Docker 159 | ## Run Netdata in a Docker container 160 | 161 | Você pode [Instalar o Netdata com Docker](../docker/#install-netdata-with-docker). 162 | 163 | --- 164 | 165 | ## Instalando o Netdata manualmente no Linux 166 | ## Install Netdata on Linux manually 167 | 168 | Para instalar a ultima versão do Netdata do git, por favor, siga esses 2 passos: 169 | 170 | 1. [Preparando o seu sistema](#prepare-your-system) 171 | 172 | Instale os pacotes necessários no seu sistema. 173 | 174 | 2. [Instalando o Netdata](#install-netdata) 175 | 176 | Baixe e installe o Netdata. Você também pode atualizá-lo do mesmo modo. 177 | 178 | --- 179 | 180 | ### Preparando o seu sistema 181 | ### Prepare your system 182 | 183 | Tente nosso instalador experimental automático de pacotes necessários (não precisa ser root). Ele tentará encontrar os pacotes que devem ser instalados em seu sistema para construir e executar o Netdata. Ele suporta a maioria das distribuições Linux lançadas após 2010: 184 | 185 | - **Alpine** Linux e seus derivados 186 | - Você precisa instalar o `bash`, antes de usar o instalador. 187 | 188 | - **Arch** Linux e seus derivados 189 | - Você precisa do arch/aur para o pacote Judy. 190 | 191 | - **Gentoo** Linux e seus derivados 192 | 193 | - **Debian** Linux e seus derivados (incluindo o **Ubuntu**, **Mint**) 194 | 195 | - **Redhat Enterprise Linux** e seus derivados (incluindo o **Fedora**, **CentOS**, **Amazon Machine Image**) 196 | - Por favor, veja que para RHEL/CentOS você precisa 197 | [EPEL](http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/). 198 | Além disso, a versão 6 do RHEL/CentOS também precisa 199 | [OKay](https://okay.com.mx/blog-news/rpm-repositories-for-centos-6-and-7.html) para empacotar a versão q do libuv. 200 | 201 | - **SuSe** Linux e seus derivados (incluindo o **openSuSe**) 202 | 203 | - **SLE12** Deve ter seus sistema registrado com o Suse Customer Center ou possuir o DVD. Veja [#1162](https://github.com/netdata/netdata/issues/1162) 204 | 205 | Instalar os pacotes para ter uma **instalação básica do Netdata** (monitoramento do sistema e muitas aplicações, sem `mysql` / `mariadb`, `postgres`, `named`, sensores de hardware e `SNMP`): 206 | 207 | ```sh 208 | curl -Ss 'https://raw.githubusercontent.com/netdata/netdata-demo-site/master/install-required-packages.sh' >/tmp/kickstart.sh && bash /tmp/kickstart.sh -i netdata 209 | ``` 210 | 211 | Instalar todos os pacotes necessários para **monitorar tudo que o Netdata pode monitorar**: 212 | 213 | ```sh 214 | curl -Ss 'https://raw.githubusercontent.com/netdata/netdata-demo-site/master/install-required-packages.sh' >/tmp/kickstart.sh && bash /tmp/kickstart.sh -i netdata-all 215 | ``` 216 | 217 | Se o comando acima não funcionar pra você, por favor, [abra uma issue no github](https://github.com/netdata/netdata/issues/new?title=packages%20installer%20failed&labels=installation%20help&body=The%20experimental%20packages%20installer%20failed.%0A%0AThis%20is%20what%20it%20says:%0A%0A%60%60%60txt%0A%0Aplease%20paste%20your%20screen%20here%0A%0A%60%60%60) com uma cópia da mensagem exibida na tela. Estamos tentando fazê-lo funcionar em qualquer lugar (isso é um dos motivos para o script [reportar](https://github.com/netdata/netdata/issues/2054) sucesso ou falha para todas as suas execuções). 218 | 219 | --- 220 | 221 | É assim que se faz manualmente: 222 | 223 | ```sh 224 | # Debian / Ubuntu 225 | apt-get install zlib1g-dev uuid-dev libuv1-dev liblz4-dev libjudy-dev libssl-dev libmnl-dev gcc make git autoconf autoconf-archive autogen automake pkg-config curl python 226 | 227 | # Fedora 228 | dnf install zlib-devel libuuid-devel libuv-devel lz4-devel Judy-devel openssl-devel libmnl-devel gcc make git autoconf autoconf-archive autogen automake pkgconfig curl findutils python 229 | 230 | # CentOS / Red Hat Enterprise Linux 231 | yum install autoconf automake curl gcc git libmnl-devel libuuid-devel openssl-devel libuv-devel lz4-devel Judy-devel make nc pkgconfig python zlib-devel 232 | 233 | # openSUSE 234 | zypper install zlib-devel libuuid-devel libuv-devel liblz4-devel judy-devel libopenssl-devel libmnl-devel gcc make git autoconf autoconf-archive autogen automake pkgconfig curl findutils python 235 | ``` 236 | 237 | Uma vez que o Netdata compilou, para executá-lo, os seguintes pacotes são necessários (já instalados usando os comandos acima): 238 | 239 | | pacotes | descrição| 240 | |:-----:|-----------| 241 | | `libuuid` | parte do `util-linux` para gerenciamento de GUIDs| 242 | | `zlib` | compresssão gzip para o servidor web interno do Netdata| 243 | 244 | *Netdata falhará ao iniciar sem os pacotes acimas.* 245 | 246 | Os plugins do Netdata plugins e vários aspectos do Netdata podem ser ativados ou se beneficiar quando instalados (são opcionais): 247 | 248 | | package |description| 249 | |:-----:|-----------| 250 | | `bash`|para plugins do shell e **alarmes de notificação**| 251 | | `curl`|para plugins do shell e **alarmes de notificação**| 252 | | `iproute` or `iproute2`| para monitoramento do **tráfego QoS do Linux**
use `iproute2` se `iproute` mostrar como não disponível ou obsoleto| 253 | | `python`|para maioria dos plugins externos| 254 | | `python-yaml`|usado para monitorar **beanstalkd**| 255 | | `python-beanstalkc`|usado para monitorar **beanstalkd**| 256 | | `python-dnspython`|usado para monitorar DNS query time| 257 | | `python-ipaddress`|usado para monitorar **DHCPd**
esse pacote é necessário apenas se o sistema tiver python v2. python v3 tem essa funcionalidade embarcada| 258 | | `python-mysqldb`
ou
`python-pymysql`|usado para monitorar o banco de dados **mysql** ou **mariadb**
`python-mysqldb` é rápido e, portando, preferido| 259 | | `python-psycopg2`|usado para monitorar o banco de dados **postgresql**| 260 | | `python-pymongo`|usado para monitorar o banco de dados **mongodb**| 261 | | `nodejs`|usado para os plugins `node.js` para monitorar dispositivos **named** e **SNMP**| 262 | | `lm-sensors`|para monitorar os **sensores de hardware**| 263 | | `libmnl`|para coletar metricas do netfilter| 264 | | `netcat`|for plugins do shell coletar métricas de sistemas remotos| 265 | 266 | *O Netdata se beneficiará muito se você tiver os pacotes acima instalados, mas ainda funcionará sem eles.* 267 | 268 | As engines de banco de dados do Netdata podem ser ativados quando os pacotes abaixo estão instalados (opcionais): 269 | 270 | | package | description| 271 | |:-----:|-----------| 272 | | `libuv` | Biblioteca de suporte multiplataforma com foco em I/O assíncrono, versão 1 ou superior| 273 | | `liblz4` | Algoritmo de compactação extremamente rápido, versão r129 ou superior| 274 | | `Judy` | Matriz dinâmica de uso geral| 275 | | `openssl`| Kit de ferramentas de criptografia e SSL/TLS| 276 | 277 | *O Netdata se beneficiará muito se você tiver os pacotes acima instalados, mas ainda funcionará sem eles.* 278 | 279 | --- 280 | 281 | ### Instalando o Netdata 282 | ### Install Netdata 283 | 284 | Siga os passos abaixo para instalar e executar o Netdata: 285 | 286 | ```sh 287 | # download it - the directory 'netdata' will be created 288 | git clone https://github.com/netdata/netdata.git --depth=100 289 | cd netdata 290 | 291 | # run script with root privileges to build, install, start Netdata 292 | ./netdata-installer.sh 293 | ``` 294 | 295 | - Se você não quer executá-lo imediatamente, adicione a opção `--dont-start-it`. 296 | 297 | - Você pode adicionar também `--stable-channel` para buscar e instalar apenas os lançamentos oficiais do GitHub, em vez das versões noturnas. 298 | 299 | - Se você não quiser instalá-lo nos diretórios padrão, poderá executar o instalador da seguinte maneira: `./netdata-installer.sh --install /opt`. Isso irá instalar o Netdata em `/opt/netdata`. 300 | 301 | - Se o seu servidor não tiver acesso à Internet e você definir manualmente o diretório de instalação no servidor, será necessário passar a opção `--disable-go` para o instalador. A opção impedirá que o instalador tente baixar e instalar o `go.d.plugin`. 302 | 303 | Depois que o instalador terminar, o arquivo `/etc/netdata/netdata.conf` será criado se você trocou o diretório de instalação, a configuração aparecerá também nesse diretório). 304 | 305 | Voce pode editar esse arquivo para definir as opções. Uma opção comum para ajustar é `history`, que controla o tamanho da memória do banco de dados que o Netdata utilizará. O valor padrão é `3600` segundos ( uma hora de dadosno gráfico) que faz com que o Netdata use cerca de 10-15MB de RAM (dependendo do número de gráficos detectados no seus sistema). Veja **\[[Requisistos de Memória]]**. 306 | 307 | Para aplicar as mudanças realizadas, reinicie o Netdata. 308 | 309 | --- 310 | 311 | ### Pacotes Binários 312 | ### Binary Packages 313 | 314 | ![](https://raw.githubusercontent.com/netdata/netdata/master/web/gui/images/packaging-beta-tag.svg?sanitize=true) 315 | 316 | Fornecemos nosso próprio flavor de pacotes binários para os sistemas operacionais mais comuns que estão em conformidade com os formatos de pacote .RPM e .DEB. 317 | 318 | No momento, lançamos pacotes seguindo o formato .RPM com a versão [1.16.0] (https://github.com/netdata/netdata/releases/tag/v1.16.0). 319 | Planejamos lançar pacotes seguindo o formato .DEB com a versão [1.17.0] (https://github.com/netdata/netdata/releases/tag/v1.17.0). 320 | Pioneiros podem experimentar nossos pacotes .DEB usando nossos lançamentos noturnos. Nosso atual provedor de infraestrutura de empacotamento é o [Package Cloud] (https://packagecloud.io). 321 | 322 | O Netdata está comprometida em oferecer suporte à instalação de nossa solução em todos os sistemas operacionais. Essa é uma batalha constante para o Netdata, pois nos esforçamos para automatizar e facilitar as coisas para nossos usuários. Para a matriz de suporte do sistema operacional, visite nossa página de suporte de [distribuições](../../packaging/DISTRIBUTIONS.md). 323 | 324 | Oferecemos dois repositórios separados, um para os lançamentos estáveis e outro para os lançamentos noturnos. 325 | 326 | 1. Lançamentos estáveis: Nossas versões estáveis de produção são hospedadas no repositório [netdata/netdata](https://packagecloud.io/netdata/netdata) do package cloud 327 | 2. Lançamentos noturnos: Nossas últimas versões são hospedadas no repositório [netdata/netdata-edge](https://packagecloud.io/netdata/netdata-edge) do package cloud 328 | 329 | Visite as páginas dos repositórios e sigam as instruções de configuração rápida para começar. 330 | 331 | --- 332 | 333 | ## Outros Sistemas 334 | ## Other Systems 335 | 336 | ##### FreeBSD 337 | 338 | Você pode instalar o Netdata a partir da coleção de pacotes ou ports. 339 | 340 | Abaixo, como instalar a versão mais recente do Netdata a partir de fontes no FreeBSD: 341 | 342 | ```sh 343 | # install required packages 344 | pkg install bash e2fsprogs-libuuid git curl autoconf automake pkgconf pidof 345 | 346 | # download Netdata 347 | git clone https://github.com/netdata/netdata.git --depth=100 348 | 349 | # install Netdata in /opt/netdata 350 | cd netdata 351 | ./netdata-installer.sh --install /opt 352 | ``` 353 | 354 | ##### pfSense 355 | 356 | Para installar o Netdata no pfSense, execute os seguintes comandos (dentre de um shell ou sobre o prompt de **Diagnósticos/Comando** dentro da interface web do pfSense). 357 | 358 | Note que os primeiros 4 pacotes são baixados do repositório do pfSense para manter a compatibilidade com o pfSense, Netdata e Python que são baixados do repositório FreeBSD. 359 | 360 | ```sh 361 | pkg install pkgconf 362 | pkg install bash 363 | pkg install e2fsprogs-libuuid 364 | pkg install libuv 365 | pkg add http://pkg.freebsd.org/FreeBSD:11:amd64/latest/All/python36-3.6.9.txz 366 | pkg add http://pkg.freebsd.org/FreeBSD:11:amd64/latest/All/netdata-1.15.0.txz 367 | ``` 368 | **Nota:** Se você receber um erro de `Not Found` durante a execução dos dois ultimos comandos acima, você precisará procurar manualmente na [pasta do repositório](http://pkg.freebsd.org/FreeBSD:11:amd64/latest/All/) pela últimas versões disponíveis dos pacotes e utilizar suas URL, ou poderá tentar mudar manualmente a versão do netdata na URL da última versão. 369 | 370 | Você deve editar `/usr/local/etc/netdata/netdata.conf` e trocar `bind to = 127.0.0.1` para `bind to = 0.0.0.0`. 371 | 372 | Para iniciar manualmente o Netdata, execute `service netdata onestart` 373 | 374 | Visite o painel de controle do Netdata para confirmar se está tudo funcionando: `http://:19999` 375 | 376 | Para iniciar automaticamente o Netdata a cada boot, adicione `service netdata onestart` como uma entrada de comando do Shell dentro da interface web do pfSense em **Serviços/Shellcmd**. Você precisará instalar o pacote Shellcmd antecipadamente em **System/Package Manager/Available Packages**. O tipo Shellcmd deve ser definido como `Shellcmd`. 377 | ![](https://i.imgur.com/wcKiPe1.png) 378 | Alternativamente, mais informações podem ser encontradas em , para obter a mesma linha de comando e scripts. 379 | 380 | Se você tiver problema com o `/usr/bin/install` ausente no pfSense 2.3 ou anterior, atualize o pfSense ou use uma solução alternativa de 381 | 382 | **Nota:** No pfSense, os arquivos de configuração do Netdata estão localizados em `/usr/local/etc/netdata` 383 | 384 | ##### FreeNAS 385 | 386 | No FreeNAS-Corral-RELEASE (>=10.0.3), Netdata está pre-instalado. 387 | 388 | Para usar o Netdata, o serviço precisa ser habilitado e iniciado na **[CLI](https://github.com/freenas/cli)** do FreeNAS. 389 | 390 | Para ativar o serviço do Netdata: 391 | 392 | ```sh 393 | service netdata config set enable=true 394 | ``` 395 | 396 | Para iniciar o serviço do Netdata: 397 | 398 | ```sh 399 | service netdata start 400 | ``` 401 | 402 | ##### macOS 403 | 404 | O Netdata no macOS ainda possui gráficos limitados, mas plugins externos funcionam. 405 | 406 | Você pode instalar o Netdata com o [Homebrew](https://brew.sh/) 407 | 408 | ```sh 409 | brew install netdata 410 | ``` 411 | 412 | ou pela fonte: 413 | 414 | ```sh 415 | # install Xcode Command Line Tools 416 | xcode-select --install 417 | ``` 418 | 419 | pressione `Install` na janela de atualização do software, então 420 | 421 | ```sh 422 | # install HomeBrew package manager 423 | /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" 424 | 425 | # install required packages 426 | brew install ossp-uuid autoconf automake pkg-config 427 | 428 | # download Netdata 429 | git clone https://github.com/netdata/netdata.git --depth=100 430 | 431 | # install Netdata in /usr/local/netdata 432 | cd netdata 433 | sudo ./netdata-installer.sh --install /usr/local 434 | ``` 435 | 436 | O instalador também instalará uma lista de inicialização para iniciar o Netdata quando seu Mac iniciar. 437 | 438 | ##### Alpine 3.x 439 | 440 | Execute os comandos abaixo no Alpine Linux 3.x: 441 | 442 | ```sh 443 | # install required packages 444 | apk add alpine-sdk bash curl zlib-dev util-linux-dev libmnl-dev gcc make git autoconf automake pkgconfig python logrotate 445 | 446 | # if you plan to run node.js Netdata plugins 447 | apk add nodejs 448 | 449 | # download Netdata - the directory 'netdata' will be created 450 | git clone https://github.com/netdata/netdata.git --depth=100 451 | cd netdata 452 | 453 | 454 | # build it, install it, start it 455 | ./netdata-installer.sh 456 | 457 | 458 | # make Netdata start at boot 459 | echo -e "#!/usr/bin/env bash\n/usr/sbin/netdata" >/etc/local.d/netdata.start 460 | chmod 755 /etc/local.d/netdata.start 461 | 462 | # make Netdata stop at shutdown 463 | echo -e "#!/usr/bin/env bash\nkillall netdata" >/etc/local.d/netdata.stop 464 | chmod 755 /etc/local.d/netdata.stop 465 | 466 | # enable the local service to start automatically 467 | rc-update add local 468 | ``` 469 | 470 | ##### Synology 471 | 472 | A documentação anteriormente recomendava a instalação do pacote Debian Chroot a partir das fontes do pacote da comunidade Synology e a execução do Netdata de dentro do chroot. Isso não funciona, pois o ambiente chroot não tem acesso ao `/ proc` e, portanto, expõe muito poucas métricas ao Netdata. Além disso, [esta issue](https://github.com/SynoCommunity/spksrc/issues/2758), ainda aberta em 24/06/2018, indica que o pacote Debian Chroot não é adequado para versões DSM maiores que a versão 5 e pode corromper as bibliotecas do sistema e impossibilitar a inicialização do NAS. 473 | 474 | A boa notícia é que o instalador estático de 64-bit funciona bem se seu NAS é um que utiliza a arquitetura amd64. Ele instalará o conteúdo em `/opt/netdata`, tornando a remoção simples e segura. 475 | 476 | Quando o Netdata é instalado pela primeira vez, ele será executado como *root*. Isso pode ou não ser aceitável para você e, como outras instalações o executam como o usuário *netdata*, você pode fazer o mesmo. Isso requer algum trabalho extra: 477 | 478 | 1. Crie um grupo `netdata` via interface de grupo do Synology. Não o dê acesso a nada. 479 | 2. Crie um usuário `netdata` via interface de usuário do Synology. Não o dê acesso a nada e defina uma senha aleatória. Atribua o usuário ao grupo `netdata`. O Netdata será enviado a esse usuário durande a execução. 480 | 3. Altere a propriedade dos seguintes diretórios, conforme definido em [Segurança do Netdata](../../docs/netdata-security.md#security-design): 481 | 482 | ```sh 483 | chown -R root:netdata /opt/netdata/usr/share/netdata 484 | chown -R netdata:netdata /opt/netdata/var/lib/netdata /opt/netdata/var/cache/netdata 485 | chown -R netdata:root /opt/netdata/var/log/netdata 486 | ``` 487 | 488 | Além disso, a partir de 24/06/2018, o instalador do Netdata não reconhece o DSM como um sistema operacional; portanto, nenhum init script é instalado. Você precisará fazer isso manualmente: 489 | 490 | 1. Adicione [esse arquivo](https://gist.github.com/oskapt/055d474d7bfef32c49469c1b53e8225f) como `/etc/rc.netdata`. Torne-o executável com `chmod 0755 /etc/rc.netdata`. 491 | 2. Edite `/etc/rc.local` e adicione uma linha chamada `/etc/rc.netdata` para iniciá-lo no boot: 492 | 493 | ``` 494 | # Netdata startup 495 | [ -x /etc/rc.netdata ] && /etc/rc.netdata start 496 | ``` 497 | 498 | ## Lançamentos Noturnos vs. Estáveis 499 | ## Nightly vs. stable releases 500 | 501 | A equipe do Netdata mantêm duas versões do agente do Netdata: **noturnos** and **estáveis**. Por padrão, os scripts de instalação do Netdata fornecerão atualizações **automáticas noturnas**, pois essa é a nossa configuração recomendada. 502 | 503 | **Noturnos**: Criamos builds noturnas a cada 24 horas. Elas contêm código amplamente testado que corige bugs ou falhas de segurança, ou introduzem novos recursos ao Netdata. Todo lançamento noturno é um candidato para se tornar um lançamento estável; quando estiver pronto, simplesmente alteramos as tags de lançamento no GitHub. Isso significa que as versões noturnas são estáveis e comprovadamente funcionam corretamente na grande maioria dos casos de uso do Netdata. É por isso que a versão noturna é a *melhor opção para a maioria dos usuários de Netdata*. 504 | 505 | **Estáveis**: Criamos versões estáveis sempre que acreditamos que o código atingiu um marco importante. Na maioria das vezes, versões estáveis se correlacionam com a introdução de novos recursos significativos. Versões estáveis podem ser uma escolha melhor para aqueles que executam o Netdata em *sistemas de produção de missão crítica*, pois as atualizações ocorrerão com menos frequência e somente depois que a comunidade ajudar a corrigir os bugs que possam ter sido introduzidos nas versões anteriores. 506 | 507 | **Vantagens de usar as versões noturnas:** 508 | 509 | - Obtenha os recursos e correções mais recentes assim que estiverem disponíveis 510 | - Receba correções relacionadas à segurança imediatamente 511 | - Use código estável e totalmente testado que está sempre melhorando 512 | - Aproveite a mesma experiência Netdata que nossa comunidade está usando 513 | 514 | **Vantagens de usar as versões estáveis:** 515 | 516 | - Proteja-se do raro caso em que grandes bugs passam por nossos testes e afetam negativamente uma instalação do Netdata 517 | - Mantenha mais controle sobre a versão Netdata usada 518 | 519 | ## Instalações Offline 520 | ## Offline installations 521 | 522 | Você pode instalar o Netdata em sistemas sem acesso à Internet, mas é necessário executar algumas etapas extras para fazê-lo funcionar. 523 | 524 | Por padrão, o `kickstart.sh` e o` kickstart-static64.sh` baixam os ativos do Netdata, como o binário pré-compilado e algumas dependências, usando a conexão com a Internet do sistema, mas você também pode fornecer esses arquivos do sistema de arquivos local. 525 | 526 | Primeiro, baixe os arquivos necessários. Se você estiver usando o `kickstart.sh`, precisará do tarball do Netdata, do checksum, do binário do plug-in go.d e da configuração do plug-in go.d. Se você estiver usando o `kickstart-static64.sh`, precisará apenas do tarball e soma de verificação do Netdata. 527 | 528 | Faça o download dos arquivos necessários para um sistema que esteja conectado à Internet. Você pode usar os comandos abaixo ou visitar a [última versão do Netdata](https://github.com/netdata/netdata/releases/latest) e a [última página do release go.d plugin](https://github.com/netdata/go.d.plugin/releases) para baixar os arquivos necessários manualmente. 529 | 530 | #### kickstart.sh 531 | ```bash 532 | cd /tmp 533 | 534 | curl -s https://my-netdata.io/kickstart.sh > kickstart.sh 535 | 536 | # Netdata tarball 537 | curl -s https://api.github.com/repos/netdata/netdata/releases/latest | grep "browser_download_url.*tar.gz" | cut -d '"' -f 4 | wget -qi - 538 | 539 | # Netdata checksums 540 | curl -s https://api.github.com/repos/netdata/netdata/releases/latest | grep "browser_download_url.*txt" | cut -d '"' -f 4 | wget -qi - 541 | 542 | # Netdata dependency handling script 543 | curl -s https://raw.githubusercontent.com/netdata/netdata-demo-site/master/install-required-packages.sh | wget -qi - 544 | 545 | # go.d plugin 546 | # For binaries for OS types and architectures not listed on [go.d releases](https://github.com/netdata/go.d.plugin/releases/latest), kindly open a github issue and we will do our best to serve your request 547 | export OS=$(uname -s | tr '[:upper:]' '[:lower:]') ARCH=$(uname -m | sed -e 's/i386/386/g' -e 's/i686/386/g' -e 's/x86_64/amd64/g' -e 's/aarch64/arm64/g' -e 's/armv64/arm64/g' -e 's/armv6l/arm/g' -e 's/armv7l/arm/g' -e 's/armv5tel/arm/g') && curl -s https://api.github.com/repos/netdata/go.d.plugin/releases/latest | grep "browser_download_url.*${OS}-${ARCH}.tar.gz" | cut -d '"' -f 4 | wget -qi - 548 | 549 | # go.d configuration 550 | curl -s https://api.github.com/repos/netdata/go.d.plugin/releases/latest | grep "browser_download_url.*config.tar.gz" | cut -d '"' -f 4 | wget -qi - 551 | ``` 552 | 553 | #### kickstart-static64.sh 554 | ```bash 555 | cd /tmp 556 | 557 | curl -s https://my-netdata.io/kickstart-static64.sh > kickstart-static64.sh 558 | 559 | # Netdata static64 tarball 560 | curl -s https://api.github.com/repos/netdata/netdata/releases/latest | grep "browser_download_url.*gz.run" | cut -d '"' -f 4 | wget -qi - 561 | 562 | # Netdata checksums 563 | curl -s https://api.github.com/repos/netdata/netdata/releases/latest | grep "browser_download_url.*txt" | cut -d '"' -f 4 | wget -qi - 564 | ``` 565 | 566 | Mova os arquivos baixados para o diretório `/tmp` no sistema offline da maneira que sua política definida permitir (se houver alguma). 567 | 568 | Agora você pode executar os scripts `kickstart.sh` ou` kickstart-static64.sh` usando a opção `--local-files`. Esta opção requer que você especifique o local e os nomes dos arquivos que você acabou de baixar. 569 | 570 | !!! Nota: Quando usar `--local-files`, os scripts `kickstart.sh` ou `kickstart-static64.sh` não irá baixar nenhum arquivo do Netdata da internet. Mas, ainda assim, você pode precisar de uma conexão de internet para instalar dependêcias usando o gerenciador de pacotes do seu sistema. Os scripts irão avisar se seu sistema não possui todas as dependências. 571 | 572 | ```bash 573 | # kickstart.sh 574 | bash kickstart.sh --local-files /tmp/netdata-version-number-here.tar.gz /tmp/sha256sums.txt /tmp/go.d-binary-filename.tar.gz /tmp/config.tar.gz /tmp/install-required-packages.sh 575 | 576 | # kickstart-static64.sh 577 | bash kickstart-static64.sh --local-files /tmp/netdata-version-number-here.gz.run /tmp/sha256sums.txt 578 | ``` 579 | 580 | Agora que você terminou sua instalação offline, pode seguir para o nosso [guia de primeiros passos](../../docs/getting-started.md)! 581 | 582 | ## Atualizações automáticas 583 | ## Automatic updates 584 | 585 | Por padrão, os scripts de instalação do Netdata permitem atualizações automáticas para os canais de versões noturnos e estáveis. 586 | 587 | Se você preferir atualizar manualmente o seu agente Netdata, poderá desativar as atualizações automáticas usando a opção `--no-updates` ao instalar ou atualizar o Netdata usando o [script de instalação de uma linha](#one-line-installation). 588 | 589 | ```bash 590 | bash <(curl -Ss https://my-netdata.io/kickstart.sh) --no-updates 591 | ``` 592 | 593 | Com as atualizações desabilitadas, você poderá escolher exatamente quando e como você irá [atualizar o Netdata](UPDATE.md). 594 | 595 | [![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%2Finstaller%2FREADME&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)](<>) 596 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | --------------------------------------------------------------------------------