-
Notifications
You must be signed in to change notification settings - Fork 1
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
Observe mode events #1
Comments
This should not be too complicated, but I have a couple questions:
|
If you currently only rely on @chcorbato what do you think? |
I think de answer depends on how we decide to use metacontrol and system modes:
What would be your preferred design @norro ? |
I think you're right, Carlos, this is indeed a design decision. And when you put it like that I would suggest we go for the 2. option to have it more consistent. |
Superseeded by #2 |
Currently, the mode observer observes all
/{node}/transition_event
topics to observe state transition, e.g., going to active, inactive or error-processing. This way it is observing all state transitions, however, it is missing all mode changes.The observer should additionally observe
/{node}/mode_event
topics to observe mode changes, e.g., a node going from normal mode to degraded mode. Messages sent on this topic are of type ModeEvent and very close to the TransitionEvent messages.The text was updated successfully, but these errors were encountered: