Fortinet FortiGateFortinet FortiGate
Gain insights into the performance of your Fortinet FortiGate solution.
Extension
- Product information
- Release notes
Overview
The FortiGate Monitoring extension uses HTTP API requests to gather data remotely, ensuring that data from your Fortinet FortiGate devices is collected every minute and analyzed continuously by our platform. This tool offers insights that extend beyond simple charting, covering the extensive features and capabilities of the FortiGate devices. Our unified analysis pages provide deep insights into both the health and performance of your network security infrastructure, while our analytics engine sets baselines and alerts for critical indicators. With a topology-first approach, our AI-driven analytics can explore and correlate detected issues across components to pinpoint root causes.
This is designed for users who:
- Aim to monitor the health state and performance of their FortiGate Fortinet devices
- Seek analysis support for security, IT, and network administrators.
This enables you to:
- Monitor your network security infrastructure with an all-encompassing dashboard
- Detect network anomalies and establish alerting mechanisms for them
- Monitor traffic, errors, and connectivity to the devices
- Implement proactive measures to prevent security incidents and service degradation
Use cases
- Monitor Fortinet FortiGate infrastructure and resource utilization
- Understand the health and performance of firewall, interfaces, tunnels, and proxies
- Enable alerting on detected anomalies
Get started
Activate the extension in your environment web-UI using the in-product Hub, provide the necessary device configuration, and you’re all set.
Details
The extension package contains:
- Python data source code for metric ingestion and problem detection.
- Topology and relationship definitions for physical (FortiGate devices, network interfaces) and logical (Tunnels, proxies) components of the Fortinet FortiGate platform.
- Dashboard offering monitoring overviews and a high level status overview
- Alerts covering component availability
- Unified Analysis pages for each entity
This extension is built on top of the new Extension 2.0 Framework.
Compatibility information
The extension retrieves the list of interfaces and available interfaces from the two endpoints below:
/monitor/system/interface/select?scope=global/monitor/system/available-interfaces/select
As such, queries to CMDB endpoints are not performed and include_vlan parameter is not added to the query.
This may lead to not all virtual interfaces being collected during data acquisition process.
Extension content
Feature sets
Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Tunnel bytes in | fortigate.tunnel.bytes.in.count | Tunnel bytes in | Byte |
| Tunnel bytes out | fortigate.tunnel.bytes.out.count | Tunnel bytes out | Byte |
| Tunnel proxy bytes in | fortigate.tunnel.proxy.bytes.in.count | Tunnel proxy bytes in | Byte |
| Tunnel proxy bytes out | fortigate.tunnel.proxy.bytes.out.count | Tunnel proxy bytes out | Byte |
| Tunnel proxy status | fortigate.tunnel.proxy.status | Tunnel proxy status | State |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Ping availability | fortigate.ping.availability | Ping availability | Percent |
| Ping packets in | fortigate.ping.packets.in | Ping packets in | Count |
| Ping packets out | fortigate.ping.packets.out | Ping packets out | Count |
| Ping packets lost | fortigate.ping.packets.lost | Ping packets lost | Count |
| Ping RTT | fortigate.ping.rtt | Ping RTT | MilliSecond |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Interface bytes in | fortigate.interface.bytes.in.count | Interface bytes in | Byte |
| Interface bytes out | fortigate.interface.bytes.out.count | Interface bytes out | Byte |
| Interface errors in | fortigate.interface.errors.in.count | Interface errors in | Count |
| Interface errors out | fortigate.interface.errors.out.count | Interface errors out | Count |
| Interface packets in | fortigate.interface.packets.in.count | Interface packets in | Count |
| Interface packets out | fortigate.interface.packets.out.count | Interface packets out | Count |
| Interface speed | fortigate.interface.speed | Interface speed | Unspecified |
| Interface status | fortigate.interface.status | Interface status | State |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Connectivity | fortigate.connectivity | Connectivity | Percent |
| CPU usage | fortigate.cpu.usage | CPU usage | Percent |
| Disk log rate | fortigate.disk.log.rate | Disk log rate | Percent |
| Disk usage | fortigate.disk.usage | Disk usage | Percent |
| Memory usage | fortigate.memory.usage | Memory usage | Percent |
| Sessions | fortigate.sessions | IPv4 Sessions | Count |
| IPv6 Sessions | fortigate.sessions.ipv6 | IPv6 Sessions | Count |
Related to Fortinet FortiGate
Full version history
Full version history
Bug fixes:
- Fixed an error condition where trying to ping an unreachable host caused an exception and did not raise a problem event.
Full version history
Breaking changes:
- This is a new
MAJORrelease. Not compatible with previously published versions. - Any existing monitoring configurations will have to be recreated.
Bug fixes:
- Inability to filter down interfaces due to the
splitlinesattribute bug.
Improvements:
- Highly improved parallel execution.
- Option to enable problem alerts on: Login failure, Ping failure, system status retrieval failure.
- More detailed Ping metrics.
- Improved topology. Available interfaces are tracked separately from Interfaces.
- Robust fastcheck procedure that makes sure that the ActiveGate can actually connect to the device before proceeding with monitoring.
- Ability to control which data to collect using Feature Sets.
Features:
- Limit data collection to specific Interfaces, Tunnels, and Proxies.
- Connectivity metric now measures whether we were able to successfully retrieve the system status information.
- Availability metric measures percentage of the ping packets that have succeeded.
- Both IPv4 and IPv6 sessions are now monitored.
- Metrics for Interface speed and status.
Full version history
Initial release