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.
  • 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.
  • 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
  • Need below json payload as input for log monitoring:
    • Name: This can be any string used to identify individual log configuration.
    • File Name: It is a combination of folder path and file name. Folder path should contain the exact path for the file as prefix. File name can be any valid string or regular expression. In case of file not found with specified file name, alert will be generated with the severity specified by the user.
      Example 1: C:\Program Files (x86)\Vistara\Agent\log\Age.?t.log
      Matches: Agent.log, Ageat.log ,..
    • Rotated File Name: It is similar to file name field but specifying the rotated file. This is a optional field.
    • Expression: This can be any valid string or regular expression used to specify the search string. It is a mandatory field.
    • Check Type: This can be either “exists” or “not exists”(case insensitive).
    • Threshold: This can be any valid integer. Alert will be generated in case of specified threshold breach happens.
    • Severity: It is used to specify the alert type to be created in case of expression found. Possible values are CRITICAL, WARNING, INFO, and OK (case insensitive).

Log file configuration:

 [
  {
  "Name":"",
  "File Name":"",
  "Rotated File Name":"",
  "Expression":"",
  "Check Type":"",
  "Threshold":"",
  "Severity":""
  }
]

  • 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 consider the latest logs ( logs generated between first and second polls) from the second request and process accordingly.
  • No recovery alerts are generated for expression related alerts. we will get recovery only for file not found alerts.