What could be the best way for naming and logging?
Is logging the errors in txt file and sending email enough, or should take a screenshot or anything else?
Some people say it’s best way to have a report for the task details like powerBi, instead of looking at error mails.
What do you think?
also how do you name variables, string-integer-list-datetime-boolean etc
Kindly check the following links:
Regards
I will check them
We standardized our logging after a long discussion with all our developers. We created a logging taskbot that requires certain params that are fed into the logging taskbot. Things like bot name, task name, bot runner, user, message etc.
Everyone uses the same logging taskbot now and all our logs have the same format. We even added a couple of other taskbots that control how often a log file is created for each bot (daily, weekly, monthly etc.) and a naming convention for the log files. Those tasks are run at the beginning of each bot and new log files are created if necessary or the BOT may continue to log to an existing file.
Yes, we have a taskbot that takes variables (Bot name, log folder, log freq...) and creates a new log file at the start of all our BOTs. Then we have a standardized logging taskbot that we use throughout every BOT for logging. We even added logging levels controlled by a credential (level 1, 2, 3) so we can increase or decrease the amount of logging. Every time we call the logging taskbot, we pass in the credential vault variable and the level of logging for that item and if the level in credential vault is higher than the logging level for that log line, it logs. This way we can get more verbose logging when needed for debugging but we can dial it back to minimal logging when all is well.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.