开源版
夜莺V6
项目介绍
架构介绍
快速开始
黄埔营
安装部署
升级
采集器
使用手册
API
数据库表结构
alert_aggr_view
alert_cur_event
alert_his_event
alert_mute
alert_rule
alert_subscribe
alerting_engines
board
board_payload
builtin_cate
busi_group
busi_group_member
chart_share
configs
datasource
metric_view
notify_tpl
recording_rule
role
role_operation
sso_config
target
task_record
task_tpl
task_tpl_host
user_group
user_group_member
users
FAQ
夜莺V5
企业版
智能告警
夜莺开源生态
Telegraf
Prometheus
版权声明
第1章:天降奇兵
第2章:探索PromQL
开篇
理解时间序列
Metrics类型
初识PromQL
PromQL操作符
PromQL聚合操作
PromQL内置函数
在HTTP API中使用PromQL
最佳实践:4个黄金指标和USE方法
小结
第3章:Prometheus告警处理
开篇
Prometheus告警简介
自定义Prometheus告警规则
部署Alertmanager
Alertmanager配置概述
基于标签的告警处理路由
使用Receiver接收告警信息
告警模板详解
屏蔽告警通知
使用Recoding Rules优化性能
小结
第4章:Exporter详解
第5章:数据与可视化
第6章:集群与高可用
第7章:Prometheus服务发现
第8章:监控Kubernetes
开篇
初识Kubernetes
在Kubernetes下部署Prometheus
Kubernetes下的服务发现
使用Prometheus监控Kubernetes集群
基于Prometheus的弹性伸缩
小结
第9章:Prometheus Operator
参考资料
Categraf traces-agent配置
简介
categraf对OpenTelemetry Collector做了简单的封装, 用户可以对接各种trace系统。
traces-agent 配置
文件位于conf/traces.yaml
, 当前默认只支持 extensions
reciver
processor
exporter
四个模块的配置。
traces:
# 是否开启trace-agent
enable: false
# Extensions:
# provide capabilities that can be added to the Collector, but which do not require direct access to telemetry data
# and are not part of pipelines. They are also enabled within the service section.
#
# Categraf supports:
# pprof: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/pprofextension
# health_check: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/healthcheckextension
# basicauth: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/basicauthextension
# jaegerremotesampling: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/jaegerremotesampling
extensions:
# pprof:
# endpoint: 0.0.0.0:1777
health_check:
#jaegerremotesampling:
# source:
# remote:
# endpoint: jaeger-collector:14250
#basicauth/server:
# htpasswd:
# file: .htpasswd
# inline: |
# ${BASIC_AUTH_USERNAME}:${BASIC_AUTH_PASSWORD}
#
#basicauth/client:
# client_auth:
# username: username
# password: password
# Receiver:
# which can be push or pull based, is how data gets into the Collector. Configuring a receiver does not enable it.
# Receivers are enabled via pipelines within the service section.
#
# Categraf supports:
# jaeger: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/jaegerreceiver
# zipkin: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/zipkinreceiver
# otlp: https://github.com/open-telemetry/opentelemetry-collector/tree/main/receiver/otlpreceiver
# kafka: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/kafkareceiver
receivers:
jaeger:
protocols:
thrift_http:
endpoint: 0.0.0.0:14268
# Processor:
# run on data between being received and being exported. Configuring a processor does not enable it.
# Processors are enabled via pipelines within the service section.
#
# Categraf supports:
# batch: https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor/batchprocessor
# attributes: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/attributesprocessor
# resource: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourceprocessor
# span: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/spanprocessor
# tailsampling: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/tailsamplingprocessor
processors:
batch/example:
send_batch_size: 1000
timeout: 10s
attributes/example:
actions:
- key: ident
value: categraf-01.bj
action: upsert
# Exporter:
# which can be push or pull based, is how you send data to one or more backends/destinations. Configuring an
# exporter does not enable it. Exporters are enabled via pipelines within the service section.
#
# Categraf supports:
# otlp: https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlpexporter
# otlphttp: https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlphttpexporter
# jaeger: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/jaegerexporter
# zipkin: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/zipkinexporter
# kafka: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/kafkaexporter
# alibabacloudlogservice: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/alibabacloudlogserviceexporter
exporters:
jaeger:
endpoint: "127.0.0.1:14250"
tls:
insecure: true
zipkin:
endpoint: "http://127.0.0.1:9411/api/v2/spans"
# Service:
# used to configure what components are enabled in the Collector based on the configuration found in the receivers,
# processors, exporters, and extensions sections. If a component is configured, but not defined within the service
# section then it is not enabled. The service section consists of three sub-sections:
# - extensions: Extensions consist of a list of all extensions to enable.
# - pipelines: A pipeline consists of a set of receivers, processors and exporters.
# - telemetry: Telemetry is where the telemetry for the collector itself can be configured.
service:
extensions: [health_check, pprof]
pipelines:
traces:
receivers: [jaeger]
processors: [batch/example, attributes/example]
exporters: [jaeger, zipkin]
telemetry:
logs:
level: info
initial_fields:
service: my-instance