我目前正在為遙測網(wǎng)絡(luò)應(yīng)用程序編寫一個 Prometheus 導(dǎo)出器。我已閱讀此處的文檔“編寫導(dǎo)出器”，雖然我了解實(shí)現(xiàn)自定義收集器以避免競爭條件的用例，但我不確定我的用例是否適合直接檢測?；旧?，網(wǎng)絡(luò)指標(biāo)通過網(wǎng)絡(luò)設(shè)備通過 gRPC 進(jìn)行流式傳輸，因此我的導(dǎo)出器只需接收它們，而不必有效地抓取它們。我使用以下代碼直接檢測：我使用 promauto 包聲明我的指標(biāo)以保持代碼緊湊：package metricsimport (? ? "github.com/lucabrasi83/prom-high-obs/proto/telemetry"? ? "github.com/prometheus/client_golang/prometheus"? ? "github.com/prometheus/client_golang/prometheus/promauto")var (? ? cpu5Sec = promauto.NewGaugeVec(? ? ? ? prometheus.GaugeOpts{? ? ? ? ? ? Name: "cisco_iosxe_iosd_cpu_busy_5_sec_percentage",? ? ? ? ? ? Help: "The IOSd daemon CPU busy percentage over the last 5 seconds",? ? ? ? },? ? ? ? []string{"node"},? ? )下面是我如何簡單地設(shè)置 gRPC 協(xié)議緩沖區(qū)解碼消息的指標(biāo)值：cpu5Sec.WithLabelValues(msg.GetNodeIdStr()).Set(float64(val))最后，這是我的主循環(huán)，它基本上處理我感興趣的指標(biāo)的遙測 gRPC 流：for {? ? ? ? req, err := stream.Recv()? ? ? ? if err == io.EOF {? ? ? ? ? ? return nil? ? ? ? }? ? ? ? if err != nil {? ? ? ? ? ? logging.PeppaMonLog(? ? ? ? ? ? ? ? "error",? ? ? ? ? ? ? ? fmt.Sprintf("Error while reading client %v stream: %v", clientIPSocket, err))? ? ? ? ? ? return err? ? ? ? }? ? ? ? data := req.GetData()? ? ? ? msg := &telemetry.Telemetry{}? ? ? ? err = proto.Unmarshal(data, msg)? ? ? ? if err != nil {? ? ? ? ? ? log.Fatalln(err)? ? ? ? }? ? ? ? if !logFlag {? ? ? ? ? ? logging.PeppaMonLog(? ? ? ? ? ? ? ? "info",? ? ? ? ? ? ? ? fmt.Sprintf(? ? ? ? ? ? ? ? ? ? "Telemetry Subscription Request Received - Client %v - Node %v - YANG Model Path %v",? ? ? ? ? ? ? ? ? ? clientIPSocket, msg.GetNodeIdStr(), msg.GetEncodingPath(),? ? ? ? ? ? ? ? ),? ? ? ? ? ? )? ? ? ? }? ? ? ? }}我使用 Grafana 作為前端，到目前為止，在關(guān)聯(lián) Prometheus 公開的指標(biāo)與直接在設(shè)備上檢查指標(biāo)時，還沒有看到任何特定的差異。所以我想了解這是否遵循 Prometheus 最佳實(shí)踐，或者我仍然應(yīng)該采用自定義收集器路線。
1 回答
鳳凰求蠱
TA貢獻(xiàn)1825條經(jīng)驗(yàn) 獲得超4個贊
您沒有遵循最佳實(shí)踐，因?yàn)槟谑褂媚溄拥降奈恼滤娴娜种笜?biāo)。使用您當(dāng)前的實(shí)現(xiàn)，在設(shè)備斷開連接后（或者更準(zhǔn)確地說，直到您的導(dǎo)出器重新啟動），您的儀表板將永遠(yuǎn)顯示 CPU 指標(biāo)的一些任意且恒定的值。
相反，RPC 方法應(yīng)該維護(hù)一組本地指標(biāo)，并在方法返回后將其刪除。這樣，當(dāng)設(shè)備斷開連接時，設(shè)備的指標(biāo)就會從抓取輸出中消失。
這是執(zhí)行此操作的一種方法。它使用包含當(dāng)前活動指標(biāo)的地圖。每個映射元素都是一個特定流的一組指標(biāo)（我理解它對應(yīng)于一個設(shè)備）。一旦流結(jié)束，該條目就會被刪除。
package main
import (
"sync"
"github.com/prometheus/client_golang/prometheus"
)
// Exporter is a prometheus.Collector implementation.
type Exporter struct {
// We need some way to map gRPC streams to their metrics. Using the stream
// itself as a map key is simple enough, but anything works as long as we
// can remove metrics once the stream ends.
sync.Mutex
Metrics map[StreamServer]*DeviceMetrics
}
type DeviceMetrics struct {
sync.Mutex
CPU prometheus.Metric
}
// Globally defined descriptions are fine.
var cpu5SecDesc = prometheus.NewDesc(
"cisco_iosxe_iosd_cpu_busy_5_sec_percentage",
"The IOSd daemon CPU busy percentage over the last 5 seconds",
[]string{"node"},
nil, // constant labels
)
// Collect implements prometheus.Collector.
func (e *Exporter) Collect(ch chan<- prometheus.Metric) {
// Copy current metrics so we don't lock for very long if ch's consumer is
// slow.
var metrics []prometheus.Metric
e.Lock()
for _, deviceMetrics := range e.Metrics {
deviceMetrics.Lock()
metrics = append(metrics,
deviceMetrics.CPU,
)
deviceMetrics.Unlock()
}
e.Unlock()
for _, m := range metrics {
if m != nil {
ch <- m
}
}
}
// Describe implements prometheus.Collector.
func (e *Exporter) Describe(ch chan<- *prometheus.Desc) {
ch <- cpu5SecDesc
}
// Service is the gRPC service implementation.
type Service struct {
exp *Exporter
}
func (s *Service) RPCMethod(stream StreamServer) (*Response, error) {
deviceMetrics := new(DeviceMetrics)
s.exp.Lock()
s.exp.Metrics[stream] = deviceMetrics
s.exp.Unlock()
defer func() {
// Stop emitting metrics for this stream.
s.exp.Lock()
delete(s.exp.Metrics, stream)
s.exp.Unlock()
}()
for {
req, err := stream.Recv()
// TODO: handle error
var msg *Telemetry = parseRequest(req) // Your existing code that unmarshals the nested message.
var (
metricField *prometheus.Metric
metric prometheus.Metric
)
switch msg.GetEncodingPath() {
case CpuYANGEncodingPath:
metricField = &deviceMetrics.CPU
metric = prometheus.MustNewConstMetric(
cpu5SecDesc,
prometheus.GaugeValue,
ParsePBMsgCpuBusyPercent(msg), // func(*Telemetry) float64
"node", msg.GetNodeIdStr(),
)
default:
continue
}
deviceMetrics.Lock()
*metricField = metric
deviceMetrics.Unlock()
}
return nil, &Response{}
}
- 1 回答
- 0 關(guān)注
- 191 瀏覽
添加回答
舉報(bào)
0/150
提交
取消