Cheshire Cat Computing

Is it possible to monitor multiple host in single graph?
Ex.
Packet loss Monitoring for Primary & Secondary WAN link in a single graph.

Yes.
You need to first define the Targets for the component lines of the graph, then define a UserDefined graph over the two (or more) component Targets.
This is not really a cfgmaker issue, it is using the extended Routers2 directives. See the documentation on Userdefined graphs and the routers.cgi*Graph[] directive.
Steve

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hi Steve,

Following is the code using but getting 2 different graphs. I want both the hosts in Single Graph. Please advise.

Regards
ARS.

#########
#WAN-Primary
Target[WAN-Primary.ping]: `mrtg-ping-probe -t 42 -p loss/loss WAN-Primary`
PageTop[WAN-Primary.ping]: <H1> WAN-Primary Response time </H1>
Title[WAN-Primary.ping]: Packet Loss Monitoring - WAN-Primary
Factor[WAN-Primary.ping]: 0.001
Maxbytes[WAN-Primary.ping]: 100
AbsMax[WAN-Primary.ping]: 101
Options[WAN-Primary.ping]: growright,gauge
YLegend[WAN-Primary.ping]: % Packet Loss
ShortLegend[WAN-Primary.ping]: %
LegendO[WAN-Primary.ping]: Low:&nbsp;
LegendI[WAN-Primary.ping]: High:
Legend1[WAN-Primary.ping]: Ping response time range
Legend2[WAN-Primary.ping]: Ping response time range
Legend4[WAN-Primary.ping]: Peak low response RTT
Legend3[WAN-Primary.ping]: Peak high response RTT
routers.cgi*WithPeak[WAN-Primary.ping]: none
routers.cgi*Options[WAN-Primary.ping]: nomax, nopercent, nototal, scaled
routers.cgi*InOut[WAN-Primary.ping]: no
routers.cgi*InCompact[WAN-Primary.ping]: no
routers.cgi*GraphStyle[WAN-Primary.ping]: range
routers.cgi*Icon[WAN-Primary.ping]: clock-sm.gif
routers.cgi*ShortName[WAN-Primary.ping]: Response
routers.cgi*Graph[WAN-Primary.ping]: WAN1


#WAN-Secondary
Target[WAN-Secondary.ping]: `mrtg-ping-probe -t 42 -p loss/loss WAN-Secondary`
PageTop[WAN-Secondary.ping]: <H1> WAN-Secondary Response time </H1>
Title[WAN-Secondary.ping]: Packet Loss Monitoring - WAN-Secondary
Factor[WAN-Secondary.ping]: 0.001
Maxbytes[WAN-Secondary.ping]: 100
AbsMax[WAN-Secondary.ping]: 101
Options[WAN-Secondary.ping]: growright,gauge
YLegend[WAN-Secondary.ping]: % Packet Loss
ShortLegend[WAN-Secondary.ping]: %
LegendO[WAN-Secondary.ping]: Low:&nbsp;
LegendI[WAN-Secondary.ping]: High:
Legend1[WAN-Secondary.ping]: Ping response time range
Legend2[WAN-Secondary.ping]: Ping response time range
Legend4[WAN-Secondary.ping]: Peak low response RTT
Legend3[WAN-Secondary.ping]: Peak high response RTT
routers.cgi*WithPeak[WAN-Secondary.ping]: none
routers.cgi*Options[WAN-Secondary.ping]: nomax, nopercent, nototal, scaled
routers.cgi*InOut[WAN-Secondary.ping]: no
routers.cgi*InCompact[WAN-Secondary.ping]: no
routers.cgi*GraphStyle[WAN-Secondary.ping]: range
routers.cgi*Icon[WAN-Secondary.ping]: clock-sm.gif
routers.cgi*ShortName[WAN-Secondary.ping]: Response
routers.cgi*Graph[WAN-Secondary.ping]: WAN12

########

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hi Steve,

It works perfectly.
Thanks for the support.

Regards
ARS