Fortinet white logo
Fortinet white logo

User Guide

26.1.0

Migrating from instance-level to metric-level flapping configuration

Migrating from instance-level to metric-level flapping configuration

Flapping Metric detection has moved from an instance-level configuration to a metric-level configuration. This change provides more granular control but requires manual reconfiguration.

Old behavior

Flapping detection was configured at the instance level and applied across metrics.

New behavior

Flapping detection is configured per metric, allowing independent thresholds, maintenance period duration, severity, and alert timelines for each metric.

Impact on existing configurations

  • All existing instance-level flapping configurations are deprecated and no longer used.

  • Previous flapping settings are not automatically migrated.

  • Any metrics that relied on the old configuration will not generate flapping incidents until reconfigured using the new metric-level approach.

  • All active flapping incidents are automatically resolved.

Required actions

To continue using flapping detection, reconfigure flapping metric thresholds for each applicable metric using the metric-level flapping configuration described in this guide.

Large deployments

For environments with a large number of instances or metrics, you can use templates to simplify reconfiguration. Templates allow you to apply consistent flapping settings across multiple metrics and reduce manual configuration effort.

Refer to the template configuration section in this guide when migrating large deployments.

Note

Until the new metric-level configuration is completed, flapping detection will not function for metrics that previously relied on instance-level settings.

Migrating from instance-level to metric-level flapping configuration

Migrating from instance-level to metric-level flapping configuration

Flapping Metric detection has moved from an instance-level configuration to a metric-level configuration. This change provides more granular control but requires manual reconfiguration.

Old behavior

Flapping detection was configured at the instance level and applied across metrics.

New behavior

Flapping detection is configured per metric, allowing independent thresholds, maintenance period duration, severity, and alert timelines for each metric.

Impact on existing configurations

  • All existing instance-level flapping configurations are deprecated and no longer used.

  • Previous flapping settings are not automatically migrated.

  • Any metrics that relied on the old configuration will not generate flapping incidents until reconfigured using the new metric-level approach.

  • All active flapping incidents are automatically resolved.

Required actions

To continue using flapping detection, reconfigure flapping metric thresholds for each applicable metric using the metric-level flapping configuration described in this guide.

Large deployments

For environments with a large number of instances or metrics, you can use templates to simplify reconfiguration. Templates allow you to apply consistent flapping settings across multiple metrics and reduce manual configuration effort.

Refer to the template configuration section in this guide when migrating large deployments.

Note

Until the new metric-level configuration is completed, flapping detection will not function for metrics that previously relied on instance-level settings.