Connect Job - SS&E External Logging

Connect Job Overview

Modern versions of Connect include an auto-updater that automatically updates the Connector and direct access to view logging from within Student Success & Engagement.

  • This allows SS&E Administrators to view the most recent Connect Job Application Log.
  • As soon as the Connect Job completes, the most recent Connect2 Application Log is transfered from the Connect server and visible from within SS&E.

Connect External Logging

The Connect log is accessed from External Logging (SS&E Administration - Advanced  - External Logging found here). Here, you can either view/filter on external logging entries or view the most recent Application log by clicking on "Connect2 Full Log" in the top right corner.

If External Logging is empty and the link to the Application log does not work, then your SS&E application has most likely not yet been implemented with the modern version of Connect/Accelerate.

  • Searching for application.log on the Connect server will find the log(s) for the Connect job.
  • For schools that are already on Connect/Accelerate and do not see External Logging, instructions on how to update to the latest Connect version (that includes external logging and the auto-updater task) can be found here.

Connect Job Frequency

The Connect Job Application log is created and generated during the Connect job run on the Connect server.

By default, the Connect job is scheduled to run as a Scheduled Task every six hours, and (for clients that are updated with the latest Connect version) the application.log is uploaded to S3 every time the Connect job completes.

External Logging Error Search/Filtering

Filtering on External Logging by Log Level "Error" will return errors that occurred during the Connect job.

  • Drilling down into an error message will display the error message details.
  • If the error message details are not helpful enough, searching the Application Log may find additional information.

When searching the Connect2 Full Log Application log, searching by a keyword or a specific data stream using Ctrl-F can help quickly check for additional information.

  • By searching the Application Log for the data stream displayed in External Logging and/or the message displays in the error message details, there may be some additional helpful information displayed in the log immediately before the message occurred.

Survey Integration External Logging

Survey integration logs are also visible in External Logging. 

External Logging Log Levels

The following log levels are useful and meaningful for Student Success & Engagement clients:

INFO

The INFO level designates informational messages that highlight the progress of the Connect Job as it processes the different data streams used to pull data from the SIS to Student Success & Engagement.

WARN

The WARN log level is a potentially harmful issue that will most likely not prevent the program from running.

  • An example of a Warning Message is a null data stream or a data feed that is not implemented.
  • In most cases, this indicates that for some reason the specific data stream is not configured to import data from the SIS as it has been determined that the specific data feed contents either are not relevant for the institution or that the data feed is not yet implemented for some reason.

ERROR

The ERROR level indicates that the Connect Job encountered an error that is preventing one or more SS&E data stream imports from properly functioning.

  • Since the Connect job runs on the Connect Server, any Connect errors included in External Logging must first be evaluated to determine if they are relevant.
  • If the data is supposed to be imported from the SIS, the errors must be resolved so that the correct data will successfully import into SS&E.

Other

The following log levels display in External Logging, yet are not in use by SS&E:

  • TRACE 
  • DEBUG
  • FATAL

External Logging  - Connect Job Error Examples

Object xyz is not found in dfs.tmp

  • This error indicates that something has recently changed in the source data. 

SYSTEM ERROR: IOException: There is not enough space on the disk

  • This error indicates that the Connect server is out of space.

VALIDATION ERROR: Schema [[dfs, root]] is not valid with respect to either root schema or current default schema

    • This error usually indicates that something changed on the Connect server and is causing the drill service to to be unable to write files to S3. For additional resolution tips, click here.

 

 

 

 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more
How to Contact Support
There are many ways to reach out! Click here for our support options.
Watermark Academy
Click to access the Watermark Academy for consultation, training, and implementation companion courses.