We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is a problem with counters from munin-node.exe. Problem as I find out is for now with counters:
Object | Counter Process | IO Read Operations/sec Process | IO Write Operations/sec Process | IO Data Operations/sec Process | IO Other Operations/sec
Process | IO Read Operations/sec Process | IO Write Operations/sec Process | IO Data Operations/sec Process | IO Other Operations/sec
The count value read using powershell / cmd is ok. For example:
Powershell -> Get-Counter -Counter "\Process(*)\IO Other Operations/sec" -MaxSamples 1
CMD -> typeperf.exe -c "\Process(*)\IO Other Operations/sec" -sc 1
After few restart munin-node (run as services or started manually) for an indefinite time, the correct value is returned.
└──╼ $ telnet 4949 Trying ... Connected to < Host name>.>. Escape character is '^]'. munin node at < Host name>.> fetch IOReadOpSec IOReadOpSec.value 0.00 IOReadOpSec_1_.value 0.00 IOReadOpSec_2_.value 0.00 IOReadOpSec_3_.value 0.00 IOReadOpSec_4_.value 0.00 IOReadOpSec_5_.value 0.00 IOReadOpSec_6_.value 0.00 IOReadOpSec_7_.value 0.00 IOReadOpSec_8_.value 0.00 IOReadOpSec_9_.value 0.00 IOReadOpSec_10_.value 0.00 IOReadOpSec_11_.value 0.00 IOReadOpSec_12_.value 0.00 IOReadOpSec_13_.value 0.00 IOReadOpSec_14_.value 0.00 IOReadOpSec_15_.value 0.00 IOReadOpSec_16_.value 0.00 IOReadOpSec_17_.value 0.00 IOReadOpSec_18_.value 0.00 IOReadOpSec_19_.value 0.00 IOReadOpSec_20_.value 0.00 IOReadOpSec_21_.value 0.00 IOReadOpSec_22_.value 1.33 IOReadOpSec_23_.value 0.00 IOReadOpSec_24_.value 3.34 IOReadOpSec_25_.value 0.00 IOReadOpSec_26_.value 0.00 IOReadOpSec_27_.value 0.00 IOReadOpSec_28_.value 0.00 IOReadOpSec_29_.value 0.00 IOReadOpSec_30_.value 0.00 IOReadOpSec_31_.value 0.00 IOReadOpSec_32_.value 0.00 IOReadOpSec_33_.value 0.00 IOReadOpSec_34_.value 0.00 IOReadOpSec_35_.value 0.00 IOReadOpSec_36_.value 0.00 IOReadOpSec_37_.value 0.00 . ^] telnet> q Connection closed.
└──╼ $ telnet 4949 Trying ... Connected to < Host name>.>. Escape character is '^]'.
fetch IOReadOpSec IOReadOpSec.value 0.00 IOReadOpSec_1_.value 0.00 IOReadOpSec_2_.value 0.00 IOReadOpSec_3_.value 0.00 IOReadOpSec_4_.value 0.00 IOReadOpSec_5_.value 0.00 IOReadOpSec_6_.value 0.00 IOReadOpSec_7_.value 0.00 IOReadOpSec_8_.value 0.00 IOReadOpSec_9_.value 0.00 IOReadOpSec_10_.value 0.00 IOReadOpSec_11_.value 0.00 IOReadOpSec_12_.value 0.00 IOReadOpSec_13_.value 0.00 IOReadOpSec_14_.value 0.00 IOReadOpSec_15_.value 0.00 IOReadOpSec_16_.value 0.00 IOReadOpSec_17_.value 0.00 IOReadOpSec_18_.value 0.00 IOReadOpSec_19_.value 0.00 IOReadOpSec_20_.value 0.00 IOReadOpSec_21_.value 0.00 IOReadOpSec_22_.value 1.33 IOReadOpSec_23_.value 0.00 IOReadOpSec_24_.value 3.34 IOReadOpSec_25_.value 0.00 IOReadOpSec_26_.value 0.00 IOReadOpSec_27_.value 0.00 IOReadOpSec_28_.value 0.00 IOReadOpSec_29_.value 0.00 IOReadOpSec_30_.value 0.00 IOReadOpSec_31_.value 0.00 IOReadOpSec_32_.value 0.00 IOReadOpSec_33_.value 0.00 IOReadOpSec_34_.value 0.00 IOReadOpSec_35_.value 0.00 IOReadOpSec_36_.value 0.00 IOReadOpSec_37_.value 0.00 . ^] telnet> q Connection closed.
In all other situations there is a error.
$ telnet 4949 Trying ... Connected to . Escape character is '^]'. munin node at < Host name>.> fetch IOReadOpSec Unknown Error . ^] telnet> q Connection closed.
$ telnet 4949 Trying ... Connected to . Escape character is '^]'.
fetch IOReadOpSec
. ^] telnet> q Connection closed.
Problem occure in all servers where we have Windows as a system.
The text was updated successfully, but these errors were encountered:
Same situation here... :( Any development? Any News? ps script runs from poowershell but timing out in munin :(
Sorry, something went wrong.
I am not familiar with perf counters but ill take a look at it...
Use of munin-node.exe -run gives generally more informations. Can you provide it's output during your query resulting in "unknown error"?
No branches or pull requests
There is a problem with counters from munin-node.exe.
Problem as I find out is for now with counters:
The count value read using powershell / cmd is ok.
For example:
After few restart munin-node (run as services or started manually) for an indefinite time, the correct value is returned.
In all other situations there is a error.
Problem occure in all servers where we have Windows as a system.
The text was updated successfully, but these errors were encountered: