bloomberg/goldpinger

[feature request] topology.kubernetes.io values in metrics

Open

#84 opened on Apr 30, 2020

View on GitHub
 (4 comments) (2 reactions) (0 assignees)JavaScript (2,316 stars) (186 forks)batch import
enhancementgood first issuehelp wanted

Description

It would be awesome if the metrics could include the node's topology.kubernetes.io/region & topology.kubernetes.io/zone (not sure what the non-AWS fields are called). That would help quickly identify patterns in the results. e.g., zone "a" is slower than zone "b" or that cross-zone traffic is what's causing a large spike in response times. Not sure if this is possible within the framework of this tool.

keep up the great work & thank you!

Contributor guide

Tech stack
javascriptkubernetesdockerprometheus
Domain
backendcloudobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Kubernetes node labelsFamiliarity with Prometheus metrics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate how goldpinger currently exposes metrics (likely via Prometheus) and identify where to add node topology labels. Look at the existing metric definitions and the cluster's node label fetching. Check the issue comments for any additional context. There is no linked PR, so the implementation is open.
[feature request] topology.kubernetes.io values in metrics · bloomberg/goldpinger#84 | Good First Issue