Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Open a REST API to list current actives jobs #563

Open
fabienfeatOF opened this issue Jun 7, 2023 · 3 comments
Open

[Question] Open a REST API to list current actives jobs #563

fabienfeatOF opened this issue Jun 7, 2023 · 3 comments

Comments

@fabienfeatOF
Copy link

Hello !
We need to list current actives jobs from a spring boot application.
Zeebe gRPC API doesn't give this feature, so we decided to develop this feature in the zeebe-simple-monitor project.

The idea is to open a generic endpoint to be able to search any object (process instance, jobs, message, etc.) in zeebe-simple-monitor.
Is this the right solution from your point of view ?

We also see ZeeQs, wich is maybe a better solution to bring our need ?

Thanks

@skayliu
Copy link
Contributor

skayliu commented Jun 7, 2023

Hi, @fabienfeatOF, both of them are using the Hazelcast exporter to export data from the broker to you DB, then use you own service to query data from you DB.

@fabienfeatOF
Copy link
Author

fabienfeatOF commented Jun 14, 2023

Hi @skayliu, Ok I understand your response.

We have studied Camunda's Operate REST API and we are considering proposing the same functionalities.
We understand that Simple Monitor corresponds to Operate.

Therefore, we would like to suggest pull requests (PRs) to fulfill this need.
Does this align with your vision for the Simple Monitor, and would you be open to accepting these PRs?

Thanks

@nitram509
Copy link
Collaborator

@fabienfeatOF
Sure, such a feature seems reasonable and I would review and merge such a PR.

Here're some hints for implementation/contribution:

  • since there is already logic implemented for the server-side rendering, please try code re-use where it makes sense.
  • unit tests are very welcome ;)
  • documentation is first-class citizen, means please provide information or code snippets in the README, e.g. on how to use the API

@fabienfeatOF Last note: I'm a fan of incremental improvements ... means if you provide a "draft pr" I will commit myself to review in a timely manner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants