NSF Log handling capacity

May I know how much capacity worth of logs it can handle? Is it calculated in terms of quantity (eg. 1000 logs a day) or capacity (eg. 20Gb a day)?

Hello,

for capacity or quantity logs, there are no specific explaination in nsf_v8.0.85_Associate
but you can auto-delete it with configuration you'd like (in example: 365 days or 7 days)
you also can select other options with percentage of disk:
Delete the earliest log if disk usage reaches .....%

by default you can export latest log 100 entries, you can edit it up to 10.000 entries

hope this help you

Hi,

Sangfor Network Secure Key Features & Capabilities ; NSF-1050A-I · 10 Gbps · 6 Gbps ; NSF-1100A-I · 20 Gbps · 12 Gbps ; NSF-3100A-I · 30 Gbps · 20 Gbps

Sangfor’s log handling capacity is typically measured in terms of both quantity and capacity. For example, the Sangfor Cyber Command solution can handle millions of logs per day and the capacity is also measured in gigabytes per day. Here are some specifics:

Daily Log Quantity: Depending on the model, Sangfor Cyber Command can handle between 216 million to 378 million logs per day.
Disk Consumption: The disk consumption ranges from 112 GB to 200 GB per day.
This dual measurement ensures that the system can manage a high volume of logs while also considering the storage capacity required.

The capacity for handling logs is typically calculated in terms of data volume (e.g., 20GB per day) rather than quantity.

Hi,

The ideal capacity depends on several factors including but not limited to the following:

- number of devices or systems sending logs to the server
- level of logging (debug, info, warning, error) enabled on those devices/systems (higher logging levels generate more logs)
- average size of individual log messages
- retention period for compliance or troubleshooting purposes

Hi,
The ability to manage logs is usually measured in terms of data volume (for instance, 20GB per day) rather than the number of logs. The optimal capacity is influenced by a variety of factors, which include but are not limited to:
The count of devices or systems that are transmitting logs to the server
The logging level (debug, info, warning, error) that is enabled on these devices/systems (note that higher logging levels produce more logs)
The average size of each log message
The retention duration required for compliance or troubleshooting needs

Hi,
Usually is calculated in terms of capacity.

The capacity of a log management system is typically measured in terms of data volume, such as gigabytes (GB) per day, rather than the quantity of individual logs. This metric reflects the total amount of log data the system can ingest, store, and process within a specified time frame. For instance, a system might be capable of handling 20 GB of log data per day. This approach acknowledges that log entries can vary significantly in size and complexity, making data volume a more practical measure of the system's capabilities to manage and analyze logs effectively.

The capacity of logs that an EDR solution can handle is typically measured in terms of volume, usually in gigabytes (GB) or terabytes (TB), rather than quantity (number of logs). For example, some EDR solutions can handle up to 50 GB of log data per day, while others can handle up to 100 TB of log data per month. This capacity is often referred to as the "log ingestion rate" or "log collection capacity". The exact capacity depends on the specific EDR solution, the type and complexity of the data being collected, and the processing power of the underlying infrastructure.