KubeMQ Targets

Targets

Standalone Services

Google Cloud Platform (GCP)

Category

Target

Kind

Configuration

Cache

gcp.cache.memcached

Stores/db

gcp.stores.postgres

gcp.stores.mysql

Messaging

Storage

Serverless

Amazon Web Service (AWS)

Microsoft Azure

Category

Target

Kind

Configuration

Stores/db

azure.stores.azuresql

azure.stores.mysql

azure.stores.postgres

Storage

azure.storage.blob

azure.storage.files

azure.storage.queue

EventHubs

ServiceBus

Sources

Type

Kind

Configuration

Middlewares

In bindings configuration, KubeMQ Bridges supports middleware setting for each pair of source and target bindings.

These properties contain middleware information settings as follows:

Logs Middleware

KubeMQ Bridges supports level based logging to console according to as follows:

Property

Description

Possible Values

log_level

log level setting

"debug","info","error"

"" - indicate no logging on this bindings

An example for only error level log to console:

Retry Middleware

KubeMQ Bridges supports Retries' target execution before reporting of error back to the source on failed execution.

Retry middleware settings values:

Property

Description

Possible Values

retry_attempts

how many retries before giving up on target execution

default - 1, or any int number

retry_delay_milliseconds

how long to wait between retries in milliseconds

default - 100ms or any int number

retry_max_jitter_milliseconds

max delay jitter between retries

default - 100ms or any int number

retry_delay_type

type of retry delay

"back-off" - delay increase on each attempt

"fixed" - fixed time delay

"random" - random time delay

An example for 3 retries with back-off strategy:

Last updated