Logs and reports management is the heart of FortiAnalyzer, enabling administrators to monitor network activity, analyze security events, and create meaningful reports for decision-making. This section covers log collection, storage, analysis, and reporting.
Log storage ensures that all network activity and security events are systematically collected and stored for analysis and reporting.
Local Disk Storage:
Network-Attached Storage (NAS):
Defining Retention Periods:
Determine how long logs should be retained based on:
Example Retention Policy:
Automatic Log Cleanup:
Log analysis helps administrators identify trends, detect anomalies, and respond to security incidents efficiently.
Purpose:
Usage:
Advanced Search:
192.168.1.100.Filters:
Purpose:
Steps:
Report management transforms raw log data into structured, visualized insights, helping stakeholders make informed decisions.
Predefined Reports:
Custom Reports:
Using Built-In Templates:
Creating Custom Templates:
Scheduling Reports:
Distribution:
FortiAnalyzer’s Logs and Reports Management capabilities enable organizations to efficiently store, analyze, and interpret log data. By setting up robust storage policies, using advanced analysis tools, and leveraging automated reporting, you can maintain a secure and well-monitored network environment.
Different protocols offer varying levels of performance, reliability, and security:
To improve log transmission efficiency, consider the following optimizations:
Batch Transmission
Log Compression
Priority-Based Log Transmission
To prevent unexpected storage issues, administrators should:
Regularly check disk usage:
diagnose system df
Configure storage alerts:
If FortiAnalyzer requires additional storage, the following methods can be implemented:
Hash Verification
Ensures logs have not been altered.
FortiAnalyzer generates a cryptographic hash for each log file.
To verify log integrity:
diagnose log integrity-check
Read-Only Storage
FortiAnalyzer supports compliance reports for various industry regulations:
These additional details enhance Logs and Reports Management by covering:
Why might traffic logs appear in Log View but not in FortiAnalyzer reports?
Because the logs may not yet be indexed for analytics.
FortiAnalyzer stores logs immediately after receiving them, but reports rely on indexed data. The indexing process prepares logs for analytics and reporting. If indexing is delayed or disabled, the logs will appear in the raw log viewer but not in reports or charts. This often occurs when the device is under heavy log load or when analytics is disabled for certain log types. Administrators should verify that log indexing is enabled and confirm that the indexing process has completed.
Demand Score: 86
Exam Relevance Score: 92
What is the difference between Log View and Analytics in FortiAnalyzer?
Log View displays raw logs, while Analytics uses indexed logs for reporting and visualization.
Log View allows administrators to inspect individual log entries in real time. Analytics, on the other hand, processes indexed logs to generate charts, summaries, and reports. Because analytics relies on indexed data, there may be a delay between receiving logs and seeing them reflected in analytics dashboards. Administrators often confuse the two interfaces when troubleshooting missing report data.
Demand Score: 78
Exam Relevance Score: 90
Why might a scheduled report generate successfully but contain no data?
Because the report dataset does not match available indexed logs or the time range contains no data.
Scheduled reports use predefined datasets and filters. If the selected dataset references log types that are not being collected or indexed, the report will produce an empty output even though the job completes successfully. Another common cause is an incorrect time range or device selection. Administrators should verify dataset filters, log availability, and the report’s time range configuration.
Demand Score: 79
Exam Relevance Score: 88
What is a dataset in FortiAnalyzer reporting?
A dataset is a query that extracts specific log information for reports and charts.
Datasets define how FortiAnalyzer retrieves data from indexed logs. They function similarly to database queries and determine which fields and filters are applied. Reports and charts rely on datasets to generate meaningful insights. Administrators can use predefined datasets or create custom ones for specialized reporting needs. A misunderstanding of datasets is a common reason why reports fail to display expected information.
Demand Score: 71
Exam Relevance Score: 87
Why is log retention important in FortiAnalyzer reporting?
Because reports can only analyze logs that are still stored in the system.
FortiAnalyzer deletes older logs when storage limits are reached according to retention policies and disk quotas. If logs required for a report have already been deleted, the report will not show historical data. Administrators should configure retention settings and disk quotas carefully to ensure required reporting periods are preserved. Organizations that require long-term analysis often increase storage allocations or archive logs externally.
Demand Score: 65
Exam Relevance Score: 82