Logging Archives - Page 2 of 5 - File transfer tool from Limagito

26 Feb
Global logging options in Limagito File Mover
Q: It looks like the logging options are per job. Would it be possible for there to be a global option for logging. This way someone cannot forget to set it up on a single job, and so we can be sure the logging is consistent across jobs. The individual job logging settings could always override the global settings.
A: We are working on a global log setting at this moment (logging to a single log file). You’ll still need to enable a checkbox for each Rule you want to use this Global log setup in. The individual Rule Log file will stay (what we call history logging at the moment).
New Logging Framework in Limagito File Mover starting from version v2023.2.26.0
We replaced our previous logging framework because it was not ideal for the many requests we received regarding to logging. A long time request was a global file logging option which we added together with the new framework. The output result is not 100% identical as with the previous framework but this is something we cannot avoid, every advantage has its disadvantage.
The setup of the ‘Global File Logger’ is available under ‘Global’:
If you want a Rule to write to this Global File Log then please enable this in the Rule Logging setup:
Important, the Log Level and Include&Exclude Filters in the Rule Logging setup below are individual for the selected Rule. The actual Global File Logger also has these Log Level and Include/Exclude Filters options. Both are used to determine if the entry is logged or not. The combination makes it possible to fine tune the entries being send to the Global File Log.
The individual Rule File Log (previously called History Log) is still available. Even both can be used at the same time, for example with different filters and levels.
#FileTransfer #Logging
If you need any info, please let us know.
Best regards,
Limagito Team
By Limagito-Team Logging global log, Global logging
19 Mar
Notificate the windows application log if a certain error occurs?
Q: is it possible notificate in the windows application log if the following error occurs?
17.03.2022 14:29:35 Connect IMAP4, OAuth2 Authorization Failed, Error:
RefreshAccessToken:
..
    fullRequestGetResponse:
      Reading response header…
      responseStatusCode: 400
      Reading response body …
    –fullRequestGetResponse
    finalResponse: {“error”:”invalid_grant”,”error_description”:”AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2021-11-18T10:09:31.0508889Z and was inactive for 90.00:00:00.\..
–RefreshAccessToken
17.03.2022 14:29:35 Connect IMAP4, CK Login to outlook.office365.com Error:
Connect_Imap:
A: Yes this is possible using the following setup.
1. Open ‘Logging’ setup and enable the ‘Clear Log at Rule Begin’ option in the ‘RunTime Log’ tab. Since we are going to use the RunTime log as content to check, we want to keep it unique for each time the Rule is started.
2. Open ‘Rule Events’
3. Enable the ‘On .. Error’ event and enable the ‘Enable Event Log’ option. Add %VSE ( Var String E ) to the ‘Event Log’ setup. Be sure the ‘On Error’ event stays selected during the setup of the other options.
Important, in the ‘Options’ tab:
Enable ‘Include connect errors in on error event’
Enable ‘Use Pascal Script as Event Precondition’
4. Enable ‘Enable Pascal Script’ for the ‘On Error’ event. Add the following ‘Pascal Script’.
Const ctErrorToFind = 'AADSTS700082'; Begin // ... add your code here psExitCode := 0; If Pos(ctErrorToFind, psLRT) <> 0 Then Begin psLogWrite(1, '', 'Write Error To Event Log, ' + ctErrorToFind); psExitCode := 1; End Else psExitCode := 0; // Put LogRunTime information in psVSE var psVSE := psLRT; End.
Summary:
The RunTime Log is cleared each time the Rule is triggered/started.
If an error (connect or others) occurs then we’ll use the Pascal Script option of the Rule Events to check if the content of the RunTime Log includes a certain text ( ‘AADSTS700082’ ).
If this text is available then we’ll put the RunTime Log content into the Windows Application Log.
#Filetransfer
If you need any info about this ‘windows application log’ request, please let us know.
Best regards,
Limagito Team
By Limagito-Team Logging Pascal Script application log, event log, windows application log, windows log
06 Mar
Log Report Summary parameter added in Limagito File Mover
In version v2022.3.6. we added a Log Report Summary parameter: %LRS
Some screenshots will help you to understand how you can use this parameter to send you a summary email after the Rule has finished.
Please select ‘Rule Events’ menu item.
We are going to use the ‘On Success’ Event to trigger an email so enable ‘On Success’ and ‘Enable Mail’.
We added the new Summary parameter %LRS into the body of the email message.
Important, do not forget to enable ‘Trigger mail event after scan’ because the %LRS parameter is only available after scanning source files. You can find this option under the ‘Options’ tab of the ‘Rule Events’ setup.
RunTime Log Result:
Email we received:
#Filetransfer
If you need any info about this ‘Log Report Summary’ option, please let us know.
Best regards,
Limagito Team
By Limagito-Team Logging log, report, summary