Risks, limitations & assumptions

• If you are upgrading the integration from a lower version to 3.1.0 or above, ensure that you update the fields File Systems, Mount Points and Processes in the configuration, if needed. Else, they will be loaded with default values.
• 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
• Solaris OS Server uses the provided IPAddress/hostname, credentials for SSH communications.
• Solaris OS Server will send duplicate/repeat failure alert notification for every 6 hours.
• Solaris OS Server cannot control monitoring pause/resume actions based on above alerts.
• Metrics can be used to monitor Solaris Server resources and can generate alerts based on the threshold values.
• We have provided 22 as default SSH Port value for connecting to Solaris 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.
• Full discovery support requires gateway version 15.0.0 or above.
• Solaris OS Server supports both Classic Gateway and NextGen Gateway.
• Currently we do not have monitoring support for below:
  • Hardware metrics
  • Processes (We provided one metric for each process RunningStatus. i.e, solaris_os_server_process_RunningStatus)
• Use the below commands to fetch max limits, see To configure shared memory and semaphores on Solaris for more information.

Max Limit Commands

Semaphore ID Limit: echo seminfo_semmni/D | mdb -k

Shared memory ID Limit: echo shminfo_shmmni/D | mdb -k

Message Queue ID Limit: echo msginfo_msgmni/D | mdb -k

• We do not process logs of size greater than 1GB.

• we do not process logs for the first request, since it leads to performance issues due to huge data. we will consider the latest logs ( logs generated between first and second polls) from second request and process accordingly.

• No recovery alerts are generated for expression related alerts. we will get recovery only for file not found alerts.

• If the original log file is overwritten or cleared without a rotated log file, the app miss log entries during that polling cycle, as it 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"
  }