Local Socket for Server Health monitoring
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Is your feature request related to a problem?
Currently some server providers rely on the mspt command for server health monitoring. This limits paper in changing the command output to be consistent with spark's output.
Describe the solution you'd like.
Since this is not really the intended way to monitor server health in the first place, there should be a proper alternative.
Maybe a local socket that serves this information can be implemented.
Describe alternatives you've considered.
keep using the command
Other
No response
Contributor guide
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 the existing mspt command and how server health information is currently exposed. Define the local socket's health data and protocol, then verify that monitoring tools can consume it consistently with Spark's output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100