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
Is your feature request related to a problem? Please describe.
When a remote poller has temporarily lost connectivity, it still collects the data but it does not process thresholds.
The code of the thold plugin is distributed across all connected machines, therefore it would probably be possible to do so.
Replication of thold settings must probably be added, not sure if there is a proper hook in the replication code, which can call code from a plugin.
Describe the solution you'd like
If a poller is disconnected, it should have its thold configs in the local DB so that it can process the thresholds and generate the alert logs in place of the master.
The text was updated successfully, but these errors were encountered:
it would be cool if one day we could have thold run checks on each of the servers kinda like a spine for thold
that way each server participates in threshold checking
Is your feature request related to a problem? Please describe.
When a remote poller has temporarily lost connectivity, it still collects the data but it does not process thresholds.
The code of the thold plugin is distributed across all connected machines, therefore it would probably be possible to do so.
Replication of thold settings must probably be added, not sure if there is a proper hook in the replication code, which can call code from a plugin.
Describe the solution you'd like
If a poller is disconnected, it should have its thold configs in the local DB so that it can process the thresholds and generate the alert logs in place of the master.
The text was updated successfully, but these errors were encountered: