mdt-dialout-collector

所属分类:人工智能/神经网络/深度学习
开发工具:C++
文件大小:166KB
下载次数:2
上传日期:2023-03-05 10:22:21
上 传 者sh-1993
说明:  模型驱动遥测-通过gRPC拨出收集<多供应商>指标

文件列表:
CMakeLists.txt (17191, 2023-08-01)
LICENSE (1075, 2023-08-01)
Makefile.am (442, 2023-08-01)
VERSION (7, 2023-08-01)
autogen.sh (68, 2023-08-01)
bin (0, 2023-08-01)
config_m4 (0, 2023-08-01)
config_m4\debug.m4 (664, 2023-08-01)
config_m4\profiling.m4 (516, 2023-08-01)
config_m4\versioning.m4 (1136, 2023-08-01)
configure.ac (2148, 2023-08-01)
csv (0, 2023-08-01)
doc (0, 2023-08-01)
doc\CONFIG-KEYS (9458, 2023-08-01)
doc\Changelog (3692, 2023-08-01)
doc\Dependencies (864, 2023-08-01)
doc\Deprecated (0, 2023-08-01)
doc\Deprecated\centos_INSTALL.md (2651, 2023-08-01)
doc\Deprecated\debian_INSTALL.md (2109, 2023-08-01)
doc\integration-with-pmtelemetryd.md (3565, 2023-08-01)
doc\network-devices-conf-snip.md (4104, 2023-08-01)
docker (0, 2023-08-01)
docker\Dockerfile (924, 2023-08-01)
docker\scripts (0, 2023-08-01)
docker\scripts\grpc.sh (861, 2023-08-01)
docker\scripts\mdt_dialout_collector.conf (169, 2023-08-01)
docker\scripts\mdt_dialout_collector.sh (370, 2023-08-01)
grpc-collector.pc.in (357, 2023-08-01)
install.sh (23695, 2023-08-01)
proto (0, 2023-08-01)
proto\Cisco (0, 2023-08-01)
... ...

[![Build status](https://github.com/network-analytics/mdt-dialout-collector/workflows/ci/badge.svg?branch=main)](https://github.com/network-analytics/mdt-dialout-collector/actions) ## Table of Content * [Introduction](#introduction) * [Deployment options](#deployment-options) * [Standalone binary with mdt-dialout-collector](#standalone-binary-with-mdt-dialout-collector) * [Library/Header integration with pmtelemetryd](#libraryheader-integration-with-pmtelemetryd) * [Build/Install](#buildinstall) * [References](#references) ## Introduction **mdt-dialout-collector** & **gRPC dial-out libraries** are leveraging the [**gRPC Framework**](https://grpc.io/) to implement a multi-vendor gRPC Dial-out collector. The [doc/Changelog](https://github.com/network-analytics/mdt-dialout-collector/blob/main/doc/Changelog) file is including additional details about the supported network devices. The collector functionalities can be logically grouped into three categories: 1. **Data Collection** - they are steering the daemon(s) behavior. 2. **Data Manipulation** - they are conveniently transforming the in-transit data-stream. 3. **Data Delivery** - they are inter-connecting the collector with the next stage in the pipeline. The [doc/CONFIG-KEYS](https://github.com/network-analytics/mdt-dialout-collector/blob/main/doc/CONFIG-KEYS) file is including the description for each one of the available options. ## Deployment options The gRPC dial-out data-collection functionality can be deployed in two ways: ### Standalone binary with mdt-dialout-collector ```TEXT +------------------------------------------------------+ +---------+ | +------------+ +--------------+ +--------------+ | +---------+ | network |-->| | collection |-->| manipulation |-->| kafka client | |-->| kafka | +---------+ | +------------+ +--------------+ +--------------+ | | cluster | | [mdt-dialout-collector] | +---------+ +------------------------------------------------------+ ``` the building process is generating a single binary: ```TEXT /opt/mdt-dialout-collector/bin/mdt_dialout_collector ``` which, by default, is reading the running options from: ```TEXT /etc/opt/mdt-dialout-collector/mdt_dialout_collector.conf ``` Additionally, the default configuration file can be further specified via the following command line: ```TEXT /opt/mdt-dialout-collector/bin/mdt_dialout_collector -f ``` ### Library/Header integration with pmtelemetryd ```TEXT +---------------------------------------------------------+ +---------+ | +------------+ +--------------+ +-----------------+ | +------------+ | network |-->| | collection |-->| manipulation |-->| ZMQ (PUSH/PULL) | |-->| pipeline | +---------+ | +------------+ +--------------+ +-----------------+ | | next stage | | [pmtelemetryd] | +------------+ +---------------------------------------------------------+ ``` the building process is generating both the library and the header file required to build [pmtelemetryd](https://github.com/pmacct/pmacct/blob/master/INSTALL) with gRPC dial-out support: ``` /usr/local/lib/libgrpc_collector.la /usr/local/include/grpc_collector_bridge/grpc_collector_bridge.h ``` there is one main pmtelemetryd [CONFIG-KEYS](https://github.com/pmacct/pmacct/blob/master/CONFIG-KEYS) which is mandatory in order to enable the embedded gRPC dial-out collector: ```TEXT KEY: telemetry_daemon_grpc_collector_conf DESC: Points to a file containing the configuration of the gRPC collector thread. An example of the configuration plus all available config keys is available here: https://github.com/network-analytics/mdt-dialout-collector DEFAULT: none ``` ## Build/Install [install.sh](https://github.com/network-analytics/mdt-dialout-collector/blob/main/install.sh) is automating the build/install process, taking care of all [dependencies](https://github.com/network-analytics/mdt-dialout-collector/blob/main/doc/Dependencies). - The Standalone binary can be deployed using: ```SHELL sudo /bin/sh -c "$(curl -fsSL https://github.com/network-analytics/mdt-dialout-collector/raw/main/install.sh)" -- -b ``` - The Library/Header can be deployed using: ```SHELL sudo /bin/sh -c "$(curl -fsSL https://github.com/network-analytics/mdt-dialout-collector/raw/main/install.sh)" -- -l ``` ## References - [Integration with PMACCT/pmtelemetryd](https://github.com/network-analytics/mdt-dialout-collector/blob/main/doc/integration-with-pmtelemetryd.md) - [Network devices configuration snippets](https://github.com/network-analytics/mdt-dialout-collector/blob/main/doc/network-devices-conf-snip.md) - [Multivendor (async) gRPC dial-out collector - APNIC Blog](https://blog.apnic.net/2022/10/17/multivendor-async-grpc-dial-out-collector/)

近期下载者

相关文件


收藏者