--- title: "How event summary queries work best practice" slug: "how-event-summary-queries-work-best-practice" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-08-27T19:33:18Z published: 2026-09-07T17:47:17Z canonical: "docs.trellix.com/how-event-summary-queries-work-best-practice" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # How event summary queries work best practice Client events and threat events make up most of the event data in your database. Queries help you track how many events are stored in your database. Event summary queries help you manage any performance problems that these events might cause for your ePO - On-prem server and database. Client events from your agents relate their task status to ePO - On-prem. Items like update complete, update failed, deployment completed, or encryption started are considered client events. Threat events include a virus was found, a DLP event was triggered, or an intrusion was detected. Depending on which products you have installed and which events you are collecting, there might be thousands or even millions of these events in your database.