Risks, Limitations & Assumptions

  • As of now the application only supports discovery and monitoring for FTDs managed by FMC or FDM.
  • The integration can manage critical/recovery failure alerts for the following two scenarios when the user activates App Failure Notifications in the settings:
    • Connectivity Exception (ConnectTimeoutException, HttpHostConnectException, UnknownHostException)
    • Authentication Exception (UnauthorizedException)
  • Cisco Firepower Threat Defense will not send any duplicate/repeat failure alert notification until the already existed critical alert is recovered.
  • Cisco Firepower Threat Defense cannot control monitoring pause/resume actions based on above alerts.
  • Metrics can be used to monitor FTD resources and can generate alerts based on the threshold values.
  • Event/Alert polling will start only if the user enables Event/Alert Polling in configuration.
  • Possible values of Event/Alert Severity filter configuration property are kWarning, kCritical, kInfo.
  • We have given sample mappings to map FTD Severity with OpsRamp Severities as part of the Event/Alert Severity Mapping configuration file. You can modify them as per their use case at any point of time from the SDK application configuration page. Possible OpsRamp Severities are Critical, Warning, Ok, Info.
  • Support for Macro replacement for threshold breach alerts (i.e, customisation for threshold breach alert’s subject, description).
  • No support of showing activity logs.
  • The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
  • Support for the option to get Latest snapshot metric.
  • Cisco Firepower Threat Defense is not compatible with Cluster Gateway.
  • Interfaces under FTD are represented as Network devices in Opsramp.
  • Cisco Firepower Threat Defense supports both Classic Gateway and NextGen Gateway.