15/04/2024 8:37 am
Topic starter
Community
Connect with us and enhance your M-Files experience using Unitfly Toolkit for M-Files. Here’s how to get started.
Notifications
Clear all
0
In the logs you can get stuff like Unitfly.ExtensionKit.Module.Modules.TriggerBased.TriggerBasedModule`4
It is not quite clear how you would identify the rule which caused the error. There can be trigger based rules in several modules, and those rules can be listed in between scheduled rules and run once rules. So it becomes quite a puzzle if you have many rules configured.
Could you provide some guidance on how to identify the module and rule in question, or how to configure Logging to provide information in a way that is easier to read and use?
1 Answer
0
19/04/2024 7:56 am
Hi @karl-lausten,
Yes, with the latest logging updates, the logs are a little bit more tricky to read. And for now there are some things that are out of our hands about it.
The first thing I would recommend, especially for file logs, is setting this custom "Log Message Format" under the Advanced settings of the target configuration:
${longdate} [${level:uppercase=true:padding=3}] ${logger} [Task: ${mdlc:TaskID}] [${mdlc:ModuleName}] ${mdlc:Vault} ${mdc:Rules} ${message}${onexception:${newline}${exception:format=ToString:innerformat=ToString:separator=\r\n}}
With this format, you will see logs like this, with the Module and rule name.
Unitfly.ExtensionKit.Module.Modules.TriggerBased.TriggerBasedModule`4 [Task: ] [Property Operations] "Simple PO Rule"
With this custom format, error logs are also more readable and easier to identify.
Kind regards,
Tadej
So, you came to the end of the page. This means you are passionate about technology as we are.
