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
- None
- Domain
- observabilityperformance
- 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.
- mostly clear
- Prerequisites
- Akka HTTP client connection poolJMX (Java Management Extensions)Squbs project structure
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 25
- Research direction
- Investigate existing JMX MBeans in Squbs (e.g., in src/main/scala/org/squbs/jmx) to understand the pattern. Examine Akka HTTP's client connection pool implementation and identify which metrics are available. Propose a design for exposing pool status via JMX. Potential files to modify include modules like akka http client or squbs jmx.