Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
nico does not periodically republish managed host state on the event bus. this is a known choice. integrators are meant to query the nico api periodically to catch missed events. but some integrating services may not have access to query the API due to network restrictions, this can result in missed state that is never reconciled.
Feature Description
nico-core shall periodically republish current managed host state in addition to how it currently publishes managed host state on change.
Describe your ideal solution
nico can have a periodic task which walks through the current managed hosts that its instance is responsible for, and publish its current state on the dsx exchange event bus. if this is too noisy, healthy hosts can be published with less frequency.
Describe any alternatives you have considered
integrating systems could be required to deploy agents into each dsx data hall cluster to query the nico api and manage reconciliation themselves. since multiple integrating systems are interested in nico's events this is not preferred.
Additional context
No response
Code of Conduct
Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
nico does not periodically republish managed host state on the event bus. this is a known choice. integrators are meant to query the nico api periodically to catch missed events. but some integrating services may not have access to query the API due to network restrictions, this can result in missed state that is never reconciled.
Feature Description
nico-core shall periodically republish current managed host state in addition to how it currently publishes managed host state on change.
Describe your ideal solution
nico can have a periodic task which walks through the current managed hosts that its instance is responsible for, and publish its current state on the dsx exchange event bus. if this is too noisy, healthy hosts can be published with less frequency.
Describe any alternatives you have considered
integrating systems could be required to deploy agents into each dsx data hall cluster to query the nico api and manage reconciliation themselves. since multiple integrating systems are interested in nico's events this is not preferred.
Additional context
No response
Code of Conduct