[Enhancement] Use event processor chain to process event in runtime
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 658
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 52
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
### Enhancement Request
Currently, EventMesh has the basic ability to transport event, but there are shortcomings in process/filter/monitor/xx event.
For example, if I want to monitor the number of specific events or just filter some events, I may need to change the code in runtime(It is not easy).
A better practice is to add a processor when I want to add a processing function, instead of change the core code.
### Describe the solution you'd like
Using event processor chain to enhance EventMesh runtime.

### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
Contributor guide
Research direction
Start by inspecting EventMesh's runtime event-processing path and how runtime components currently process events. Define the processor-chain extension points and determine how filtering, monitoring, and other processing functions should be registered without changing core runtime code. Done means the runtime uses the chain for these processing functions and the behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100