You should send the data in a "data" instruction:
Cat mydsta.dat|$xymon --merge $xymsrv "data server.column whatever"
On Tue, 25 Apr 2023, 20:49 Scott Driemeier-Showers, <user-8d275c0639b6@xymon.invalid>
wrote:
Experts,
Revisiting a question I asked back in 2017, and is still nagging me today.
We monitor (among many other things) the network connections to our remote
offices with Xymon. Each site has a ?primary? network/firewall interface
that is monitored using the ?conn? test. I created a custom script to
monitor a ?secondary? interface (labeled ?voip?) at each site. From a
purely monitoring and alerting standpoint this combination of tests
operates flawlessly.
What I have never been able to get to work is the RRD/graphing on the
secondary interface.
To TEST2RRD in xymonserver.cfg I added ?,voip=tcp? to the end of the
stanza.
To GRAPHS in xymonserver.cfg I added ?,voip? to the end of the stanza.
To graphs.cfg I added the [voip] service definition, specifying FNPATTERN
^tcp.voip.(.+).rrd
The script builds results for each interface, set appropriate variable
values, and sends data with:
$XYMON $XYMSRV "status $SRVR.$COLUMN $STAT `date`
\n${MESG} \n&${STAT} ${DATA} \n"
What is NOT happening is the .rrd file is not being created.
Comparing the custom test results with those of the conn test in xymondlog:
# xymon 127.0.0.1 "xymondlog talsau.nmi.dom.voip"
talsau.nmi.dom|voip|green||1682104123|1682449560|1682451360|0|0|192.168.10.250||||N|
green Tue Apr 25 14:06:00 CDT 2023
Service voip on talsau.nmi.dom is OK (up)
&green 10.10.24.251 is alive (16.3 ms)
# xymon 127.0.0.1 "xymondlog talsau.nmi.dom.conn"
talsau.nmi.dom|conn|green|OrdAstLe|1682407336|1682449750|1682451550|0|0|192.168.10.250||||N|
green <!-- [flags:OrdAstLe] --> Tue Apr 25 14:09:09 2023 conn ok
Service conn on talsau.nmi.dom is OK (up)
&green 192.168.24.251 is alive (22.1 ms)
The only difference I see is the conn test includes ?|OrdAstLe|? flags in
position 4, where the voip test is blank.
Any thoughts/input would be greatly appreciated?
Thanks,
Scott