Risks, Limitations & Assumptions

  • App can handle Critical/Recovery failure alert notifications for:
    • Connectivity Exception
    • Authentication Exception
  • Duplicate/repeat failure alert notifications are sent every 6 hours.
  • App cannot control monitoring pause/resume actions based on alerts.
  • Metrics can monitor HP-UX Cluster resources and generate alerts based on threshold values.
  • Minimum supported version for Latest snapshot metric: nextgen-14.0.0
  • Full discovery support requires gateway version 15.0.0 or above.
  • App is not compatible with Cluster Gateway.
  • Default SSH Port: 22 (modifiable from configuration page)
  • Component-level thresholds can be configured per resource.
  • Template Applied Time is shown only if collector profile version is 18.1.0 or higher.
  • Currently unsupported monitoring features:
    • Hardware metrics
    • Programmable Resource Monitoring
    • Processes (We provided one metric for each process RunningStatus. i.e, hpux_server_process_RunningStatus)
  • Log File Monitoring is supported only for HP-UX Server type.
  • For log monitoring, we expect below JSON payload as input.
    • "Name" can be any string used to identify individual log configuration.
    • "File Name" 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: C:\Program Files (x86)\Vistara\Agent\log\Age.?t.log
      • Matches: Agent.log, Ageat.log, ...
    • "Rotated File Name" is similar to file name field but specifying the rotated file. This field is optional.
    • "Expression" can be any valid string or regular expression used to specify the search string. It's a mandatory field.
    • "Check Type" can be either "exists" or "not exists" (case insensitive).
    • "Threshold" can be any valid integer. Alert will be generated in case of specified threshold breach happens.
    • "Severity" 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": ""
  }
]
  • Logs larger than 1GB are not processed.
  • First request logs are skipped to avoid performance issues; processing starts from second poll.
  • No recovery alerts for expression-based alerts; recovery only for file-not-found alerts.
  • Alerts may not trigger if the log file contains fewer than 10 lines, because the checksum calculation uses the first 10 lines and the last 10 lines.

Support for Multiple Expressions in the Same Log File Configuration

You can configure multiple expressions for the same log file by separating them with a semicolon (;) in a single configuration entry. Use this approach when all expressions share the same check type and threshold for that log file.

Note: If different expressions require different check types or thresholds, configure them as separate 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"
}

This configuration triggers a separate alert for each expression, using the same check type and threshold.

Separate Configurations Required (Different Check Type or Threshold)

If expressions require different thresholds or check types, create multiple configuration entries:

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

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