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

Lack of observability during successful operation #76

Open
jalaziz opened this issue Apr 9, 2024 · 1 comment
Open

Lack of observability during successful operation #76

jalaziz opened this issue Apr 9, 2024 · 1 comment

Comments

@jalaziz
Copy link

jalaziz commented Apr 9, 2024

So far I'm loving suture, but one thing that is less than ideal is the lack of observability during normal, successful operation. It would be great if events could be emitted for service start and normal service stop.

With these additional events, it should be possible to trace all important lifecycle events.

@jalaziz
Copy link
Author

jalaziz commented Apr 9, 2024

I just found #69. I understand the sentiment there, but I still think it would be valuable to have the events built-into suture for a few reasons:

  1. It makes event hook handling easier (e.g. no need to wrap sutureslog)
  2. It avoids the need to wrap each and every service and supervisor to emit the events.
  3. Sending the supervisor of a service in the event is not trivial from outside of suture.

I realize these may not be compelling enough reasons, but the general observability of the system is incomplete without these events.

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

1 participant