changed how we determine if we should start monitr to be more consistent with other services, also fixing it so that it starts if FQDNs are used
Merge pull request #404 from shatterednirvana/appmonitoring-on-ec2

Starting AppMonitoring correctly in EC2