Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update to GIT-13-8275829

...

Filter application events types. Allowed and/or disallowed event type filtering can be done. The body (parameter) should specify a JSON key/value object that describes the type of event filtering needed. One, or both of the following keys can be designated:<br /><br />"allowed" - Specifies an allowed list of event types
types<br />"disallowed" - Specifies a disallowed list of event typesFurthertypes<br /><br />Further, each of those key's value should be a JSON array that holds zero, or more JSON key/value objects. Each of these objects must contain the following key with an associated value:<br /><br />"type" - The type name of the event to filterThe filter<br /><br />The value must be the string name (case sensitive) of the event type that needs filtering. For example:<br /><br />{ "allowed": [ { "type": "StasisStart" }, { "type": "StasisEnd" } ] }As <br /><br />As this specifies only an allowed list, then only those two event type messages are sent to the application. No other event messages are sent.The <br /><br />The following rules apply:<br /><br />* If the body is empty, both the allowed and disallowed filters are set empty.

...

<br />* If both list types are given then both are set to their respective values (note, specifying an empty array for a given type sets that type to empty).

...

<br />* If only one list type is given then only that type is set. The other type is not updated.

...

<br />* An empty "allowed" list means all events are allowed.

...

<br />* An empty "disallowed" list means no events are disallowed.

...

<br />* Disallowed events take precedence over allowed events if the event type is specified in both lists.

Path parameters

Parameters are case-sensitive.

...