Skip to content

Maintain monitorable & actionable object status across restart of HERD exe

Use case: You're developing a plugin - building the code manually - and want to rebuild the code in order to debug some issues, fix a bug, add a new command or more monitoring data etc., however you can't re-run the full set of commands that took you to the current state

  • In particular, in HGC running the commands again would disrupt the FE, requiring one to realign all frontend links.

State to be preserved includes at least:

  • For each monitorable object: Enabled/Non-critical/Disabled
  • For each metric: Enabled/Non-critical/Disabled
  • For each actionable object: Enabled/Disabled; FSM state?

General question: Default behaviour if object now exists but didn't before - and vice versa.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information