import{_ as e,a}from"./chunks/webssh.Cvv4PsOJ.js";import{_ as r,c as t,o,a4 as n}from"./chunks/framework.BmdFiWrL.js";const _=JSON.parse('{"title":"Broker for Nezha - Advancing on more platforms","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/case/case7.md","filePath":"en_US/case/case7.md","lastUpdated":1724530785000}'),i={name:"en_US/case/case7.md"},l=n('

Broker for Nezha - Advancing on more platforms ​

Contributor:

Broker for Nezha is a modified version of the Nezha Agent that separates data collection from gRPC reporting, enabling small devices to connect to the Nezha Dashboard.

Project link: https://github.com/uubulb/broker

Online Documentation: Broker for Nezha

Difference from Nezha Agent ​

Broker for Nezha needs to be used with specific data collection software. Currently, it provides two data collection methods:

  1. HTTP (HTTP/1.1) - Active polling
  2. TCP - Passive collection (recommended to avoid creating redundant connections)

For existing data collection software, refer to the project README. Due to security concerns, it's recommended to use this only in a trusted network.

Writing a Data Collector ​

If you need to write your own data collector, you'll need to implement a basic HTTP server or TCP client and use a specific data format that Broker can recognize. For details, see: Data types

Examples ​

Dashboard
Dashboard

WebSSH
WebSSH
',17),s=[l];function c(d,f,h,p,u,m){return o(),t("div",null,s)}const k=r(i,[["render",c]]);export{_ as __pageData,k as default};