How is the agent-side queue managed when using InTrust Deployment Manager real-time collections (4294401)

Chatee ahora con Soporte

Regresar

Comentarios enviados

¿Este artículo solucionó su problema?

Seleccionar calificación

Título

How is the agent-side queue managed when using InTrust Deployment Manager real-time collections
Descripción

How is the agent-side queue managed when using InTrust Deployment Manager collections?
Causa

InTrust Deployment Manager collections (aka real-time collections) have their own send queue managed by the agent. This is not the same mechanism as used with traditional scheduled collections which used agent-side cache. Instead, collections use same mechanism as real-time monitoring feature.
Resolución

InTrust Deployment Manager collections (aka real-time collections) use same mechanism as real-time monitoring feature. The default queue size is 1024 MB and should not be increased. By default, Domain Controllers and Member Servers forward events every 1 minute. Workstations forward events every 7 minutes.

How does send queue work:

1. InTrust Agent packs event data into repository files and then puts the files in the send queue which are then sent to their destination. The send queue is located here:

\data\tasks\\tpvc\messages.1

2. If max queue size is reached due to InTrust server being unavailable for long periods of time, the oldest data is purged from the queue as new data is added.
Información adicional

Starting in InTrust 11.3 default queue size will be increased from 128 MB to 1024 MB.

Comentarios enviados

¿Este artículo solucionó su problema?

Seleccionar calificación

Contenido recomendado

Historial del artículo:: Creado el: 11/3/2015
Última actualización: 5/27/2024

Título