The functionality described in this article is available in the meshIQ Platform versions 11.1.1 and later.
For a quick overview of what's new or changed, visit the meshIQ Highlights page for a version-by-version breakdown.
Jump to Section:
Version 11.2 and Earlier
Version 12.x and Later
Version 11.2 and Earlier
Operator policies allow operators to enforce certain policies. Their definitions are merged with regular policy definitions before the result is applied to matching queues.
Operator policies are limited to a small set of arguments. See https://www.rabbitmq.com/parameters.html#operator-policies for more information.
To create an operator policy, do the following:
- Click
on an operator policy viewlet.
- Enter the Operator Policy Name.
- In the Pattern field, enter a regular expression pattern to help match queues to this operator policy by queue name.
- In the Apply To field, indicate the object that the operator policy applies to (for example, queues or exchanges).
- Enter a Priority to determine the relative likelihood of this policy being applied.
- Click OK to save the operator policy.
Pattern | Regular expression pattern used to match queues to this operator policy by name. For example: "^amq\." |
Apply to | Indicates the object that the operator policy applies to (for example, queues or exchanges). |
Priority | The operator policy with the greatest priority applies. |
Status tab
Definitions tab
The list of arguments that can be appended through operator policies is limited. See https://www.rabbitmq.com/parameters.html#operator-policies for details.
Use the fields provided to enter the argument and its value. Then select its data type from the list.
______________________________________________________________________________________________________________
Version 12.x and Later
Operator policies allow operators to enforce certain policies. Their definitions are merged with regular policy definitions before the result is applied to matching queues.
Operator policies are limited to a small set of arguments. See https://www.rabbitmq.com/parameters.html#operator-policies for more information.
Create an Operator Policy
To create an Operator Policy:
- Click the Add Operator Policy
button in the Operator Policy viewlet. The Select Object Path window opens.
- Specify the object path for the new Operator Policy, then click Select path.
- The RabbitMQ Operator Policy Create Window opens.
- In General tab, enter the Operator Policy Name.
- In the Pattern field, enter a regular expression pattern to help match queues to this operator policy by queue name.
- In the Apply To field, indicate the object that the operator policy applies to (for example, queues or exchanges).
- Enter a Priority to determine the relative likelihood of this policy being applied.
- Click Ok to create the Operator Policy immediately. Alternatively, click Schedule to create it at a later time (see Scheduling for details).
Pattern | Regular expression pattern used to match queues to this operator policy by name. For example: "^amq\." |
Apply to | Indicates the object that the operator policy applies to (for example, queues or exchanges). |
Priority | The operator policy with the greatest priority applies. |
Definitions tab
The list of arguments that can be appended through operator policies is limited. See https://www.rabbitmq.com/parameters.html#operator-policies for details.
Click Definitions Description to learn how each argument behaves.
- Click the file button to view the list of available arguments.
- To see the description of a specific argument, click the Info
button next to it.
- Select an argument, provide a value and data type, and then click the
button to add it.
- Repeat this process to add more arguments as needed.
You can also create your own custom properties on the Custom Attributes tab in the Operator Policy Properties window.
Definitions Description
Definition | Key name | Description |
Max Length | max-length | Sets the maximum number of messages allowed in the queue. |
Max Length Bytes | max-length-bytes | Sets the maximum total size (in bytes) of messages in the queue. |
Overflow Behaviour | overflow | Controls how the queue handles excess messages when limits are reached (e.g., drop or reject). |
Message TTL | message-ttl | Specifies the time-to-live for messages before they expire. |
Auto Expire | expires | Automatically deletes the queue after a period of inactivity. |
Delivery Limit | delivery-loot | Sets the maximum number of delivery attempts for a message before it is dead-lettered or dropped. |