KubeMQ Sources

Sources

Standalone Services

Category	Target	Kind	Configuration
Http	Http	http	Usage
Messaging
	Kafka	messaging.kafka	Usage
	RabbitMQ	messaging.rabbitmq	Usage
	MQTT	messaging.mqtt	Usage
	ActiveMQ	messaging.activemq	Usage
	IBM-MQ	messaging.ibmmq	Usage
	Nats	messaging.nats	Usage

Google Cloud Platform (GCP)

Category	Target	Kind	Configuration
Messaging	Pub/Sub	gcp.pubsub	Usage

Amazon Web Service (AWS)

Category	Target	Kind	Configuration
Messaging
	AmazonMQ	aws.amazonmq	Usage
	MSK	aws.msk	Usage
	SQS	aws.sqs	Usage

Microsoft Azure

Category	Target	Kind	Configuration
EventHubs
	EventHubs	azure.eventhubs	Usage
ServiceBus
	ServiceBus	azure.servicebus	Usage

Targets

Type	Kind	Configuration
Queue	kubemq.queue	Usage
Events	kubemq.events	Usage
Events Store	kubemq.events-store	Usage
Command	kubemq.command	Usage
Query	kubemq.query	Usage

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:

bindings:
  - name: sample-binding 
    properties: 
      log_level: error
    sources:
    ......

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:

bindings:
  - name: sample-binding 
    properties: 
      retry_attempts: 3
      retry_delay_milliseconds: 1000
      retry_max_jitter_milliseconds: 100
      retry_delay_type: "back-off"
    sources:
    ......