Hi all,
Thank you for looking at my question. Currently I’m running into a problem that seems unsolvable. The company I work for uses Akamai’s CDN network to offload traffic from their origin servers. The way the Akamai CDN works is that clusters of servers, that have different IPs around the globe, provide access to our company’s website static assets faster than our origin servers would. Now the check I would like to create is a check that tries to acquire a specific URL and check for its contents, but I want the check to also obtain the current IP that it can resolve from the CDN network. Since the first check that Nagios does it to see what IP address it can obtain in order for it to apply a PING check to the host, this IP is setup as part of all the checks thereafter. I cannot have the static IP setup. Is there anyway within check_mk, OMD, WATO, or something else to force the check to obtain the IP address every time the check is ran? I know this is literally circumventing the way Nagios works.
Why do you want a check like this?
The reason for this is because we have had issues with Akamai’s CDN network, where some of their clusters may have severe packet loss and our website would become inaccessible.
Why not have the check against your origin servers?
Already have a check like this for my origin servers, but I need to have a check that also tests Akamai’s network as well.
Why does it matter if you have a fixed IP for the test?
The issue is that the check may fail for a different cluster of servers that Akamai’s DDNS has provided as a faster route to a client. If this happens, then I can’t tell with a static address whether the check has failed. Some client may report that the site is failing, but my check would not be able to provide that information because the IP that I’m hitting may be different than the one the client has.
Thanks,
Jesus
Hey There
I hope the link below helps…
https://mathias-kettner.de/checkmk_configvars.html#dyndns_hosts
dyndns_hosts
Hosts listed in this binary configuration list (which is compatible to [bulkwalk_hosts](https://mathias-kettner.de/checkmk_configvars.html#bulkwalk_hosts) ), do never do a DNS lookup but use their host name in all places where otherwise the
IP address would occur (also in the Nagios’ host declarations). That way, a dynamic DNS lookup will be done whenever the host will be contacted.
This is useful in two cases:
- If the host’s IP address dynamically changes (e.g. the host is a dialin router using dynamic DNS updates)
- If the host does not have any IP address (in that case you also have to make sure that the standard host check command is not used).
Kind regards,
Christoph
···
-----Original Message-----
From: Jesus Malena jesus.malena@gmail.com
To: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: [Check_mk (english)] Akamai DDNS domain IP allocation
Date: Mon, 14 Jul 2014 00:25:45 -0700
Hi all,
Thank you for looking at my question. Currently I’m running into a problem that seems unsolvable. The company I work for uses Akamai’s CDN network to offload traffic from their origin servers. The way the Akamai CDN works is that clusters of servers, that have
different IPs around the globe, provide access to our company’s website static assets faster than our origin servers would. Now the check I would like to create is a check that tries to acquire a specific URL and check for its contents, but I want the check
to also obtain the current IP that it can resolve from the CDN network. Since the first check that Nagios does it to see what IP address it can obtain in order for it to apply a PING check to the host, this IP is setup as part of all the checks thereafter.
I cannot have the static IP setup. Is there anyway within check_mk, OMD, WATO, or something else to force the check to obtain the IP address every time the check is ran? I know this is literally circumventing the way Nagios works.
Why do you want a check like this?
The reason for this is because we have had issues with Akamai’s CDN network, where some of their clusters may have severe packet loss and our website would become inaccessible.
Why not have the check against your origin servers?
Already have a check like this for my origin servers, but I need to have a check that also tests Akamai’s network as well.
Why does it matter if you have a fixed IP for the test?
The issue is that the check may fail for a different cluster of servers that Akamai’s DDNS has provided as a faster route to a client. If this happens, then I can’t tell with a static address whether the check has failed. Some client may report that the site
is failing, but my check would not be able to provide that information because the IP that I’m hitting may be different than the one the client has.
Thanks, Jesus
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
Darn it!!! Why didn’t I see that? I’ll take a look at that and report back.
Thanks for the link.
Jesus
···
On Mon, Jul 14, 2014 at 12:34 AM, Christoph Blau christoph@4dt.co.za wrote:
Hey There
I hope the link below helps…
https://mathias-kettner.de/checkmk_configvars.html#dyndns_hosts
dyndns_hosts
Hosts listed in this binary configuration list (which is compatible to [bulkwalk_hosts](https://mathias-kettner.de/checkmk_configvars.html#bulkwalk_hosts) ), do never do a DNS lookup but use their host name in all places where otherwise the
IP address would occur (also in the Nagios’ host declarations). That way, a dynamic DNS lookup will be done whenever the host will be contacted.
This is useful in two cases:
- If the host’s IP address dynamically changes (e.g. the host is a dialin router using dynamic DNS updates)
- If the host does not have any IP address (in that case you also have to make sure that the standard host check command is not used).
Kind regards,
Christoph
-----Original Message-----
From: Jesus Malena jesus.malena@gmail.com
To: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: [Check_mk (english)] Akamai DDNS domain IP allocation
Date: Mon, 14 Jul 2014 00:25:45 -0700
Hi all,
Thank you for looking at my question. Currently I’m running into a problem that seems unsolvable. The company I work for uses Akamai’s CDN network to offload traffic from their origin servers. The way the Akamai CDN works is that clusters of servers, that have
different IPs around the globe, provide access to our company’s website static assets faster than our origin servers would. Now the check I would like to create is a check that tries to acquire a specific URL and check for its contents, but I want the check
to also obtain the current IP that it can resolve from the CDN network. Since the first check that Nagios does it to see what IP address it can obtain in order for it to apply a PING check to the host, this IP is setup as part of all the checks thereafter.
I cannot have the static IP setup. Is there anyway within check_mk, OMD, WATO, or something else to force the check to obtain the IP address every time the check is ran? I know this is literally circumventing the way Nagios works.
Why do you want a check like this?
The reason for this is because we have had issues with Akamai’s CDN network, where some of their clusters may have severe packet loss and our website would become inaccessible.
Why not have the check against your origin servers?
Already have a check like this for my origin servers, but I need to have a check that also tests Akamai’s network as well.
Why does it matter if you have a fixed IP for the test?
The issue is that the check may fail for a different cluster of servers that Akamai’s DDNS has provided as a faster route to a client. If this happens, then I can’t tell with a static address whether the check has failed. Some client may report that the site
is failing, but my check would not be able to provide that information because the IP that I’m hitting may be different than the one the client has.
Thanks, Jesus
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
Awesome!!! That worked like a charm.
Thanks. You guys thought of everything.
Jesus
···
On Mon, Jul 14, 2014 at 12:54 AM, Jesus Malena jesus.malena@gmail.com wrote:
Darn it!!! Why didn’t I see that? I’ll take a look at that and report back.
Thanks for the link.
Jesus
On Mon, Jul 14, 2014 at 12:34 AM, Christoph Blau christoph@4dt.co.za wrote:
Hey There
I hope the link below helps…
https://mathias-kettner.de/checkmk_configvars.html#dyndns_hosts
dyndns_hosts
Hosts listed in this binary configuration list (which is compatible to [bulkwalk_hosts](https://mathias-kettner.de/checkmk_configvars.html#bulkwalk_hosts) ), do never do a DNS lookup but use their host name in all places where otherwise the
IP address would occur (also in the Nagios’ host declarations). That way, a dynamic DNS lookup will be done whenever the host will be contacted.
This is useful in two cases:
- If the host’s IP address dynamically changes (e.g. the host is a dialin router using dynamic DNS updates)
- If the host does not have any IP address (in that case you also have to make sure that the standard host check command is not used).
Kind regards,
Christoph
-----Original Message-----
From: Jesus Malena jesus.malena@gmail.com
To: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: [Check_mk (english)] Akamai DDNS domain IP allocation
Date: Mon, 14 Jul 2014 00:25:45 -0700
Hi all,
Thank you for looking at my question. Currently I’m running into a problem that seems unsolvable. The company I work for uses Akamai’s CDN network to offload traffic from their origin servers. The way the Akamai CDN works is that clusters of servers, that have
different IPs around the globe, provide access to our company’s website static assets faster than our origin servers would. Now the check I would like to create is a check that tries to acquire a specific URL and check for its contents, but I want the check
to also obtain the current IP that it can resolve from the CDN network. Since the first check that Nagios does it to see what IP address it can obtain in order for it to apply a PING check to the host, this IP is setup as part of all the checks thereafter.
I cannot have the static IP setup. Is there anyway within check_mk, OMD, WATO, or something else to force the check to obtain the IP address every time the check is ran? I know this is literally circumventing the way Nagios works.
Why do you want a check like this?
The reason for this is because we have had issues with Akamai’s CDN network, where some of their clusters may have severe packet loss and our website would become inaccessible.
Why not have the check against your origin servers?
Already have a check like this for my origin servers, but I need to have a check that also tests Akamai’s network as well.
Why does it matter if you have a fixed IP for the test?
The issue is that the check may fail for a different cluster of servers that Akamai’s DDNS has provided as a faster route to a client. If this happens, then I can’t tell with a static address whether the check has failed. Some client may report that the site
is failing, but my check would not be able to provide that information because the IP that I’m hitting may be different than the one the client has.
Thanks, Jesus
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en