Add tracing logs/spans
- Dominant language
- Rust
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
It is very useful for identifying performance issues to log how long the network calls take.
Maybe this should be put under a dedicated `tracing` feature.
JIRA: [FD-161](https://filify.atlassian.net/browse/FD-161)
[FD-161]: https://filify.atlassian.net/browse/FD-161?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named; begin by locating the Rust network-call implementation in fireplace and reviewing how requests are currently handled. Define the tracing scope and success criteria with maintainers before implementing logs or spans, then verify that the selected network calls expose useful duration data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100