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
As I observed, there isn't any APIs to pause/resume/start diagnostic updaters. Especially when invoking diagnostic_updaters in LifecycleNodes, diagnostic updaters begins publishing topic to /diagnostics just after LifecycleNodes constructing. As description in Managed Nodes, publishers in Lifecyclenodes should be configured and activated before publishing topics.
In my opinion, there are two ways:
We need to add some APIs to pause/resume/start updaters for special usage. Then we will face with choices: Will updater run timer by default? or updater only run timer after called "start" function?
We add a new header file, eg. diagnostic_updater_lifecycle.hpp. And create a class derived from DiagnosticTaskVector that class Updater derived. Then implement all LifecycleNodes' APIs in it.
The text was updated successfully, but these errors were encountered:
As I observed, there isn't any APIs to pause/resume/start diagnostic updaters. Especially when invoking diagnostic_updaters in LifecycleNodes, diagnostic updaters begins publishing topic to /diagnostics just after LifecycleNodes constructing. As description in Managed Nodes, publishers in Lifecyclenodes should be configured and activated before publishing topics.
In my opinion, there are two ways:
DiagnosticTaskVector
that classUpdater
derived. Then implement all LifecycleNodes' APIs in it.The text was updated successfully, but these errors were encountered: