micrometer-metrics / micrometer-metrics/prometheus-rsocket-proxy
Consider splitting Spring auto-config module for client/server
- Dominant language
- Java
- Stars
- 77
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
With both together, it means non-web applications that just want the client auto-configuration have the server dependencies pulled in which causes Spring Boot to configure them as a web app. Currently, the workaround would be to exclude the server artifact `prometheus-rsocket-proxy-server` from the `prometheus-rsocket-spring` dependency.
Contributor guide
Research direction
Start by inspecting the prometheus-rsocket-spring dependency and the prometheus-rsocket-proxy-server artifact described in the issue. Trace how the combined Spring auto-configuration brings server dependencies into client-only applications and triggers web configuration. Done means client-only applications can use the client auto-configuration without pulling in the server artifact or being configured as web applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100