KubeMQ Sources
Sources
Standalone Services
Category | Target | Kind | Configuration |
Http | Http | http | |
Messaging | |||
messaging.kafka | |||
messaging.rabbitmq | |||
messaging.mqtt | |||
messaging.activemq | |||
messaging.ibmmq | |||
messaging.nats |
Google Cloud Platform (GCP)
Amazon Web Service (AWS)
Microsoft Azure
Category | Target | Kind | Configuration |
EventHubs | |||
azure.eventhubs | |||
ServiceBus | |||
azure.servicebus |
Targets
Type | Kind | Configuration |
kubemq.queue | ||
kubemq.events | ||
kubemq.events-store | ||
kubemq.command | ||
kubemq.query |
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