Robot Results

I'm okay to go in the direction proposed here. i.e. to stop further development of the tedge-watchdog component (at to deprecate it) and to improve the tedge-monit-setup for thin-edge.

I'm still in two minds about whether to fully deprecate the plugin or not. I'm leaning towards at least keeping it in the code based, so the other users can continue development (if they do prefer the systemd based approach).

@didier-wenzek What do you think?

I'm still in two minds about whether to fully deprecate the plugin or not.

Do we have known users? Not sure. We have few or no questions about it.

I would keep the code for the tedge_watchdog but remove it from the documentation as we do for the c8y_firmware_plugin.

I'm still in two minds about whether to fully deprecate the plugin or not.

Do we have known users? Not sure. We have few or no questions about it.

We don't have any exact data to support this, however since the tedge-watchdog always needed some manual configuration to enable it, I really doubt anyone has been using it, however I would use caution and expect there to be at least a few users.

I would keep the code for the tedge_watchdog but remove it from the documentation as we do for the c8y_firmware_plugin.

The tedge watchdog docs has already been marked as "unlisted" since a while now (when the original limitation was found see #2635). Unlisted pages don't turn up in the doc searches, but can still be accessed if someone knows the url (e.g. they have saved it in a bookmark) - here is a link to the unlisted page

The tedge watchdog docs has already been marked as "unlisted"

So, let's leave things as they are now.