Each sender plugin has its own queue with the messages it needs to process and eventually send to the endpoint.

1Gateway uses RabbitMQ as the internal queueing system. Sender plugins include the queue configuration fields.

Queue name

Name of the queue used to process the messages for a specific sender plugin. This name and the messages that go through the queue can be viewed in RabbitMQ.

To access RabbitMQ go to: http://localhost:15672/#/queues. The initial username and password are 1gateway/1Gateway$.

Topics

The topic defines which messages should go on the sender plugin queue. The format is: origin_endpoint.message_type.phase

  • Origin endpoint: the endpoint defines the configured name for the system that originated the message.
  • Message type: type of message that this plugin can proces. Notice that the message type described here is before mapping.
  • Phase: future use.

To define multiple topics for a queue, separate them with a semi-colon.

Example of a sender plugin that accepts metrics from Zabbix, alarms from Solarwinds and tickets from ServiceNow. In most cases, the sender plugin needs to contain a mapper for each of these message types.

Example

zabbix.NormalizedMetric.*;solarwinds.NormalizedAlarm.*;servicenow.NormalizerdIncident.*
CODE



Queues cannot change dynamically. If the topic needs to change, either change the queue name aswell to create a new queue or delete the current plugin queue for the change to take effect.