Exit Points and Backend Naming

The agent discovers a RabbitMQ backend exit point when your application sends a message to the queue using the BasicPublish()

By default, the agent names the RabbitMQ backend for the exchange parameter of the BasicPublish()

For example:

model.BasicPublish("MyExchange", "", false, false,
basicProperties, Encoding.UTF8.GetBytes(message));

In this case the agent names the queueMyExchange.RabbitMQ Backend Name

You can refine the backend name to include some or all segments of the routing key. To configure RabbitMQ naming you must be familiar with your implementation RabbitMQ exchanges and routing keys. See RabbitMQ Exchanges and Exchange Types.

Refine backend naming

Register thermqsegmentsnode property. For instructions on how to set a node property, see App Agent Node Properties.

Name: rmqsegmentsDescription: "Configure RabbitMQ naming to include routing key segments."Type: IntegerValue: <integer>The routing key is a string. The agent treats dot-separated (".") substrings of the routing key as segments. Set the value to an integer that represents the number of routing key segments to include in the name.

In the following example the routing key is "abc.def.ghi". Set the rmqsegments value to "2" to name the queue "MyExchange.abc.def".

model.BasicPublish("MyExchange", "abc.def.ghi", false, false,
basicProperties, Encoding.UTF8.GetBytes(message));

After you save the node property, the Controller sends the configuration to the agent. After some time the RabbitMQ backend shows up with the new name.