Skip to main contentIBM DataPower Operator Documentation

DataPowerMonitor

The DataPowerMonitor is a Custom Resource Definition used to monitor the Pods managed by a DataPowerService StatefulSet.

Spec

Properties

PropertyDescriptionRequiredDefault
lifecycleDebounceMsLifecycle debounce in millisecondsNo10000
peeringRecoveryCheckIntervalMsScan interval for peering checksNo1000
monitorGatewayPeeringBoolean to enable peering managementNofalse

lifecycleDebounceMs

This optional property sets the minimum time (in milliseconds) that must pass after a Pod event for the monitor controller to begin processing the event. If another Pod event occurs during this time, the timer resets.

Defaults to 10000.

peeringRecoveryCheckIntervalMs

This optional property sets the interval (in milliseconds) in which the monitor will scan for stale peers.

Defaults to 1000.

monitorGatewayPeering

This optional property enables (when set true) the Gateway Peering Monitoring feature.

Defaults to false.

Status

Example

No recent Pod events

$ oc get dpm
NAME PHASE LAST EVENT WORK PENDING WORK IN-PROGRESS AGE
example Running false false 5m7s
$ oc describe dpm/example
...
Status:
Conditions:
Last Event:

Work pending

$ oc get dpm
NAME PHASE LAST EVENT WORK PENDING WORK IN-PROGRESS AGE
example Running 2020-09-21T17:18:52Z true false 2m55s
$ oc describe dpm/example
...
Status:
Conditions:
Last Event: 2020-09-21T17:18:52Z

LastEvent

Timestamp of last Pod event in RFC 3339 format.

WorkPending

Boolean to signal that work is pending on this instance.

WorkInProgress

Boolean to signal that work is in-progress on this instance.

Conditions

Currently no conditions are generated. These may be added in future releases.

Phase

The Phase status property provides the current phase of the DataPowerMonitor. The value can be one the following:

  • Pending - The DataPowerMonitor has not yet been initialized.
  • Running - The DataPowerMonitor has been initialized and is monitoring.