0 comments (0 comments)0 reactions (0 reactions)0 assignees (0 assignees)Scala1,384 stars (1,384 stars)248 forks (248 forks)batch import
help wanted
Description
This issue does not include a description.
Contributor guide
- Tech stack
- scala
- Domain
- backendobservability
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 4
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 3-5 days
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- unclear
- Prerequisites
- ScalaAkka basics
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 20
- Research direction
- This issue lacks a description. To implement timeout policy statistics, first examine existing timeout policies in the codebase, likely under the squbs http module. Look for similar metric implementations using Codahale Metrics or Kamon. Check the Akka HTTP documentation on request timeouts. Consider adding a counter for timeouts and a gauge for timeout durations. The issue is old and may require investigating current code structure.