RabbitMQ Integration

Apinizer keeps its API Traffic transaction logs on Elasticsearch by default.

However, sometimes in institutions, since the disk resources that Apinizer will need are not met, or different strategic management concerns it may be requested to send the logs to 3rd party tools/systems instead of Elasticsearch.

In this case, RabbitMQ settings can be activated to transfer logs to target system.

The picture below shows the RabbitMQ settings:

The fields used for RabbitMQ configuration are shown in the table below.

Field	Description
Host	The host to use for connections
Virtual Host	The virtual host to use when connecting to the broker
Port	The port to use for connections
Authentication	Enables for configuring Authentication
Username	The AMQP user name to use when connecting to the broker
Password	The password to use when connecting to the broker
Connection Timeout	The TCP connection timeout, in milliseconds; zero for infinite
Requested Channel Max	Initially requested maximum channel number; zero for unlimited
Requested Frame Max	The initially requested maximum frame size, in octets; zero for unlimited
Requested Heartbeat	The initially requested heartbeat interval, in seconds; zero for none
Use SSL Protocol	Enables for configuring TLS
SSL Protocol	Method for configuring TLS. Pass in the TLS protocol version to use, e.g. "TLSv1.2" or "TLSv1.1"
Channel Exchange	The exchange to publish the message to
Channel Routing Key	The routing key
BasicProperties For Message	AMQP Basic Properties for setting metadata of each request
Enabled Fields	With this setting, the fields to be sent to RabbitMQ in the transaction log can be selected. Size limitations can be set for long text fields in the logs.
Max Undelivered Message Count in Database	If the request to RabbitMQ is failed, the log records which can not be sent to RabbitMQ are stored in the local database. This setting defines the number of log entries that can be kept in the database. The default value is set to 10,000.