FortiMonitor – Ultra Detailed
Installation Guide with Explanations
1. Step 1: Navigate to https://monitor.forticloud.com and sign in with your Fortinet
account.
→ FortiMonitor is a SaaS-based monitoring platform for full-stack visibility.
2. Step 2: If not subscribed, activate FortiMonitor via FortiCloud subscriptions.
→ You must activate it to begin monitoring infrastructure components.
3. Step 3: Launch the FortiMonitor dashboard and configure your organization settings.
→ Initial configuration ensures your organization's data is properly separated.
4. Step 4: Add your first site or data center under 'Infrastructure > Sites'.
→ Sites help you logically separate infrastructure by location or business unit.
5. Step 5: Download the FortiMonitor agent for servers or endpoints (Linux, Windows).
→ The agent collects OS-level metrics and performance data.
6. Step 6: Install the agent using the appropriate command-line options for your OS.
→ Each OS has specific install instructions using package managers or installers.
7. Step 7: During installation, input your organization ID or use the onboarding token.
→ Tokens or org IDs ensure the agent reports to the correct account.
8. Step 8: Validate that the agent is reporting back to the FortiMonitor portal.
→ Successful communication shows up as a green status in the portal.
9. Step 9: Under 'Infrastructure', define device groups or tags for logical grouping.
→ Tagging allows for filtering and customized monitoring policies.
10. Step 10: Add SNMP-enabled devices (routers, switches, firewalls) via IP or hostname.
→ SNMP monitoring enables visibility of network equipment health.
11. Step 11: Set SNMP community strings or v3 credentials as needed.
→ Correct credentials are required to pull SNMP metrics securely.
12. Step 12: Enable synthetic checks such as ping, TCP port, HTTP, and DNS from global
probes.
→ Synthetic monitoring simulates real user actions to test availability.
13. Step 13: Configure notification policies for health, availability, and performance issues.
→ Notification policies define when and how alerts should trigger.
14. Step 14: Add alert recipients and integrate email, Slack, or webhook endpoints.
→ Multi-channel alerts ensure timely notification to responsible parties.
15. Step 15: Set custom thresholds for disk usage, memory, CPU, and application-specific
metrics.
→ Custom thresholds help tailor alerts based on environment behavior.
16. Step 16: Create custom dashboards for visualizing infrastructure health.
→ Dashboards provide real-time visibility for NOC or ops teams.
17. Step 17: Configure reports and alert history under 'Reports > Scheduled Reports'.
→ Reports automate compliance and performance trend documentation.
18. Step 18: Use 'Incident Management' to track downtime and SLA breaches.
→ Incident tracking helps with root cause analysis and uptime reporting.
19. Step 19: Enable role-based access for teams and departments.
→ RBAC limits access and improves security in multi-team environments.
20. Step 20: Periodically review agent health and data collection for completeness.
→ Monitoring agent status ensures full coverage and metric accuracy.