Fortinet FortiGate extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Gain insights into the performance of your Fortinet FortiGate solution.
Get started
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.
Activate the extension in your environment web-UI using the in-product Hub, provide the necessary device configuration, and you’re all set.
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
- Aim to monitor the health state and performance of their FortiGate Fortinet devices
- Seek analysis support for security, IT, and network administrators
- 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
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.
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.
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
| Metric name | Metric key | Description |
|---|---|---|
| Connectivity | fortigate.connectivity | Connectivity |
| CPU usage | fortigate.cpu.usage | CPU usage |
| Disk log rate | fortigate.disk.log.rate | Disk log rate |
| Disk usage | fortigate.disk.usage | Disk usage |
| Memory usage | fortigate.memory.usage | Memory usage |
| Sessions | fortigate.sessions | IPv4 Sessions |
| IPv6 Sessions | fortigate.sessions.ipv6 | IPv6 Sessions |
| Metric name | Metric key | Description |
|---|---|---|
| Ping availability | fortigate.ping.availability | Ping availability |
| Ping packets in | fortigate.ping.packets.in | Ping packets in |
| Ping packets out | fortigate.ping.packets.out | Ping packets out |
| Ping packets lost | fortigate.ping.packets.lost | Ping packets lost |
| Ping RTT | fortigate.ping.rtt | Ping RTT |
| Metric name | Metric key | Description |
|---|---|---|
| Interface bytes in | fortigate.interface.bytes.in.count | Interface bytes in |
| Interface bytes out | fortigate.interface.bytes.out.count | Interface bytes out |
| Interface errors in | fortigate.interface.errors.in.count | Interface errors in |
| Interface errors out | fortigate.interface.errors.out.count | Interface errors out |
| Interface packets in | fortigate.interface.packets.in.count | Interface packets in |
| Interface packets out | fortigate.interface.packets.out.count | Interface packets out |
| Interface speed | fortigate.interface.speed | Interface speed |
| Interface status | fortigate.interface.status | Interface status |
| Metric name | Metric key | Description |
|---|---|---|
| Tunnel bytes in | fortigate.tunnel.bytes.in.count | Tunnel bytes in |
| Tunnel bytes out | fortigate.tunnel.bytes.out.count | Tunnel bytes out |
| Tunnel proxy bytes in | fortigate.tunnel.proxy.bytes.in.count | Tunnel proxy bytes in |
| Tunnel proxy bytes out | fortigate.tunnel.proxy.bytes.out.count | Tunnel proxy bytes out |
| Tunnel proxy status | fortigate.tunnel.proxy.status | Tunnel proxy status |
