Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[apps::varnish::local::plugin] mode=stats: no graphs will created - Buffer creation #5123

Open
joschi99 opened this issue Jul 31, 2024 · 6 comments

Comments

@joschi99
Copy link
Contributor

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:
image

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:
image
Next scheduled check by the engine will reproduce newly the problem

Also deleting the cache file will not solve the problem.

@lucie-dubrunfaut
Copy link
Contributor

Hello :)

So if I understand correctly, only the force check (once) will allow the plugin to work correctly?

@joschi99
Copy link
Contributor Author

joschi99 commented Sep 2, 2024

Yes

@lucie-dubrunfaut
Copy link
Contributor

All right, I'll check with the dev team to look at the subject at our next session, and I'll keep you informed.

@joschi99
Copy link
Contributor Author

joschi99 commented Sep 2, 2024

If you need we can show this behaviour durang a remote session.

@lucie-dubrunfaut
Copy link
Contributor

Hello :)

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).

@joschi99
Copy link
Contributor Author

I can confirm that the problem was related that both services was using the same stats file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants