I’m a longtime Nagios user and infrequent check_mk user who is trying to finally make the leap to check_mk. I’ve been replacing Nagios systems for my customers with check_mk wherever possible. Thus far the changeover has been pretty painless and I’m enjoying WATO far more than I expected I would.
I’ve run into what I expect is a simple problem on a customer deployment. For the life of me I can’t figure it out for myself.
This is a relatively new installation and is using RAW 1.2.8p11. The customer has numerous external websites and my intent is to monitor each of them for response time at the minimum.
I’ve added most of the websites and am getting responses just fine. As I started to add the next site on the list I ran into a little snag. This particular site is internal and hosted on an internal server that is already being monitored using the check_mk agent. The agent gives me connection counts for the site via IIS but that is all. Staff access the portal internally at https://.:444. The internal DNS server handles the URL so that it is the same for internal users and data transfer with external sites. I couldn’t figure out how to make the . check turn up as a check on the internal host so I just set it up as a new external host using . and that worked just fine.
Where I’m struggling is with monitoring both site performance and certificate expiry. I created an Active Check Rule under Check HTTP Service and gave it an explicit host name. That works fine for either checking the URL or checking the SSL certificate but not both. Thinking that wasn’t a major issue, I created a second Check HTTP Service rule, configured it for checking the SSL certificate and gave it the same explicit host. Unfortunately, the host only receives the check of the rule that is first in the list so I can check the URL or I can check the SSL certificate but I can’t seem to check both. Can anyone offer me any advice as to what I’m missing so that I might perform both checks on the same host?
I’m sure my idea is dumb, and I admit that I raced through your explanation.
What about creating 2 hosts - one with the -URL in the name and one with the -SSH in the name. site-URL and site-SSL for example.
Not pretty at all, but then both host names would be different and you would be able to create the checks associated with the new hosts.
I know you created 2 services, but if you created 2 hosts for the services, then I missed that. That would ensure you aren’t overlapping the same host like you are right now, if that’s possible.
I just figured I’d throw that out there for you to chew on, in the event that it’s a hack for a workaround until someone smarter than me provides better advice.
Brian
···
On Oct 19, 2016, at 12:43 PM, Kevin Davison <kdavison@kadencesolutions.ca> wrote:
Hello all;
I’m a longtime Nagios user and infrequent check_mk user who is trying to finally make the leap to check_mk. I’ve been replacing Nagios systems for my customers with check_mk wherever possible. Thus far the changeover has been pretty painless and I’m enjoying WATO far more than I expected I would.
I’ve run into what I expect is a simple problem on a customer deployment. For the life of me I can’t figure it out for myself.
This is a relatively new installation and is using RAW 1.2.8p11. The customer has numerous external websites and my intent is to monitor each of them for response time at the minimum.
I’ve added most of the websites and am getting responses just fine. As I started to add the next site on the list I ran into a little snag. This particular site is internal and hosted on an internal server that is already being monitored using the check_mk agent. The agent gives me connection counts for the site via IIS but that is all. Staff access the portal internally at https://<host>.<extdomain>:444 <https://%3chost%3e.%3cextdomain%3e:444/>. The internal DNS server handles the URL so that it is the same for internal users and data transfer with external sites. I couldn’t figure out how to make the <host>.<extdomain> check turn up as a check on the internal host so I just set it up as a new external host using <host>.<extdomain> and that worked just fine.
Where I’m struggling is with monitoring both site performance and certificate expiry. I created an Active Check Rule under Check HTTP Service and gave it an explicit host name. That works fine for either checking the URL or checking the SSL certificate but not both. Thinking that wasn’t a major issue, I created a second Check HTTP Service rule, configured it for checking the SSL certificate and gave it the same explicit host. Unfortunately, the host only receives the check of the rule that is first in the list so I can check the URL or I can check the SSL certificate but I can’t seem to check both. Can anyone offer me any advice as to what I’m missing so that I might perform both checks on the same host?
Nope, your suggestion seems perfectly logical. In fact that’s my backup plan if no one can point me to a method for making it happen the way my brain wants to see it.
From a monitoring standpoint I have no reason to quibble about having a host to monitor the internal server, a host to monitor the web page, and another host to monitor the SSL. From an organizational standpoint that same brain screams at me that I might be doing something wrong if I had to create three separate hosts to get all of the monitoring that I need.
It just “feels” like maybe I’m reinventing the wheel, repeatedly, because I’m missing a simple piece of information. As Nagios is all manual checks, I’m used to creating a host, and then putting all of my services under that host. I figured that there might be an answer that gets me the monitoring I’m looking for and satisfies my compulsive need to have all of these services under the same host.
I’m sure my idea is dumb, and I admit that I raced through your explanation.
What about creating 2 hosts - one with the -URL in the name and one with the -SSH in the name. site-URL and site-SSL for example.
Not pretty at all, but then both host names would be different and you would be able to create the checks associated with the new hosts.
I know you created 2 services, but if you created 2 hosts for the services, then I missed that. That would ensure you aren’t overlapping the same host like you are right now, if that’s possible.
I just figured I’d throw that out there for you to chew on, in the event that it’s a hack for a workaround until someone smarter than me provides better advice.
I’m a longtime Nagios user and infrequent check_mk user who is trying to finally make the leap to check_mk. I’ve been replacing Nagios systems for my customers with check_mk wherever possible. Thus far the changeover has been pretty painless and I’m enjoying WATO far more than I expected I would.
I’ve run into what I expect is a simple problem on a customer deployment. For the life of me I can’t figure it out for myself.
This is a relatively new installation and is using RAW 1.2.8p11. The customer has numerous external websites and my intent is to monitor each of them for response time at the minimum.
I’ve added most of the websites and am getting responses just fine. As I started to add the next site on the list I ran into a little snag. This particular site is internal and hosted on an internal server that is already being monitored using the check_mk agent. The agent gives me connection counts for the site via IIS but that is all. Staff access the portal internally at https://.:444. The internal DNS server handles the URL so that it is the same for internal users and data transfer with external sites. I couldn’t figure out how to make the . check turn up as a check on the internal host so I just set it up as a new external host using . and that worked just fine.
Where I’m struggling is with monitoring both site performance and certificate expiry. I created an Active Check Rule under Check HTTP Service and gave it an explicit host name. That works fine for either checking the URL or checking the SSL certificate but not both. Thinking that wasn’t a major issue, I created a second Check HTTP Service rule, configured it for checking the SSL certificate and gave it the same explicit host. Unfortunately, the host only receives the check of the rule that is first in the list so I can check the URL or I can check the SSL certificate but I can’t seem to check both. Can anyone offer me any advice as to what I’m missing so that I might perform both checks on the same host?
I have 3 separate services using the active http check for a single
host. One for the ssl cert, two others for specific urls.
I used different values in the ‘Name’ field to give the services
unique names so they don’t clash.
···
On 10/19/2016 2:05 PM, Kevin Davison
wrote:
Nope,�
your suggestion seems perfectly logical. In fact that�s my
backup plan if no one can point me to a method for making it
happen the way my brain wants to see it.
�
From
a monitoring standpoint I have no reason to quibble about
having a host to monitor the internal server, a host to
monitor the web page, and another host to monitor the SSL.
From an organizational standpoint that same brain screams at
me that I might be doing something wrong if I had to create
three separate hosts to get all of the monitoring that I
need.
�
It
just �feels� like maybe I�m reinventing the wheel,
repeatedly, because I�m missing a simple piece of
information. As Nagios is all manual checks, I�m used to
creating a host, and then putting all of my services under
that host. I figured that there might be an answer that gets
me the monitoring I�m looking for and satisfies my
compulsive need to have all of these services under the same
host.
the -URL in the name and one with the -SSH in the name.
�site-URL and site-SSL for example.
Not pretty at all, but then both host
names would be different and you would be able to create the
checks associated with the new hosts.
I know you created 2 services, but if you
created 2 hosts for the services, then I missed that.� That
would ensure you aren�t overlapping the same host like you
are right now, if that�s possible.
I just figured I�d throw that out there
for you to chew on, in the event that it�s a hack for a
workaround until someone smarter than me provides better
advice.
Brian
On Oct 19, 2016, at 12:43 PM, Kevin
Davison <kdavison@kadencesolutions.ca >
wrote:
�
Hello
all;
�
I�m
a longtime Nagios user and infrequent check_mk
user who is trying to finally make the leap to
check_mk. I�ve been replacing Nagios systems for
my customers with check_mk wherever possible. Thus
far the changeover has been pretty painless and
I�m enjoying WATO far more than I expected I
would.�
�
I�ve
run into what I expect is a simple problem on a
customer deployment. For the life of me I can�t
figure it out for myself.
�
This
is a relatively new installation and is using RAW
1.2.8p11. The customer has numerous external
websites and my intent is to monitor each of them
for response time at the minimum.�
�
I�ve
added most of the websites and am getting
responses just fine. As I started to add the next
site on the list I ran into a little snag. This
particular site is internal and hosted on an
internal server that is already being monitored
using the check_mk agent. The agent gives me
connection counts for the site via IIS but that is
all. Staff access the portal internally at�https://.:444 .
The internal DNS server handles the URL so that it
is the same for internal users and data transfer
with external sites. I couldn�t figure out how to
make the . check turn
up as a check on the internal host so I just set
it up as a new external host using
. and that worked
just fine.�
Where
I�m struggling is with monitoring both site
performance and certificate expiry. I created an
Active Check Rule under Check HTTP Service and
gave it an explicit host name. That works fine for
either checking the URL or checking the SSL
certificate but not both. Thinking that wasn�t a
major issue, I created a second Check HTTP Service
rule, configured it for checking the SSL
certificate and gave it the same explicit host.
Unfortunately, the host only receives the check of
the rule that is first in the list so I can check
the URL or I can check the SSL certificate but I
can�t seem to check both. Can anyone offer me any
advice as to what I�m missing so that I might
perform both checks on the same host?
�
–
Kevin Davison�
�
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
HA! I knew I was doing something stupid.
When creating the checks I had put the URL into the check name, which of course gave me two checks with the same name.
That still gives me an internal host check and an external host check but I can live with that now that I know what I was doing wrong.
Thanks for setting me straight!!
I have 3 separate services using the active http check for a single host. One for the ssl cert, two others for specific urls.
I used different values in the ‘Name’ field to give the services unique names so they don’t clash.
On 10/19/2016 2:05 PM, Kevin Davison wrote:
Nope, your suggestion seems perfectly logical. In fact that’s my backup plan if no one can point me to a method for making it happen the way my brain wants to see it.
From a monitoring standpoint I have no reason to quibble about having a host to monitor the internal server, a host to monitor the web page, and another host to monitor the SSL. From an organizational standpoint that same brain screams at me that I might be doing something wrong if I had to create three separate hosts to get all of the monitoring that I need.
It just “feels” like maybe I’m reinventing the wheel, repeatedly, because I’m missing a simple piece of information. As Nagios is all manual checks, I’m used to creating a host, and then putting all of my services under that host. I figured that there might be an answer that gets me the monitoring I’m looking for and satisfies my compulsive need to have all of these services under the same host.
I’m sure my idea is dumb, and I admit that I raced through your explanation.
What about creating 2 hosts - one with the -URL in the name and one with the -SSH in the name. site-URL and site-SSL for example.
Not pretty at all, but then both host names would be different and you would be able to create the checks associated with the new hosts.
I know you created 2 services, but if you created 2 hosts for the services, then I missed that. That would ensure you aren’t overlapping the same host like you are right now, if that’s possible.
I just figured I’d throw that out there for you to chew on, in the event that it’s a hack for a workaround until someone smarter than me provides better advice.
I’m a longtime Nagios user and infrequent check_mk user who is trying to finally make the leap to check_mk. I’ve been replacing Nagios systems for my customers with check_mk wherever possible. Thus far the changeover has been pretty painless and I’m enjoying WATO far more than I expected I would.
I’ve run into what I expect is a simple problem on a customer deployment. For the life of me I can’t figure it out for myself.
This is a relatively new installation and is using RAW 1.2.8p11. The customer has numerous external websites and my intent is to monitor each of them for response time at the minimum.
I’ve added most of the websites and am getting responses just fine. As I started to add the next site on the list I ran into a little snag. This particular site is internal and hosted on an internal server that is already being monitored using the check_mk agent. The agent gives me connection counts for the site via IIS but that is all. Staff access the portal internally at https://.:444. The internal DNS server handles the URL so that it is the same for internal users and data transfer with external sites. I couldn’t figure out how to make the . check turn up as a check on the internal host so I just set it up as a new external host using . and that worked just fine.
Where I’m struggling is with monitoring both site performance and certificate expiry. I created an Active Check Rule under Check HTTP Service and gave it an explicit host name. That works fine for either checking the URL or checking the SSL certificate but not both. Thinking that wasn’t a major issue, I created a second Check HTTP Service rule, configured it for checking the SSL certificate and gave it the same explicit host. Unfortunately, the host only receives the check of the rule that is first in the list so I can check the URL or I can check the SSL certificate but I can’t seem to check both. Can anyone offer me any advice as to what I’m missing so that I might perform both checks on the same host?