Question
Infosys
AU
Last activity: 26 Sep 2018 1:29 EDT
Unwanted log messages in Robotics Runtime Log
Hi Team,
We are getting the below unwanted error entries in Runtime Log. Though they are not related to any application issues, they will generate a bunch of service desk tickets for one of our clients which is cumbersome to clean up.
I have tried and even a bare minimum robotics project seems to generate the below errors in log.
Can you let me know how to get rid of those issues. Thanks!
Error | 08:14:54.194 AM | 1 | STA | AutomationBroker | | | AutomationBrokerServicesFactory not found
Error | 08:14:54.853 AM | 4 | MTA | ApplicationFramework | | | Error parsing StartMyDay section of RuntimeConfig. 'FileLocation' section has missing or empty 'value' attribute.
Error | 08:14:55.116 AM | 4 | MTA | Runtime Application | | | Error reading Shutdown setting. Unexpected Setting: ''
Pegasystems Inc.
US
Why do you not turn off logging altogether?
incessant
IN
Could you please elaborate more on this.
Infosys
AU
But we would need logging for detecting and analyzing unexpected errors while running the automation.
Pegasystems Inc.
US
Enabling logging has a direct effect on performances, recommendation is that logging be enabled when necessary. Logs files have a short life span and are only temporary.
If logging is required, suggest adjusting the level of information be reported. This can be accomplished by updating the LogLevel for each category (LogCategories) in the RuntimeConfig.xml.
Infosys
AU
Thank you! That clarifies a lot.
But still, the logs that I am concerned about are error logs. How would I stop them from showing up? I am thinking it might be something related to the way the project is setup? For example, if we take the AutomationBroker not found log, how do I suppress it? Why does that Broken even matter when I am not using that? Same goes with rest of the logs (like StartMyDay etc.,)
Coforge
IN
Below link might help you
https://collaborate.pega.com/question/what-does-playback-mean-robotics-runtimelog
Accepted Solution
Pegasystems Inc.
US
In the RuntimeConfig you may control the LogLevel by the Category as mentioned earlier. If you set the LogLevel to 0 for the categories that you want to suppress they should not log.
For the errors you are seeing, do you have the AutomationBroker Factory in your solution? If so, you should be able to remove it or disable it. The second error relates to the StartMyDay setting in your RuntimeConfig. Update the FileLocation key and that should go away. The third one would require looking at your solution and how shutdown is happening.
Lastly, items with the Error MsgType are not what I would generate tickets from. Exceptions are real issues that require attention. Error is a classification that is used throughout the product to ensure you have visibility to these issues with reduced logging. This is not an indication that there is an issue with your solution by default.
Infosys
AU
Thanks Jeff.
I guess I need to research a bit on the AutomatonBroker to know how to disable it. And also, I could disable StartMyDay in RuntimeConfig and see if that gets rid of the error log. And regarding the shutdown log, its generated when runtime is terminated via the "TerminateRuntime" method of RuntimeHost.
I will also look into what all categories I could disable from logging to avoid clutter. Also, unfortunately, our client has lots of applications logging into EventLog and they treat an "Error" as something that needs attention. I would check and see if they could set up some bypass rules for known "Error" logs if they can not be stopped from being logged.