File: WebAPI/rules_1.proto
Request subscription to rules events. If RuleRequest message contains this request, it must contain “subscribe” field with true or false value. Otherwise, the message is considered as invalid.
Note: It does not response with events snapshot. Instead, it starts to send the rule events triggered after subscription. For events snapshot use RuleEventHistoryRequest.
Note: If RESULT_CODE_DISCONNECTED status is received while the subscription is already established, client may lose some events, because they will not be resent later when RESULT_CODE_SUBSCRIBED status is received again. It’s necessary to use RuleEventHistoryRequest request to get events snapshot.
Type: string
Description: Filter events by rule tags. Result contains events, triggered by rules with tags, containing at least one tag from this list. All events are returned if omitted. The number of tags is limited. If the limit is exceeded, the maximum allowed number of tags is provided in the error message.