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

Provide a way to view long running operations for an agent #156

Closed
lenkan opened this issue Dec 21, 2023 · 4 comments
Closed

Provide a way to view long running operations for an agent #156

lenkan opened this issue Dec 21, 2023 · 4 comments

Comments

@lenkan
Copy link
Collaborator

lenkan commented Dec 21, 2023

Do you think it is a good idea to expose an endpoint for listing the active long running operations for an agent? I guess mainly for debugging purposes.

One use case example would be to see if a delegate operation is waiting to be resolved. Currently, only GET /operations/{operation name} and DELETE /operations/{operation.name} are exposed.

At first glance it looks fairly straightforward to implement, so I can take a look at implementing it. But first wanted to make sure it makes sense.

@psteniusubi
Copy link
Contributor

I have an implementation of this here https://github.com/psteniusubi/keria/tree/feat-get-operations-list

I've found it useful in integration testing to make sure all long running operations have been handled.

I can create a PR if it is useful.

@psteniusubi
Copy link
Contributor

I remember now that creating unit tests for this was a challenge. That's why I didn't create a PR. I'll see if I can create a test for this.

@kentbull
Copy link
Contributor

I like this idea. Being able to get all long running operations would be good for monitoring as well.

@lenkan
Copy link
Collaborator Author

lenkan commented Jan 18, 2024

Resolved with #158

@lenkan lenkan closed this as completed Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants