Logging

  • 31 Jul

    Rule runtime log doesn’t go back far enough

    Q: We had an issue with the system receiving the file Limagito moves, I want to check the Limagito logs but the rule runtime log doesn’t go back far enough. Are the runtime logs written out to a permanent log somewhere? Do we have to enable logging in anyway?

    A: The RunTime log was not created for this. It is just a ‘short’ visual log about what the File Mover is doing at the moment you use the Remote Tool.

    What you need is our ‘Logging to File’ option (History logging). Please check:
    limagito file mover logging
    – Rule File Log (aka History Log):
    limagito file mover logging setup - Rule runtime log
    Feedback user: Thank You, this is just what I was looking for.

    #mft #filetransfer #filemanagement

    If you need any info about this ‘Rule runtime log’ question, please let us know.

    Best regards,

    Limagito Team

    By Limagito-Team Logging ,
  • 27 Apr

    Centralized log file in industry standard CSV format

    Q: Could a centralized log file in industry standard CSV format be implemented within the file mover software? This would be a log file that *all* jobs could be configured to log to. We have looked at the individual History log files and even though we could probably combine them into a single, daily file to push up to Snowflake – it appears they are not character delimited and only have a space between columns which would be very difficult if not impossible to parse out into individual fields.

    A: We added a global logging option in version v2023.2.26.0.

    Feedback customer:

    We anticipate wanting to ship our log files up to a remote system every 5 or 10 minutes. Since the log file is locked we can’t force this to happen and of course it would not be wise for us to mess with the “active” log file anyway. Instead of (or in addition to) the “Start new log every day”, could there be a “Start new log every __ minutes” and let us adjust the number of minutes before a log file rolls over to a new one?

    Here is the custom message format I was testing with: %{DATETIME}|%{LEVEL}|%{LEVELINT}|%{HOSTNAME}|%{RULEID}|%{MESSAGE}

    It appears the RuleId is always 0, instead of pulling the actual RuleId value
    2023-04-24 15:05:58|INFO|1|CHHMOVER01|0|cerner – XR HIM2 [SFTP] CheckSFTPConnected, SB Request Path after Login: /

    It appears the RuleName is included as a prefix to the message:

    2023-04-24 15:05:58|INFO|1|CHHMOVER01|0|cerner – XR HIM2 [SFTP] CheckSFTPConnected, SB Request Path after Login: /

    Preferably this would be a separate tag (ex. %{RULENAME}) and not a prefix on the message so we could control the output better, for example:

    %{DATETIME}|%{LEVEL}|%{LEVELINT}|%{HOSTNAME}|%{RULEID}|%{RULENAME}|%{MESSAGE} would output a message like this:

    2023-04-24 15:05:58|INFO|1|CHHMOVER01|0|cerner – XR HIM2|[SFTP] CheckSFTPConnected, SB Request Path after Login: /

    A: We added some new options and parameters in version v2023.4.27.0

    Limagito file mover global logging

    We added options to remove certain information like “Rule Name” from the default log message. We enabled “Use Custom Message Format” and added the format from the customer as test.

    limagito file mover Centralized log file

    The following predefined variables can be used to produce a custom message output format:

    • DATETIME : Date & time log item occurs
    • DATE : Date log item occurs
    • TIME : Time log item occurs
    • LEVEL : Level or Eventype
    • LEVELINT : Level as numeric
    • MESSAGE : Message sent to logger
    • ENVIRONMENT : Customizable variable (normally Production, Test, etc)
    • PLATFORM : Customizable variable (normally Desktop, Mobile, etc)
    • APPNAME : Customizable variable (by default set as filename without extension)
    • APPVERSION : Application file version
    • APPPATH : Application run path
    • HOSTNAME : Computer name
    • USERNAME : Logged user name
    • OSVERSION : OS version
    • CPUCORES : Number of CPU cores
    • THREADID : Thread ID log item set
    • RULEID : RuleID number
    • RULENAME : RuleName
    • LOGSOURCE : Description of log source

    Logging result:

    limagito file mover runtime log

    TODO:

    We anticipate wanting to ship our log files up to a remote system every 5 or 10 minutes. Since the log file is locked we can’t force this to happen and of course it would not be wise for us to mess with the “active” log file anyway. Instead of (or in addition to) the “Start new log every day”, could there be a “Start new log every __ minutes” and let us adjust the number of minutes before a log file rolls over to a new one?

    #FileTransfer #Logging #MFT

    If you need any info  about this ‘Centralized log file’, please let us know.

    Best regards,

    Limagito Team

    By Limagito-Team Logging ,
  • 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’:

    Limagito File Mover Global Logging menu item

    Limagito File Mover Global Logging setup

    • If you want a Rule to write to this Global File Log then please enable this in the Rule Logging setup:

    Limagito File Mover Rule Logging menu item

    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.

    Limagito File Mover 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.

    Limagito File Mover Rule File Log

    #FileTransfer #Logging

    If you need any info, please let us know.

    Best regards,

    Limagito Team

     

    By Limagito-Team Logging ,
1 2 3 4 5
SEARCH