Different Logging Levels: Orchestrator and Execution Log

Hi all, I’m trying to set logging level in Orchestrator to “Info” while my Log Messages inside the robots are at Trace Level (so as I will be able to check only Info level in Orchestrator). However, I need to see these Log Messages (at Trace Level) on my Execution Logs in order to better troubleshoot.
Is there a way to see different logging levels regarding Orchestrator and Execution Logs?

Hello @Lucas_Turbuk_BR!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly

Hey, sorry for digging up old topic, but it’s the closest one to my problem, ale sadly not resolved yet.
I need to see logs of level Warning and above in Orchestrator, but have stored logs of Information and above locally on bot machine for better debugging. It looks like log level set in Orchestrator sets it for both Orchestrator logs and local logs stored in *Excecution.log files.
I have set up logging level to Warning in Orchestrator…

…and modified NLog.config file located in UiPath\Studio from below line
<logger name="WorkflowLogging" writeTo="WorkflowLogFiles" final="true" />
<logger name="WorkflowLogging" minLevel="Info" writeTo="WorkflowLogFiles" final="true" />
Sadly, even after restarting machine it still was logging anything from Warning level in Orchestrator and in Excecution.log file locally on the machine.
I am launching unattended bot from Orchestrator if that’s make any difference.
Had no idea this will be so hard.

I believe this explains the behavior that you observe:

Maybe this could be overcome by remove Logging Level option in Orchestrator and defininig multiple targets and rules in NLOG.CONFIG
as described in Configuration file · NLog/NLog Wiki · GitHub


Thanks for your answer @J0ska
If I would like to configure different logging levels via NLog file only then I wouldn’t even know where to start with setting up Orchestrator logs. By default there is no entry that looks like it’s for Orchestrator, while still logs are being sent to Orchestrator. So I guess this is happening independently of that file?
Below is a sample from unmodified NLog.config file:

    <logger name="WorkflowLogging" writeTo="WorkflowLogFiles" final="true" />
    <logger minLevel="Info" writeTo="EventLog" />
    <target type="File" name="WorkflowLogFiles" fileName="${WorkflowLoggingDirectory}/${shortdate}_Execution.log" layout="${time} ${level} ${message}" keepFileOpen="true" openFileCacheTimeout="5" concurrentWrites="true" encoding="utf-8" writeBom="true" />
    <target type="EventLog" name="EventLog" layout="${processname} ${assembly-version} ${newline}${message}" source="UiPath" log="Application" />

I doubt I will find an answer in Configuration file · NLog/NLog Wiki · GitHub as this is not specifically about logging in UiPath, but a general one for NLog.

Hi @mateuszmacheta
in robot documentation is separate Orchestrator target and NLog target

Therefore it seems these are independent and you can only adjust the NLog one, i.e. what is written to the log file.


All right, so the idea here would be to set Orchestrator logging level in Orchestrator bot settings and set different logging level for Execution.log in NLog.config file. Too bad it isn’t working for me :frowning:
Maybe I’ll check on different computer, not sure what I’m doing wrong.