All integrationsMonitoring

Checkmk

Act on Checkmk monitoring from workflows: list problems, acknowledge them with a ticket number, schedule downtime around a change, run a check now, and add, change or delete hosts from an asset system and activate the changes.

actions
14
triggers
3

Triggers

Start a workflow when something happens in Checkmk.

  • Host went downRuns when a host goes DOWN or UNREACHABLE in Checkmk, for every host or those in a host group, such as to open a ticket. Hosts in downtime don't start it, and hosts already down when the workflow is turned on don't either.
  • Service went critical or warningRuns when a service goes CRIT or WARN in Checkmk (or gets worse, from WARN to CRIT), with what its check said. Services in downtime or on a host that is down don't start it.
  • Problem recoveredRuns when a host that was DOWN or UNREACHABLE is UP again, or a service that was CRIT, WARN or UNKNOWN is OK again, such as to close a ticket.

Actions

Steps a workflow can run in Checkmk.

  • List problemsList the problems going on now as rows: hosts down or unreachable and services critical, warning or unknown, with what each check said, worst first.
  • Get host statusGet a host's state (UP, DOWN or UNREACHABLE), its address and groups, how many of its services are OK, warning or critical, and its service problems.
  • Get service statusGet a service's state (OK, WARN, CRIT or UNKNOWN), what its check said and whether someone has acknowledged it.
  • Acknowledge problemAcknowledge a host's or a service's problem with a comment, such as a ticket number, so Checkmk shows someone is on it and stops notifying about it.
  • Schedule downtimeSchedule downtime for a host, or some of its services, for a change window, so their problems don't notify anyone.
  • Remove downtimeEnd a host's or service's downtime now, by its ID from 'Schedule downtime', or every downtime on the host or service.
  • Reschedule checkRun a host's or a service's check now, such as after a fix, rather than at its next interval, and get the new result.
  • Create hostAdd a host to Checkmk in a folder, with its IP address, such as from an asset system. Discover its services and activate changes to monitor it.
  • Update hostChange a host's IP address, alias or labels, or move it to another folder. Blank fields are left as they are; activate changes to apply.
  • Delete hostDelete a host from Checkmk, such as when a server is retired. Activate changes to stop monitoring it.
  • Discover servicesScan a host for its services, such as its disks and network interfaces, and monitor the new ones, as Checkmk's Service discovery page does.
  • Activate changesActivate the pending changes, such as hosts added or deleted, so Checkmk monitors them that way, and wait until it's done.
  • List hostsList the hosts in a folder, with their IP address, labels and state.
  • List host groupsList the host groups, with their hosts and how many are down.

Automate Checkmk with Lodol.

Connect Checkmk, then hand Lodol the job in Slack, Claude or ChatGPT.

Free plan, no credit card