oxidecomputer / oxidecomputer/omicron

Publish per-IP-stack metrics to `oximeter`

Open
#2,162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Metrics networking
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

To aid debugging, we'd like to collect netstat-style data from each IP stack on the entire Gimlet to ClickHouse via oximeter. This could use the kernel interfaces in inet/mib2.h, look at the implementation of netstat itself for examples. Similar to the datalink metrics, the sled-agent needs to do this since it has visibility into everything.

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 by reading the sled-agent metrics implementation, especially the existing datalink metrics, then inspect the kernel interfaces in inet/mib2.h and the netstat implementation for per-IP-stack data. The work is done when netstat-style metrics from each IP stack on the Gimlet are published through oximeter to ClickHouse; no specific test is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
networking, observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.