Oximiter: Determine useful transport layer connection tracking

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
networking, observability

Research direction

Start by reviewing Oximeter's existing metrics and the transport-layer statistics collected by constat, focusing particularly on TCP connection tracking. Determine which statistics are useful for diagnosing network problems and define how they should be pulled into Oximeter; the work is done when the useful data and integration approach are established.

Written by the indexing model from the issue text.

Description

Metrics networking

When the network starts going sideways, OS transport layer connection tracking, particularly for TCP, is a trove of valuable information to diagnose what's going on. These are the types of statistics kept by constat. Determine what would be useful here and how to pull that information into Oximeter.

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

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.

More from oxidecomputer/omicron

All issues in oxidecomputer/omicron

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.