maplelabs / maplelabs/FOSS-Projects
Generic Reactive Monitoring Agent
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Developing reactive applications over streaming pipelines are very popular in recent days. Many opensource frameworks that are available in the market (Ex: SpringBoot reactive apis, Eclipse .Vertx....) for developing reactive applications
https://docs.spring.io/spring-framework/docs/current/reference/html/web-reactive.html
https://vertx.io/docs/vertx-reactive-streams/java/
Since the reactive monitoring are very specific to technological frameworks, i don't see any common reactive monitoring agent which supports all the platform frameworks.
The following can be done as a part of generic reactive monitoring agent.
- Identify the common reactive metrics which supports all the technological frameworks. This is bit tough initially, but we can arrive at common metrics list
- Create a testing framework which support different frameworks which exposes the common metrics
- Expand the metrics list over a period of time based on the knowledge earned during development phase
- Develop the agent in jar based deployable format, so that it can be easy to run the agent without external dependencies
- Develop a web UI to expose metrics in rich dashboards or expose an option to integrate with SnappyFlow
- The agent jar can be easily integrate with Prometheus based monitoring platforms
Based on comments, i can come up with the initial development approach for the following applications
- Event bus (messaging)
- Http servers
- Web sockets
- Datagram sockets
- Thread pool
- Net client/Server
- ....
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
No repository files, tests, or entry points are identified. Start by reading the linked Spring WebFlux and Vert.x reactive-streams documentation, then define the initial framework scope and common metrics before planning the agent. Done would require an agreed monitoring scope and an implemented agent, deployment format, and integration path, but the issue does not specify acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, prometheus, spring-boot
- Domain
- api, backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100