On 4 March 2015 at 13:26, Brandon Dale <BDale at kitchengroup.com.au> wrote:
On a windows machine running PowerShell client v1.98 I don’ta. [ifstat] contains data e.g
[ifstat]
fe80::25a5:b99d:55cd:951f%12 2655878237 519887923
10.250.100.163 2655878237 519887923
Yep, this should be parseable by Xymon. In principle.
At the moment I’m guessing the ifstat data isn’t in a format xymon will automatically graph and add to the trends page
Xymon will parse the [ifstat] data from a Windows machine, if it's in a suitable format. From the source code, the regexp for this is:
^([a-zA-Z0-9.:]+)\s+([0-9]+)\s+([0-9]+)I note that in the first [ifstat] line above, there's a percentage sign in the first token, which doesn't match the regexp. I don't know of Xymon continues on looking for other lines to match, or if it rejects the whole [ifstat] section as corrupt. But I wonder what would happen if the IPv6 address wasn't in the [ifstat] client data. Any chance you can unbind IPv6 for testing?
Another thing to note is that some of the "powershell" processing in Xymon just re-uses the "bbwin" processing. But there are some bits of parsing code, including for "ifstat" it seems, that only look for the bbwin OS string, and I can't see any place in the powershell handling code that tries to fake the bbwin OS for ifstat. In other words, could be that the code simply isn't there to do what you want. But it might also be the case that adjusting the powershell client to report itself as the bbwin client might do the trick.
J