Repository Updates Log
|
Repository Updates Log |
|
|
Repository updates log allows to view the list of updates from GUS, that includes detailed information on updated products revisions. To view the repository updates log 1.Select the Administrating item in the main menu of the Control Center. 2.In the opened window, select the Log of repository updates item of the control menu. 3.Window with the registered actions table opens. To configure viewing the log, specify on the toolbar the time period during which the actions have been performed. For this, you can select one of the proposed periods or specify arbitrary dates in the calendars which are opened on clicking the dates fields. Click Refresh to display the log for the selected dates. 4.To show only events of specific types in the table, click •Show all events—log table displays all events listed below. •Show successful update sessions—log table displays update sessions during which GUS connection has been successfully established, a new revision has been found on GUS and successfully downloaded into the Server repository. •Show unsuccessful update sessions—log table displays update sessions during which GUS connection has been successfully established, a new revision has been found on GUS but downloading of this revision failed. •Show unsuccessful connections with Dr.Web GUS—log table displays during which GUS connection has not been established or has been terminated before getting the information on revisions on GUS. 5.The log table contains the following data: •Start—date and time when an update of the certain product has been started from the GUS. •Finish—date and time when an update of the certain product has been finished from the GUS. •Product name—name of the repository product that was downloaded or was requested to be downloaded. •Update result—repository update result. Contains brief information on successful update completion or error reason.
•Initial revision—number of the revision (revisions are numbered according to the date of their creation) that was the last for this product before update process started. •Revision from update—number of the revision (revisions are numbered according to the date of their creation) that was was downloaded during update process. •Updated files—brief information on the changed files. Is given in the following format: <files number> - <actions on files>. •Initiator—system that initiated the update process: ▫Launched from the command line—update was initiated by administrator via the corresponding console command. ▫Launched by Task Scheduler—update wad launched according to the task in the Dr.Web Server schedule. ▫Interserver update—update was received via the interserver connection from the main Server. This initiator presents only in case of multiserver configuration of anti-virus network with propagation of update via the interserver connections. ▫Launched from the Control Center—update was launched by administrator via Dr.Web Security Control Center, from the Repository State section. ▫Repository import—update was loaded by administrator in the Repository Content section of the Control Center. •Administrator—login of the Server administrator. It is specified if the action was initiated directly by administrator. •Network address—IP address from which the action execution has been initiated. It is specified only in case of an external connection to the Server, particularly via the Control Center or via the Web API. •Repository folder—folder name of the Server repository that was modified according to the update process. 6.To view the detailed information on a certain update, click the line of this update. This opens the window with table on product files changed during selected update. The following information is given fro each file: File name, File hash, Size and State. 7.If necessary, you can export data for the specified period into a file. To do this, click on the the following buttons on the toolbar:
|
on the toolbar. In the drop-down list, select the necessary options:
