# 02\_Average LogSize by LogSource

The below tables makes an attempt to capture the average size of a log by logsource. 

**Please note:** *There could be variations depending on the organizaiton type, asset type, logging options chosen, deployment type and architecture. This table is for a basic reference - more like a rule of thumb.*

| Log Source                            | LogSize (in bytes) |
| ------------------------------------- | ------------------ |
| azure                                 | 710.09             |
| cylance                               | 363.51             |
| dhcp                                  | 102.67             |
| dns                                   | 151.83             |
| entrust                               | 2182.78            |
| epo                                   | 1102.28            |
| fireeye                               | 827.82             |
| fsctcenter                            | 360.29             |
| msad                                  | 1638.15            |
| msexchange                            | 186.49             |
| nessus                                | 2586.53            |
| net\_infrastructure                   | 392.78             |
| net\_lan                              | 193.71             |
| net\_security                         | 161.16             |
| websense                              | 680.60             |
| wineventlog                           | 1251.04            |
| ActiveDirectory                       | 2318.07            |
| DhcpSrvLog                            | 102.17             |
| MSAD:NT6:DNS                          | 150.57             |
| MSAD:NT6:DNS-Health                   | 1240.72            |
| MSAD:NT6:DNS-Zone-Information         | 564.93             |
| MSAD:NT6:Health                       | 650.1              |
| MSAD:NT6:Netlogon                     | 66.83              |
| MSAD:NT6:Replication                  | 233.05             |
| MSAD:NT6:SiteInfo                     | 139.33             |
| MSExchange:2013:Audit                 | 820.23             |
| MSExchange:2013:Database-Stats        | 766.54             |
| MSExchange:2013:DistributionLists     | 2781.24            |
| MSExchange:2013:Folder-Usage          | 116.24             |
| MSExchange:2013:InboxRules            | 2234.74            |
| MSExchange:2013:Mailbox-Usage         | 247.15             |
| MSExchange:2013:MailboxAudit          | 1481.75            |
| MSExchange:2013:MessageTracking       | 764.75             |
| MSWindows:2012:IIS                    | 276.38             |
| Powershell:ScriptExecutionErrorRecord | 3513.35            |
| Powershell:ScriptExecutionSummary     | 249.04             |
| WinEventLog:DFS-Replication           | 509.5              |
| WinEventLog:Directory-Service         | 689.77             |
| cisco:acs                             | 880.61             |
| cisco:asa                             | 161.55             |
| cisco:ios                             | 197.93             |
| citrix:netscaler:syslog               | 286.06             |
| mcafee:epo                            | 1128.8             |
| ms:o365:management                    | 1269.09            |
| ms:o365:reporting:messagetrace        | 484.13             |
| syslog                                | 165.61             |
| syslog\_protect                       | 366.75             |
| websense                              | 678.49             |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.blusapphire.io/log-forwarding/02_average-logsize-by-logsource.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.