夜莺-Nightingale
夜莺V7
项目介绍 功能概览
部署升级 部署升级
数据接入 数据接入
告警管理 告警管理
数据查看 数据查看
功能介绍 功能介绍
API FAQ
夜莺V6
项目介绍 架构介绍
快速开始 快速开始
黄埔营
安装部署 安装部署
升级
采集器 采集器
使用手册 使用手册
API API
数据库表结构 数据库表结构
FAQ FAQ
开源生态
Prometheus
版权声明
第1章:天降奇兵 第1章:天降奇兵
第2章:探索PromQL 第2章:探索PromQL
第3章:Prometheus告警处理 第3章:Prometheus告警处理
第4章:Exporter详解 第4章:Exporter详解
第5章:数据与可视化 第5章:数据与可视化
第6章:集群与高可用 第6章:集群与高可用
第7章:Prometheus服务发现 第7章:Prometheus服务发现
第8章:监控Kubernetes 第8章:监控Kubernetes
第9章:Prometheus Operator 第9章:Prometheus Operator
参考资料

Categraf traces-agent配置

简介

Categraf 从 v0.3.55 版本开始不再集成 traces-agent. 之前的版本对OpenTelemetry Collector做了定制和封装, OpenTelemetry社区迭代很快,categraf开源版中,请大家优先使用 OpenTelemetry Collector.

trace-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
快猫星云 联系方式 快猫星云 联系方式
快猫星云 联系方式
快猫星云 联系方式
快猫星云 联系方式
快猫星云
OpenSource
开源版
Flashcat
Flashcat