PhixFlow Help

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 36 Next »

This page is for PhixFlow administrators who need to monitor PhixFlow activity.

Overview

The System Console provides details on active and completed tasks, files imported and exported by PhixFlow, and the audit trail of changes made to PhixFlow's configuration.  Access to the console, depends on your privileges. Application users, analysis modellers and application designers are notified of errors that prevent their work, but are not notified of system warnings. These are only reported to the console. This means it is important for the PhixFlow administrator to monitor the console for warnings and to determine what action is required.For logs with information related to server and Tomcat traffic, see Server Log Files.

For information about the properties toolbar, and about the sections Parent Details, Analysis Models, Description and Audit Summary, see Common Properties.  For a full list of all the PhixFlow property tabs and windows, see Property Tabs.

Console Information

The following buttons are available at the top of the System Console:

Opens the  System Logging Configuration tab where you can configure the logging for data analysis models and objects.

Opens the task plan list.

There are five tabs that show information about the system:

Task Logs

Active Tasks

Displays a log file summary for each Task Plans that is currently active. Right click on the task and select Show Log File on the context menu to bring up the detailed log file.

Active Tasks can be stopped at any time, if required (this may be useful when testing new models) by pressing the button.

Completed Tasks

Displays a log file summary for each Task Plans that has completed.

The following buttons are available for Completed Tasks:

Apply a filter to the list of Completed Tasks.

Refresh the list of Completed Tasks.

Log file entries are colour coded as shown below:

Red

This log file contains errors

Orange

This log file contains warnings

BlueThe initiator of this log file is currently suspended which is why the task has not run.

The following details are available for each log file:

FieldDescription
StartedThe date and time that this Analysis run was started.
FinishedThe date and time that this Analysis run finished.
Archive TimeThe date and time that this Log File was archived.
NameThe name of the Task which has been run.
CancelledWhether this Analysis run was cancelled by a user.
StatusAn icon will indicate if the stream sets generated by the Analysis run were rolled back from the Stream Sets tab in the system console. See below for details.
TasksThe number of individual Tasks that were run as part of this Analysis run.
MessagesThe total number of messages in the Log File.
InfoThe number of information messages contained in the Log File.
ErrorsThe number of error messages contained in the Log File.
WarningsThe number of warning messages contained in the Log File.
Initiator TypeThe PhixFlow object that was used to launch this Analysis run.
Login nameThe user that stated this run.
ActionWhether the task was a stream action.

To display a log file, right-click its name to open the context menu, then select the Show Log Details.

For stream sets that have been rolled back from the system console Stream Sets tab:

  • If the stream sets generated by an analysis run were rolled back and the analysis repeated (see Tab: Stream Sets, below), the log file entry is displayed with a  button in the Status field. Click  to open the new log file from the rerun of analysis.
  • If the stream sets generated by an analysis run were rolled back, the log file entry is displayed with a  button in the Status field. Click  to open the log file for the rollback.

Tab: Messages

The log messages for the currently selected log file. For each message the following fields are shown:

FieldDescription
TypeThe type of message e.g. INFO, WARN, ERROR or DEBUG
CodeThe numeric error message code.
MessageThe summary message output by the analysis engine.

The following buttons are available for log messages:

Apply a filter to the list of log messages.

Refresh the list of log messages.

Log message details

Double-click on a log message to see further details. In addition to the standard fields, you will also find, on its own tab, the message detail:

FieldDescription
Message DetailDisplays the values of the variables in the parser or detailed stack trace. Populated if an error occurs during analysis or a debug attribute function has been processed.

Tab: Stream Sets

The Stream Sets for the currently selected log file.

If the Stream Sets generated by an Analysis run produced a number of Cycles, and one or more Cycle was rolled back and repeated, then Status field will contain a symbol to indicate whether:

  • this Stream Set was originally generated as part of this Analysis run, but has been moved forward into the log for the Analysis to generate those Stream Sets which were rolled back and repeated.
  • this Stream Set was moved forward into this log from the original Analysis run, along side new Stream Sets generated in this Analysis run - the new Stream Sets are those that were rolled back to be redone from the original log.

The stream set in the console also provides the following buttons:

Roll back the data for each Stream Set, and run Analysis again. Note that when data is rolled back, any subsequent - "downstream" - Stream Sets will also be rolled back. After "reprocessing" a Log File in this way, the Log File will be flagged as "Reprocessed", and no Stream Sets will be associated with it.

Roll back the data for each Stream Set. Note that when data is rolled back, any subsequent - "downstream" - Stream Sets will also be rolled back.

Tab: Imported/Exported Files

A list of files that have been read into PhixFlow by File Collectors or produced by PhixFlow File Exporters. This is found on the Imported/Exported Files tab on the System Console, on the Imported/Exported Files tab in the System Console tab on the System Console, or when viewing the details of an individual file.

By right clicking on a file you can select Show Log File from the context menu. This will bring up the log file of the Analysis run that handled this file - whether as a file imported or exported.

By right clicking on a file you can select Show File Importer/Exporter. This will being up the configuration of the importer or exporter used to handle this file.

Imported/Exported Files

FieldDescription
CycleThe analysis cycle in which the file was processed.
Processed AtDate and time that file was processed
TypeImported or Exported
File Importer/ExporterThe Importer or Exporter used to handle this file.
StatusStatus of the file.
RecordsThe number of records in the file.
FTP SiteThe FTP Site the underlying file handler is attached to, if there is one.
LocationThe location of the file on the file system.

Email Messages

Emails which have been created by the system, from task plans or file exporters.

FieldDescription
Created Date/TimeThe date and time at which the email was created.
Send by Date/TimeThe date and time at which the system will stop trying to send the email.
StatusThe status of the email (ready, sent, failed, etc).
Status MessageA message associated with the status, such as the reason for failure.
Email SubjectThe subject of the email.
Email MessageThe message of the email.
FromThe email address the message is being sent from.
ToA list of the email addresses the email will be sent to.
CcA list of the email addresses the email will be Cc to.
BccA list of the email addresses the email will be Bcc to.
Creator NameThe name of the PhixFlow object which created the email.
Creator TypeThe type of the PhixFlow object which created the email.
Zip all attachmentsWhether any attachments are being added as a zip file.
Zip file name

The name of the attached zip file.

PDF Chore

PDF Chores are the PDF converstion processes that have been created by file exporters.

FieldDescription
Created Date/TimeThe date and time at which the PDF Chore was created.
StatusThe status of the Chore (ready, failed, etc).
Status MessageA message associated with the status, such as the reason for failure.
Creator NameThe name of the PhixFlow object which created the object.
Creator TypeThe type of the PhixFlow object which created the object.
Source File PathThe Path of the source file.
Source File NameThe name of the source file.
Target PathThe Target Directory Expression

Audit Summary

Summary details of audited actions performed on PhixFlow objects.

All Audit Summaries can be viewed from the Audit Summary tab on the System Console. Details for an individual Audit Summary can be viewed by selecting an Audit Summary from this view, and double clicking.

The System Administrator uses Privilege Codes to configure which operations should be audited. If a given privilege has been configured for auditing, PhixFlow tracks details of every associated action and presents these in an Audit Summary.

PhixFlow database administrators can directly query the PhixFlow database for audit information in the audit_summary and audit_detail tables. Audit records that pre-date the upgrade to version 8.1.0 of PhixFlow will not have an entry in the message_text column.

Form: Audit Summary

FieldDescription
Date/TimeThe date/time the audited action took place.
UsernameName of the User who performed the audited action.
Action SummaryA summary description of the audited action.

Audit Details

The Audit Details of an audited action can be viewed with the details of an individual System Console.

Form: Audit Details

FieldDescription
Audit DetailsA detailed description of the audited action.

Forms: Audit Summary for Object

This form shows summary details of audited actions performed on a particular PhixFlow object.

FieldDescription
Date/TimeThe date/time the audited action took place.
UsernameName of the User who performed the audited action.
Original NameOriginal Name of the Object that was changed. i.e. if the name of the object was up dated, this is the original value.
Action DescriptionA summary description of the action.
  • No labels