You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.
I know that you are looking into monitoring support on the JVM side.
If I can make a wish, I'd like to see an interface that has an API similair to this:
In most cases, monitoring will probably not be interested in individual actors, it just needs an IncrementStopped() kind of API.
But with a monitoring API like the one proposed above.
We can provide other features, related to monitoring.
e.g. debug visualizers that update in realtime when topology changes.
For example, I did a spike on this, visualizing our chat example:
I think that could be extremely valuable to end users to see how their system or a subsection of the system behaves.
And by allowing the monitoring support to reason about the actual actorref that has been affected, this is pretty easy to accomplish.
The text was updated successfully, but these errors were encountered:
@rogeralsing, it will probably take a while in ostrich mode until we can meaningfully comment on this suggestion: we are currently looking into how monitoring could potentially be implemented, there are several proposals floating around and we are far from picking a clear winner.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I know that you are looking into monitoring support on the JVM side.
If I can make a wish, I'd like to see an interface that has an API similair to this:
In most cases, monitoring will probably not be interested in individual actors, it just needs an
IncrementStopped()
kind of API.But with a monitoring API like the one proposed above.
We can provide other features, related to monitoring.
e.g. debug visualizers that update in realtime when topology changes.
For example, I did a spike on this, visualizing our chat example:
I think that could be extremely valuable to end users to see how their system or a subsection of the system behaves.
And by allowing the monitoring support to reason about the actual actorref that has been affected, this is pretty easy to accomplish.
The text was updated successfully, but these errors were encountered: