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

Logging of the registered services #5

Open
ghost opened this issue Mar 13, 2017 · 2 comments
Open

Logging of the registered services #5

ghost opened this issue Mar 13, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented Mar 13, 2017

Is there already an idea to log the registered services?

This could include an ordered logging of the service invocations. Each service has an unique id and each transaction between the services gets a number, so the logger can create a "schedule" with the start point and the end point of the transaction. With such a plan it's possible to identify which process at which step fails, just like a stacktrace, but distributed to all the services.

If you think, this idea is useful I would implement it. But it would be great if we could coordinate the work - is there already some work done for logging or where is a good starting point in the code for this work.

Best Regards
Erik

@ivargrimstad
Copy link
Owner

That's a pretty nice feature! Let's come up with a good design and then see how we go forward with the implementation. It should be flexible so any kind of logging mechanism can be used.

We may actually even consider a standalone SnoopEE Logging Service to handle all of this to keep it decoupled from the SnoopEE Discovery Service.

@ghost
Copy link
Author

ghost commented Mar 20, 2017

Yeah sounds good.

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

1 participant