HashiCorp Consul

• Health check went criticalRuns when a health check goes critical, for every service or one, with what the check printed, such as to alert someone. Maintenance mode doesn't start it, and checks already critical when the workflow is turned on don't either.
• Health check recoveredRuns when a health check that was critical or warning is passing again, for every service or one, such as to close an alert.
• Key/value changedRuns when a key under a prefix is created, changed or deleted, with its new value, such as to act on a feature flag or a setting. Keys already there when the workflow is turned on don't start it.

• Get key valueRead a key's value, such as a feature flag or a setting, to use in a later step. A key that isn't set comes back with found false and an empty value rather than failing the step.
• Get keys under a prefixRead every key under a prefix, such as an app's settings in config/app/, as one object, up to 1000 keys.
• Set key valueSet a key's value, such as turning a feature flag on, creating the key if it isn't there. With 'Only if unchanged since', a change someone else made in between is caught rather than overwritten.
• Delete keyDelete a key, or every key under a prefix. Consul keeps no history, so a deleted key can't be brought back.
• List servicesList the services registered in Consul, with their tags, or only those with a tag.
• List service instancesList a service's instances with the address and port to reach each, its tags and its health, or only the healthy ones.
• Get service healthSee how a service is doing for a status report: how many instances are passing, warning and critical, and what each failing check printed.
• List health checksList the health checks that are failing (or critical, warning, passing, or every one) across the datacenter, or for one service or node, with what each printed.
• List nodesList the nodes (machines) in a datacenter with their addresses and whether Consul can reach them.
• Set maintenance modePut a service's instances into maintenance mode, such as before a deploy, so Consul stops sending traffic to them, or take them out again. Works for instances registered with the Consul agent at the connection's address.
• Fire eventSend a Consul user event, such as deploy, to every node or only those running a service. Scripts set up with consul watch on the nodes act on it.
• Check cluster statusCheck that a datacenter's Consul servers have a leader (without one, Consul can't answer or change anything), with its servers.

No actions match that.