ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

What factors may affect latency of incident vs. notification via UI or email?

book

Article ID: 160642

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

What factors may affect latency of incident vs. notification via UI or email?

Resolution

Factors vary and will include:

1. Physical resources and .msg load on the Monitor.
    Includes msg/incident size and quantity, cpu, memory, disk speed, disk layout and fragmentation.

2. Network latency and AVAILABLE bandwidth between Monitor and Manager.

3. Physical resources and .msg load on the Manager.
    Includes msg/incident size and quantity, cpu, memory, disk speed, disk layout and fragmentation.

4. Network latency and AVAILABLE bandwidth between Manager and database.

5. Physical resources and .msg load on the Database box (if 3 tier)
    Includes msg/incident size and quantity, cpu, memory, disk speed, disk layout and fragmentation.

6. Network latency and AVAILABLE bandwidth between Manager and MTA.

7. Physical resources and msg load on the MTA.

8. Network latency and AVAILABLE bandwidth between MTA and email recipient.


Powered by Wolken Software