Red Hat Bugzilla – Bug 156311
reporting: no way of getting reports out of Satellite on actions taken
Last modified: 2010-01-29 22:48:49 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041215 Firefox/1.0 Red Hat/1.0-12.EL4
Description of problem:
Even though you can go into the individual jobs and see when they were completed this is very tedious when you need to report on 300+ jobs. There needs to be a reporting engine or something. Not sure if this is a bug or just an enhancement request.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Reports do not exist
Actual Results: Reports do not exist
Expected Results: Reports do not exist
Sorry for the lack of feedback, this is treated as an enhancement and prioritized.
Talk to Rich/Tom/Todd for more details on this.
Satellite 530 GA will provide API call:
system.listSystemEvents - details following. I wonder if this meets the need, or if us providing an example API script using this call with others is requested/required?
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.
* string sessionKey
* int serverId - ID of system.
o 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"
+ 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.
Available since: 10.8
2 months in a needinfo state. I feel we have with this API meet the request and since 5.3.0 is GA'd, moving this to closed, current release.