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
No graphs will created when using this command: --plugin=apps::varnish::local::plugin --hostname=x.x.x.x --ssh-username=user --filter-perfdata='^(client_req|cache_hit|cache_hitpass|cache_miss|backend_conn|backend_busy|backend_unhealthy|backend_fail|sess_drop|sess_fail|sess_queued|threads_failed)$' --mode=stats
On GUI you can see the following:
We can exclude that the problem is not depending on perl connector.
When you force a check through the GUI then the perf datas will be returned correctly but only for this forced check for 1 time:
Next scheduled check by the engine will reproduce newly the problem
Also deleting the cache file will not solve the problem.
The text was updated successfully, but these errors were encountered:
Could you test on command line the same action as centreon-engine user to check if the issue is occuring also this way.
We should also schedule a remote session (we'll see this by mail).
Latest plugin version
No graphs will created when using this command:
--plugin=apps::varnish::local::plugin --hostname=x.x.x.x --ssh-username=user --filter-perfdata='^(client_req|cache_hit|cache_hitpass|cache_miss|backend_conn|backend_busy|backend_unhealthy|backend_fail|sess_drop|sess_fail|sess_queued|threads_failed)$' --mode=stats
On GUI you can see the following:
We can exclude that the problem is not depending on perl connector.
When you force a check through the GUI then the perf datas will be returned correctly but only for this forced check for 1 time:
Next scheduled check by the engine will reproduce newly the problem
Also deleting the cache file will not solve the problem.
The text was updated successfully, but these errors were encountered: