
Metaplane MonitorResultTrigger
CertifiedFire an execution when a Metaplane monitor's status changes
Metaplane MonitorResultTrigger
Fire an execution when a Metaplane monitor's status changes
Polls the status of a single monitor at each interval and fires only when the status differs from the last-seen value, so an unchanged status never re-fires the trigger every interval. The first evaluation only establishes the baseline status and does not fire.
Fails with a clear error if the monitor has never been run (HTTP 404).
type: io.kestra.plugin.metaplane.MonitorResultTriggerExamples
Fire when a Metaplane monitor's status changes
id: metaplane_on_result
namespace: company.team
triggers:
- id: on_monitor_result
type: io.kestra.plugin.metaplane.MonitorResultTrigger
apiToken: "{{ secret('METAPLANE_API_TOKEN') }}"
monitorId: "3fa85f64-5717-4562-b3fc-2c963f66afa6"
interval: PT5M
tasks:
- id: handle_result
type: io.kestra.plugin.core.log.Log
message: "Monitor result: {{ trigger.status }}"
Properties
apiToken *Requiredstring
Metaplane API token
API token used to authenticate against the Metaplane API. Generate one at https://app.metaplane.dev/account/manage-tokens and store it as a Kestra secret.
monitorId *Requiredstring
Monitor ID
UUID of the Metaplane monitor to watch.
allowConcurrent Non-dynamicboolean
falseSpecifies whether a trigger is allowed to start a new execution even if a previous run is still in progress.
baseUrl string
https://dev.api.metaplane.devMetaplane API base URL
Base endpoint for all Metaplane API calls. Defaults to https://dev.api.metaplane.dev.
interval Non-dynamicstring
PT5MdurationHow often to check the monitor's status
ISO-8601 duration. Defaults to PT5M.
options Non-dynamic
HTTP client options
Optional HTTP configuration (timeouts, proxy, SSL) applied to every Metaplane API call.
io.kestra.core.http.client.configurations.HttpConfiguration
falseIf true, allow a failed response code (response code >= 400)
List of response code allowed for this request
The authentication to use.
io.kestra.core.http.client.configurations.BasicAuthConfiguration
The password for HTTP basic authentication.
The username for HTTP basic authentication.
io.kestra.core.http.client.configurations.BearerAuthConfiguration
The token for bearer token authentication.
io.kestra.core.http.client.configurations.DigestAuthConfiguration
The password for HTTP Digest authentication.
The username for HTTP Digest authentication.
UTF-8The default charset for the request.
java.nio.charset.Charset
trueWhether to enable TCP Keep-Alive extended socket options (TCP_KEEPIDLE, TCP_KEEPINTERVAL, TCP_KEEPCOUNT).
Set to false when running on Windows workers, as these extended socket options are not supported by the Windows JDK and will cause connection failures.
trueWhether redirects should be followed automatically.
REQUEST_HEADERSREQUEST_BODYRESPONSE_HEADERSRESPONSE_BODYThe enabled log.
The proxy configuration.
io.kestra.core.http.client.configurations.ProxyConfiguration
The address of the proxy server.
The password for proxy authentication.
The port of the proxy server.
DIRECTDIRECTHTTPSOCKSThe type of proxy to use.
The username for proxy authentication.
The SSL request options
io.kestra.core.http.client.configurations.SslOptions
Whether to disable checking of the remote SSL certificate.
Only applies if no trust store is configured. Note: This makes the SSL connection insecure and should only be used for testing. If you are using a self-signed certificate, set up a trust store instead.
The timeout configuration.
io.kestra.core.http.client.configurations.TimeoutConfiguration
The time allowed to establish a connection to the server before failing.
PT5MThe time allowed for a read connection to remain idle before closing it.
stopAfter Non-dynamicarray
CREATEDSUBMITTEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPEDBREAKPOINTRESUBMITTEDList of execution states after which a trigger should be stopped (a.k.a. disabled).
when string
trueA condition that determines whether the trigger should run.
A Pebble expression evaluated at trigger time. The trigger fires only when the expression evaluates to a truthy value (true, a non-empty string, a non-zero number). Use this to gate trigger execution on dynamic runtime values such as execution labels, flow variables, or environment conditions.
Outputs
checkedAt string
date-timeTimestamp of the monitor's most recent run, if reported by the API
monitorId string
Monitor ID that was polled
status string
PASSIN_TRAININGNOT_ENOUGH_DATAFAILED_TO_PREDICTINVALID_INPUTERRORFAILUNKNOWNMonitor status when the trigger fired