Risks, Limitations and Assumptions

• 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
  • Authentication Exception

• IBM AIX will send any duplicate/repeat failure alert notification for every 6 hours.

• IBM AIX cannot control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor aix-server resource and can generate alerts based on the threshold values.

• We have provided 22 as default SSH Port value for connecting to aix end device via SSH. Users can modify this value from the application configuration page at any point of time if required.

• The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.

• IBM AIX supports both Classic Gateway and NextGen Gateway.

• Currently we do not have monitoring support for below:

  • Hardware metrics.
  • Programmable Resource Monitoring.
  • Processes (We provided one metric for each process RunningStatus. i.e, ibmaix_server_process_RunningStatus)

• Log files larger than 1GB are not processed.

• Logs are not processed during the first polling request to avoid performance degradation from large data volumes. Log processing begins with the second request, capturing entries generated between the first and second polls.

• Recovery alerts are not generated for expression-based alerts. Recovery alerts are only supported for file-not-found scenarios.

• If the original log file is overwritten or cleared without creating a rotated log file, log entries may be missed during that polling cycle, as the application does not support overwriting of the original log file.

• Support for Multiple Expressions in the same Log File Configuration:
  Multiple expressions can be configured for the same log file by separating them with a semicolon (;) in a single configuration entry. This approach is useful for the configuration when the check type and threshold are the same for all expressions related to that log file.
  

  Note: If different expressions require different Check Type or Threshold values, they must be configured separately as individual entries, even if the log file is the same.
  

  Example - Combined Configuration (Same Check Type and Threshold):

  {
  "Name": "Network Issues",
  "File Name": "/var/log/system.log",
  "Rotated File Name": "/var/log/system.log.1",
  "Expression": "Link Down;Interface Error;CRC Failure",
  "Check Type": "Exists",
  "Threshold": "1",
  "Severity": "CRITICAL"
  }
  

  The above configuration will trigger a separate alert for each expression using a single check type and threshold.
  

  • Separate Configurations Required (Different Check Type or Threshold):
    

    If expressions require different thresholds or check types, use multiple configurations:
    

    {
    "Name": "CRC Error Frequency",
    "File Name": "/var/log/system.log",
    "Expression": "CRC Failure",
    "Check Type": "Not Exists",
    "Threshold": "5",
    "Severity": "WARNING"
  }
  

  {
  "Name": "Link Down Alert",
  "File Name": "/var/log/system.log",
  "Expression": "Link Down",
  "Check Type": "Exists",
  "Threshold": "1",
  "Severity": "CRITICAL"
  }