The Decouple session agent decouples the capture pipeline from the socket receiving component and the remainder of the pipeline and throttles traffic spikes using an in-memory queue. For example, if there was a burst of traffic that exceeds the capacity of the remaining pipeline agents, the Decouple session agent queues this burst on the in-memory queue so that no hits are lost.
Unlike Extended Decouple, this session agent operates in-memory only and cannot spool hits to disk when volume is high. Consequently, this session agent is much simpler to configure. There is only one configuration option, the size of the in-memory queue.
Note: If the number of hits in memory exceeds the maximum queue size, subsequent hits are dropped
and lost. This session agent is not intended for any extended queuing periods. It can be used only
to smooth bursts of traffic lasting a minute or two.
Note: Extended Decouple includes additional features and configuration options that are not
available in Decouple session agent. For any envisioned extended queuing that lasts longer than two
minutes, you should consider deploying the Extended Decouple session agent.
Settings
- Display Name values are displayed in TMS, which is the recommended method for configuring session agents.
- Name values are displayed in
TealeafCaptureSocket.cfg.
| Display Name | Name | Description |
|---|---|---|
Max Queue Size |
MaxQueueSize |
Specifies the maximum number of hits the memory queue can hold. Increasing the memory queue size increases competition for memory resources. The default value is 2500. |
Comments
0 comments
Please sign in to leave a comment.