34.79. listSystemEvents

Name
listSystemEvents
Description
List all system events for given server. This includes *all* events for the server since it was registered. This may require the caller to filter the results to fetch the specific events they are looking for.
Available since: 10.8
Parameters
  • string sessionKey
  • int serverId - ID of system.
Return Value
  • array:
    • struct - action
      • int failed_count - Number of times action failed.
      • string modified - Date modified. (Deprecated by modified_date)
      • dateTime.iso8601 modified_date - Date modified.
      • string created - Date created. (Deprecated by created_date)
      • dateTime.iso8601 created_date - Date created.
      • string action_type
      • int successful_count - Number of times action was successful.
      • string earliest_action - Earliest date this action will occur.
      • int archived - If this action is archived. (1 or 0)
      • string scheduler_user - available only if concrete user has scheduled the action
      • string prerequisite - Pre-requisite action. (optional)
      • string name - Name of this action.
      • int id - Id of this action.
      • string version - Version of action.
      • string completion_time - The date/time the event was completed. Format ->YYYY-MM-dd hh:mm:ss.ms Eg ->2007-06-04 13:58:13.0. (optional) (Deprecated by completed_date)
      • dateTime.iso8601 completed_date - The date/time the event was completed. (optional)
      • string pickup_time - The date/time the action was picked up. Format ->YYYY-MM-dd hh:mm:ss.ms Eg ->2007-06-04 13:58:13.0. (optional) (Deprecated by pickup_date)
      • dateTime.iso8601 pickup_date - The date/time the action was picked up. (optional)
      • string result_msg - The result string after the action executes at the client machine. (optional)
      • array additional_info - This array contains additional information for the event, if available.
        • struct - info
          • string detail - The detail provided depends on the specific event. For example, for a package event, this will be the package name, for an errata event, this will be the advisory name and synopsis, for a config file event, this will be path and optional revision information...etc.
          • string result - The result (if included) depends on the specific event. For example, for a package or errata event, no result is included, for a config file event, the result might include an error (if one occurred, such as the file was missing) or in the case of a config file comparison it might include the differenes found.