You can now use the status of your check_mk service as the host status. If you check your hosts with the “nc” jump host command.
Once I removed the -‘J’, it worked perfectly. I found that when I was testing from my monitoring server by putting the command in on the CLI, it would hang for a minute or so until it finally timed I removed the ‘-J’ from the original command posted. įrom: checkmk-en on behalf of Lists Wednesday, J3:05:35 PM.I suspect it may not be possible to do that? What is the command check_mk uses to ping? Maybe I can just relicate that command?
Sorry, another question on this: if I have hosts behind the NAT firewall that I want to just know if they are up or not (e.g., switches, VMware hosts), what command could I put in the jump box Datasource program to doĪ ping and just return “OK” if it is up? I tried:īut the host shows as down. I assume the quotes around the netcat command would be necessary? Is it better to use single quotes or double quotes? Using this, if I want to monitor remote hosts via check_mk that are behind a NAT router, if I don’t want to setup a whole monitoring server on the client’s network (to do Distributed monitoring), all I need is a Linux box and a single port forward Coming across that blog post I posted earlier certainly made it much less daunting, and I am quite happy and impressed right now Just on a side note, I had looked into this before when I was moving from “pure” Nagios to OMD (and now Check_MK Raw), and it had been suggested to use datasource and jump box, but I found it a little “daunting” Then I can probably apply it to a different host tag that I can create like “Datasource” or “NAT Only” or something. For now, I will create a Datasource program for each client, but I can probably edit the command to replace the client’s server host name withĪ variable, and just keep the user name consistent. I will do the same thing for any other clients that I setup jump boxes for. So basically any host I add, if the “Client” host tag matches the value for this client, In my Datasource Program I created for this client, I am applying based on my “Client” host tag I created a while ago. I found that when I was testing from my monitoring server by putting the command in on the CLI, it would hang for a minute or so until it finally timed out. it is really just to try to keep things consistent In case the “proper” SSH port is already being used to access something else (the firewall itself or another server). This is not to obscure the SSH service but because I anticipate doing this at other clients, so I want to standardise the port used, I am using external port 8022 to go to jump box behind my client’s firewall. Ssh -p 8022 -tt -o StrictHostKe圜hecking=no “/bin/nc $HOSTNAME$ 6556” OK, so just to followup and close this out, here is the final command I ended up going with that is working for me:
Geschäftsführer: Peer Heinlein – Sitz: Berlin HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
#Windows ssh tunnel through jumpbox install
You could install netcat on the jumphost and the call ssh as datasource If I am correct about the above, how would I use the jump box+datasource To: Re: Datasource Program / Jump Box question įrom: checkmk-en on behalf of Robert Sander Wednesday, J11:51:01 AM.
In the datasource program entry, with the variable being replaced by whatever I enter for the IP/Hostname when I create the host. Thanks, Robert! It looks like that netcat command will work on a Linux host as well (I just tried it from my monitoring host to a local Linux host we monitor), so, I could actually change the jump host command to:
0 kommentar(er)
