On 22 June 2017 at 16:29, Randy Barlow <bowlofeggs@xxxxxxxxxxxxxxxxx> wrote:
> Hello! I'm new to Nagios. Will this patch work for monitoring
> cdn.registry.fedoraproject.org, which lives completely outside our
> network? I basically just copy/pasted this from the code that appears
> to monitor our proxies, but I wasn't sure what to put on the
> hostgroup_name since this isn't really our proxy (so that's probably
> wrong in the below patch). Thoughts?
So the CDN would need a host or hostgroup set up for it. It is
currently pointing as such:
$ host cdn.registry.fedoraproject.org
cdn.registry.fedoraproject.org is an alias for 1723040894.rsc.cdn77.org.
1723040894.rsc.cdn77.org has address 185.180.13.25
So we would need to add something to the
roles/nagios_server/templates/nagios/hosts/other.cfg.j2
define host {
host_name cdn.registry.fedoraproject.org
alias cdn.registry.fedoraproject.org
use mincheck
address cdn.registry.fedoraproject.org
{% if vars['nagios_location'] == 'internal' %}
parents phx2-gw
{% else %}
parents ibiblio-gw
{% endif %}
}
## Did this
and then instead of a hostgroup_name you would use 'host_name
cdn.registry.fedoraproject.org'
>
> diff --git a/roles/nagios_server/templates/nagios/services/websites.cfg.j2 b/roles/nagios_server/templates/nagios/services/websites.cfg.j2
> index ab137a7..386472b 100644
> --- a/roles/nagios_server/templates/nagios/services/websites.cfg.j2
> +++ b/roles/nagios_server/templates/nagios/services/websites.cfg.j2
> @@ -73,6 +73,14 @@ define service {
> use websitetemplate
> }
>
> +define service {
> + hostgroup_name proxies
> + service_description http-moby-registry-cdn
> + check_command check_website_ssl!cdn.registry.fedoraproject.org!/v2/!{}
> + max_check_attempts 8
> + use websitetemplate
> +}
> +
>
> ##
> ## Individual hosts
> _______________________________________________
> infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
>
--
Stephen J Smoogen.
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
