Unable to view logs in Orchestrator for a specific tenant

[adityarikame (Aditya M Rikame)]

Hello Everyone we are facing an issue where we are not able to see logs for all tenant in the Orchestrator

For other tenants its working perfectly fine

After uirobot service restart the logs are visible but after certain executions the problem reappears

Any help on the same would be helpful thanks

[Gokul001 (Gokul Balaji)]

Hi @adityarikame

welcome to Uipath community

Check if you are hard disk having some space for the C drive

Check out this thread

https://forum.uipath.com/t/log-message-doesnt-populated-in-orchestrator-log/390141/12

Regards
Gokul

[Sudharsan_Ka]

HI @adityarikame

Checkout this threads

Orchestrator Job Logs Are Missing or Not Showing

What to perform when Orchestrator Job logs are missing or not showing? Issue Overview: Orchestrator Job logs are missing or not showing. Root Cause: There are a few different scenarios that can cause this condition. This scenario usually arises after the making incorrect configuration changes to Orchestrators logging functionality. Diagnosing the Issue If the issue only occurs with certain Robot machines, go to the section “Robot Cannot Send Logs to Orchestrator” Open the Orchestrator s…

Log message doesn't populated in orchestrator log

Hi @Sudharsan_Ka , Before dong all the research check if you are hard disk having some space for the C drive. some times if we don’t have space in the C drive it will create these kind of issues. if the disk is fully occupied delete temporary and un wanted files and clear sufficient space in the C drive and try executing your process in orchestrator and see if you are getting logs. And also make sure that you are using logging type as info so that you will get all the informative logs in orche…

Logs are not visible in Orchestrator but they are in the database

@wilbardmtei The Logs page displays when logs generated by Robots in all folders that you have access to. Logs generated outside the context of a folder can be viewed only in the Orchestrator database and Elasticsearch. Refer this – About Logs

Regards
Sudharsan

[Sudharsan_Ka]

Also @adityarikame

Job log not visible in Orchestrator

changing web.config file as below fixed my issue as per support help. Changing the target name under robotelasticbuffer from "robotelastic’ to “robotelastic1”. This change is done to read the data from orchestrator database instead of elasticsearch. Please refer below screenshot. [fix]

[adityarikame (Aditya M Rikame)]

The Orchestrator is a cloud one not managed by us . I would be able to change anything related to orchestrator

[adityarikame (Aditya M Rikame)]

Tried the solution already mentioned in the forums its not working

[Sudharsan_Ka]

You are using community version or enterprise? @adityarikame

[Gokul001 (Gokul Balaji)]

May i know the version of the orchestrator @adityarikame

[adityarikame (Aditya M Rikame)]

its an enterprise cloud

[Sudharsan_Ka]

Then you should ask your infrastructure team to check the space in the database and extend the space there so that the logs can be populated again in your orchestrator

Check out this thread for Database space increasing

Uipath database size increasing

Review the logs that are actively being generated this will indicate the credential being used as well as the Robot. Do they have anything in common? Robots can be adjusted to have different log levels within their NLog configuration, Orchestrator Robot setting, and from the UiRobot Tray / Agent Desktop has any of your robots been bumped up to trace level and over logging when it does need to? Take a look at your Orchestrator’s Web.config and look to what your minimum log level is configured f…

Regards
Sudharsan