prometheus / prometheus/node_exporter

Feature Request to resolve Virtual-IPs to Hostnames in ipvs collector

Open
#1,141 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
Go
Stars
13.8k
Forks
2.7k
Avg merge
1d 23h
Merged PRs (30d)
8

Description

node_exporter version: 0.15.2

Feature request for the collector ipvs:

  • Option to resolve Virtual-IPs to hostnames

Currently the ipvs collector provides Virtual IPs associated to Real-server IPs, and I set up a dashboard in Grafana with a multitude of label_replace to show off the Virtual IPs as hostnames. What about a flag for ipvs to resolve the IPs?

For example:

# curl -s <SERVER>:9100/metrics
# HELP node_ipvs_backend_connections_active The current active connections by local and remote address.
# TYPE node_ipvs_backend_connections_active gauge
node_ipvs_backend_connections_active{local_address="<VIRTUAL-IP>",local_port="443",proto="TCP",remote_address="<IP-REAL-SERVER>",remote_port="443"} 0
[...]

The collector could have an option to provide both fields local_address and local_fqdn:

node_ipvs_backend_connections_active{local_address="<VIRTUAL-IP>",local_fqdn="<FQDN>",local_port="443",proto="TCP",remote_address="<IP-REAL-SERVER>",remote_port="443"} 0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the ipvs collector and inspect the node_ipvs_backend_connections_active metrics exposed by the /metrics endpoint. Determine how an optional resolution setting should add local_fqdn alongside local_address, and verify that the collector produces both labels when enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.