oxidecomputer / oxidecomputer/progenitor
Annotate errors with address of the server?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 136
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
In some of our uses of progenitor clients, we don't know the exact server that handled the request:
- We could be using multiple clients configured to talk to different servers
- We could be talking to a server identified by DNS name that identifies multiple possible hosts
Particularly in the case of a request failing, it'd be nice to log the server address. In 1 we could annotate any logs with the client that was used, but I don't think we have any recourse for 2 without help from progenitor, maybe?
(Some down in the weeds context: https://github.com/oxidecomputer/omicron/pull/4502#discussion_r1397680403)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how progenitor clients identify their configured servers and how request failures are logged. Read the linked omicron discussion for context, then determine whether the generated client can expose the actual server address when DNS resolves to multiple hosts. Done means a concrete, agreed approach for annotating failures or documenting why it is not possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100