With the number of machines we manage in AWS, that's not really an option since that would essentially be a custom client for each site. The hosts themselves already present themselves as a hostname but it is not in DNS (for various reasons) and only the amazon provided name is resolvable.
=G=
On 12/13/2013 04:40 AM, deepak deore wrote:
For EC2 hosts, I changed MACHINEDOTS variable in runclient.sh on xymon client. eg. MACHINEDOTS=hostname.example.com <http://hostname.example.com>
On server side, no need to use CLIENT or NAME in hosts.cfg, just use the name which is defined in client's MACHINEDOTS.
On Fri, Dec 13, 2013 at 8:53 AM, Galen Johnson <solitaryr at gmail.com <mailto:solitaryr at gmail.com>> wrote:
Is it possible to key on the "NAME:" or "CLIENT:" definition instead of HOST? Monitoring several systems in EC2 and all the servers have hosts defined as ec2-12-34-56-78.blah.blah.blah. =G= _______________________________________________ Xymon mailing list Xymon at xymon.com <mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon