Welcome Guest! To enable all features please Login or Register.
Options
Go to last post Go to first unread
ipadmin  
#1 Posted : Monday, January 23, 2017 8:25:06 PM(UTC)
ipadmin

Rank: Administration

Groups: Administrators
Joined: 8/17/2015(UTC)
Posts: 19

Was thanked: 1 time(s) in 1 post(s)
Inaport logging lets you create log files to record overall statistics, as well as detailed information, for each job or batch of jobs . With Inaport logging activated you can:

  • check that jobs have run as scheduled
  • check individual jobs for errors
  • trace data as it flows through the integration process
  • notify administrators of errors on an exception basis


Inaport has standard logging functions for everyday job management, however it also has more powerful logging functions for complex and challenging situations.


Setting up a log file for an Inaport job

Setting up a log file for a particular job is very easy, and it’s strongly recommend that it be done for every profile. By default the log file will contain:

  • Management information such as the profile run, start and stop time.
  • Overall statistics for the run – how many records processed, how many match or match fail, how many written.
  • Detailed statistics for each entity or table in the target – how many rows inserted/updated/deleted, how many errors.
  • Optionally, if source records have data errors or match problems, the row can be added to the log file.


To set up a file, simply enable logging on tab 6, and specify the location of the file:

Logging - Standard Setup

As well as specifying the log file, you can optionally:

  • Write Start and Complete to System Application Log
  • Send an email when the job is complete. The email will have the overall job statistics by default, and you can optionally attached the full log file.



Naming the log file using expressions

The log file path can be just a fixed file name; for example:

Code:
C:Inaport logsMyLogFile.txt


However, the log file name can actually be a full Inaport expression. In the screen shot above, the log file name is:

Code:
C:Inaport_logs#P #D_#T.log


This is the recommended name form. The components “#P #D_#T” are replaced with respectively:
  • #P – the full name of the profile
  • #D – the current date, in the format ‘yyyyMMdd’. For example: 20151004 for October 4, 2015
  • #T – the current time, in the format ‘THHmmss’ For example: ‘T143021’ for 2:30 and 21 seconds PM


The net result is that every log file has the full name of the profile and the date/time the job ran. This makes it straightforward to scan a log directory for a particular job run.

You are not, however, restricted to this format. The name text can be built up using Inaport expressions, such as nowstr() which can be used to format a date/time however you wish:

UserPostedImage

As a result of being able to include expressions in the file name, Inaport users can make sure that files are automatically named in a way that makes identification and sorting easy.


Customizing the content of Inaport log files

By default, the standard log file will have:

  • Overall statistics for the run – number of records processed, how many resulted in inserts or updates on the target, start/stop time and overall time
  • Optionally, records that had data errors or match fail errors
  • Detailed statistics for each table targeted – how many matches or match fails, how many inserts/updates/deletes.


For many purposes, the standard information is sufficient. However, there are some scenarios where it may be important to add more information to the log.

For example, suppose you are importing leads from a marketing automation system. As you import the leads, it may be important to know specifically which leads are new to the system, and which already existed and so update existing data. In this case, it can be useful to modify the standard Inaport log files.

Inaport provides the log() function, that allows you to write your own information to the log file. For example:

Code:
log("Write this to log file")


will cause the text to be written to the log file, in the area where information about record errors is written.

Although this feature used in isolation has limited use, it can be combined with Inaport’s ability to execute functions after a record is updated, with information about the update:

Logging in the post operation tab

Here you can see the PostOperation tab being used to specify a couple of expressions.

  1. The first row says “If the record was inserted, write “Lead: xxx@yyy.com was inserted” to the log file
  2. The second row says “If the record was updated, write “Lead: xxx@yyy.com was updated” to the log file.


This is how the results look in the log file for some sample data:

UserPostedImage

Using this approach, you can can see the progress of leads through multiple jobs.

Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2017, Yet Another Forum.NET
This page was generated in 0.181 seconds.

Notification

Icon
Error