Administering Durable Subscribers

You can search, monitor, and delete durable subscribers on the Universal-Messaging-instanceName > Administration > Durable Subscribers page in Command Central. You can also browse events on a specific durable subscriber and purge events for shared durable subscribers.

Attribute	Description
Name	The name of the durable subscriber.
Channel	The name of the channel to which the durable subscriber belongs.
Durable type	The type of durable subscriber (Shared, Serial, or Durable).
Last event ID	The event ID of the last successfully consumed event.
Outstanding events	The number of events outstanding for a particular durable subscriber. Note: The outstanding event count displayed for a non-shared durable is only an estimate.
Last read time	The last date and time when the durable subscriber read, committed, or rolled back an event.

Attribute	Description
Name	The name of the durable subscriber.
Channel	The name of the channel to which the durable subscriber belongs.
Durable type	The type of durable subscriber (Shared, Serial, or Durable).
Cluster-wide	Whether the durable subscriber is on a channel that is part of a Universal Messaging cluster.
Persistent	Whether the durable subscriber is persistent. Persistent durable subscribers retrieve the last event ID consumed before the Universal Messaging server instance was restarted.
Selector	Events are filtered based on the defined selector.

Attribute	Description
Last event ID	The event ID of the last successfully consumed event.
Total events	The number of outstanding events for the durable subscriber.
Pending events	The number of outstanding events waiting for a commit or a rollback.
Last read time	The last date and time when the durable subscriber read, committed, or rolled back an event.
Last write time	The last time the durable was written to. Typically, this is the last time an event was added to the durable subscriber.

Attribute	Description
ID	The connection ID.
Mode	The client subscription mode (subscription based or getNext).
Max pending	The window size specified by the client.
Acknowledged	The total acknowledged events.
Rolled back	The total rolled-back events.
Pending	The event queues waiting to be acknowledged or rolled back.
Last read time	The last time the session acknowledged, rolled back, or read an event from the durable subscriber.

The Browse events page displays the event list and lets you to browse events for a durable subscriber. Events are displayed in the order of old to new. A maximum of 1000 events are displayed in the table with a maximum combined size of 10 MB. For example, if two events of size 10 MB and 100 MB are present for the durable subscriber, only the event of size 10 MB is displayed, and no other events are displayed. Click Browse events to refresh the events displayed in the table.

Attribute	Description
Event ID	A unique ID to identify the event.
TTL (ms)	Specifies how long (in milliseconds) each event is retained. Note: You can publish an event with a specified TTL only on queues and channels of type Mixed. Events on queues and channels of type Persistent or Reliable use the TTL set on store level and ignore any event-level TTL.
Tag	The tag information of the event if an event tag exists.
Event data	The content of the event. For Protobuf events, the content is a JSON string.
Event size (bytes)	The size of the event in bytes. The event size is the total size of the event that is the sum of the event data and event properties.
Event properties	The event properties represented as key-value pairs.
Persistent	Whether the event is persistent or not.

When you select an event ID in the table, you can view additional details about the event including the type of event (persistent, transient, or Protobuf event), a hexadecimal view of the event data, an ASCII representation of the event data, the header and properties of the event. If the event is a Protobuf event and its tag matches the name of a Protobuf file descriptor that has already been uploaded on the channel, the ASCII representation of the event is the decoded Protobuf content in JSON format.

Use the Bulk purge option to purge events in bulk for a durable subscriber. You can purge events by providing an event range and event filter, or purge all the events.