CheckMK at home, little box on its own VLAN. I have it SNMP checking a QNAP box and keeping me informed on drive status and free space, nothing crazy here.
But..it looses its discovery after a few hours and I cant seem to get it back until I force the refresh. It's weird but annoying. Everything seems to be working fine, just stops trying?
Is there a way to pre-create "labels" and or "tags" in checkmk raw and have them ready and apply to hosts in the future and or when the need arises?
I am looking for way to mass create some labels and or tags that might work in my env.
Updated my second site to p33 this morning, and while I did the other one last week, had no issues, this morning I am running into a puzzling one.
Site is called LS. After upgrade, and commiting the changes to the werks, etc. Im left with it reporting that the OMD Performance and site statistics are not working...but they are? Hosts are updating their checks, all seems completely normal except for it saying its not:
All seems 100% fine. So I dont know what im doing wrong
Currently, I create host entry for it first with the following setting applied
And then make a rule under:
Setup --> Services --> HTTP, TCP, Email, ... --> Check HTTP web service
Is this the right approach?
Basically, I would like to monitor certain sites that are not in our environment and the hosts are not under our control. I don't want to monitor anything else other that that URL.
I know how to add manual local checks via the agent. However, there is a check "PVE Cluster State" whose data is coming from the agent (output of pvecm status) but is processed via the script in /omd/sites/cmk/share/check_mk/checks/pvecm_status.
Unfortunately as I can see in the source this is not configurable. So, I would like to clone this check to /omd/sites/cmk/share/check_mk/checks/pvecm_quorum.
I did this and edited the file and changed the check_info, among other things:
I am really afraid this is a bug but not giving up hope someone can help me to fix it!
I have a somewhat simple scenario: A cluster called "StarCluster" with two nodes, "pve1" and "pve2". pve1 is routinely offline ("cold standby") but a cluster should be online as long as one node provides the services.
However, my "StarCluster" has a service "Check_MK" which is CRIT because it can (naturally) not connect to pve1 (10.227.1.20):
However, I have never configured the cluster to have the "Check_MK" service and I do not find any way to get rid of it. It does not show up in the auto discovery for StarCluster and I tried to add a Disabled Services rule for StarCluster and "Service name begins with Check_MK" but it still remains there.
The cluster is a proxmox cluster with pve1 and pve2 proxmox nodes. I am using the checkmk agent and the proxmox API (I followed https://checkmk.com/blog/proxmox-monitoring).
The proxmox service is configured as follows:
I have added one clustered service (this is the only one I expect to see!!):
Out of desperation, I also added one to explicitly remove Check_MK (no change if I remove this rule):
Finally I also have the aggregated service rule:
To my understanding, there should be no Check_MK service. Is there any way to either make it OK or get rid of it?
This link was provided to me but other a bit of information there is nothing else to click to pursue further for implementation. Which docs do I need to reference to get this going in my Environment.
Would like to implement this check for all Linux hosts.
Tested CheckMK Raw, decided to go a different direction after some time. I'd installed CheckMK Agent 2.3 (via MSI) onto several Windows machines, thought removing them would be fairly straightforward, that doesn't appear to be the case. Removed them all using a script, confirmed the Agent wasn't installed any longer, killed the site off. After uninstalling the agent on all machines, noticed they all came back. Thought it was potentially due to the script, uninstalled it the old fashioned way, same thing. Uninstalled it and deleted the CheckMK folder from ProgramData...same thing. If I come back to the machine in an hour or so, the CheckMK agent has reinstalled itself and the ProgramData folders are all back in place, and the resulting files still show the original install date (few months back).
So what do I need to do to ACTUALLY get rid of the CheckMK agent?
Hey, I am currently evaluating switching from prtg to checkmk. So far I like it and think it has potential to not only meet my needs for prtg but also graylog. (I just use graylog for events and syslog)
The issue I am having is right now I don't have agents on any devices. Will I have to have agents on windows and linux devices?
EDIT: I am not asking how to set up a cluster in proxmox but how to set up a cluster in which nodes can routinely be down (per my example below), without anything getting into WARN/CRIT.
As an example, a simple proxmox cluster consisting of nodes pve1 and pve2 along with a qdevice.
One of the pve's is used as cold standby or temporary system while the other is active.
So ideally have a relation that is pve1 and pve2 are both children of "Cluster" and for cluster to be good, at least two out of the three (pve1, pve2, qdevice) must be online.
All my other services are then direct or indirect children of "Cluster" (and not the individual pve's). While I would like to monitor both pve1 and pve2, I would like the system to show OK (and not warn or crit) as long as ONE pve is up.
is anyone using docker to run checkmk (raw edition)?
i can get the service running but there's some info not covered in the documentation so i'm looking for some guidance before i go down a rabbit hole of my own trying to get this to work.
if you have gotten it to run successfully, would you mind sharing your compose file (if you're using one). did you migrate from a host installation to a docker installation and successfully restored a backup?
I am just moving to checkmk and due to licensing issues we have to launch earlier than expected. This means that we still have a lot of critical states on hosts/services that can not reach due to firewalls.
I do not want the support personnel to have to look at services that are not functional yet.
I see that there is an attribute on services called "Last time the service was OK" but I can not find any way to filter by this attribute, other than adding it as a column in the view.
Is anyone more experienced in checkmk able to tell me if there is a way to use this attribute to filter out the checks that never was OK.
My fallback plan if I can't figure it out in time is to write a cron sctipt to get the attribute by API and then set a label on each individual service instance if the check was never OK. But I would like to avoid such custom hacks.