Orchestrator latest version Update

Help
, ,
1

Hi Friends,
I have a difficult situation . We are planning to update the orchestrator the latest version. I read this document. It has the point that if it has more than 2 million logs , it occurs the process times out . The below image. I have 105 million logs in my orchestrator. I want to know that how to handle the process time.

image
image911×361 17.4 KB

Thank you
Balamurugan.S

2

Hi @balupad14: Please follow below guide:

1 Like
3

Hi @balupad14 ,
Can you tell me that your are referring orchestrator Log table or orchestrator log file ?
then will give you idea
.mdf logs or .ldf logs

1 Like
4

From my own experience this is a recommendation and what UiPath support will tell you to keep your tables below as Akash pointd to their Maintenance Considerations page; however, this covers only the basics and if you were to reach out to support directly, they’d probably bring up a few other tables.

We had a similar scenario previously (~75M), which I did clone the database and upgrade in our test infrastructure environment with no issue. We did however end up cleaning a few tables, to lower the consumed disk space (now about ~3M Logs) before upgrading our Pre-production environment, after we do some further testing we’ll upgrade production which is very similar to Pre.

image

I would look at from the perspective of do you actually need to maintain that volume of logs in your Orchestrator’s database? Probably not, if you do need to keep it around for other non-operational reasons it probably better suited in Elastic Search, Splunk or some other platform for historical reporting.

We keep a rolling 15 days in Orchestrator to keep logs around 3M and the logs flow into Splunk in near real-time. For queue items keeping non-deleted queue items for 30 days and Deleted queue items for 15 days. We haven’t set up maintenance on the Notification or AuditLogs tables yet, but keeping an eye on them to see how they grow.

If you are concerned about upgrading with that number of records, I would definitly test it out first, make a backup, and/or trim your tables.

Cheers,
Tim

1 Like
5

Thank you @Akash_N_Jain. Definitely I take a look …

6

Thank you @Maneesha_de_silva… I am telling about he log table in orchestrator database…

7

Hi @codemonkee,

It is really so much informative . You are a great person that you gave more information, Thank you very much. In our scenario, We can not update the latest version. So what we decide that going to rename the existing log table. We create the new log table with same schema. After the updation of the latest version we are going to import only the production robot’s logs some specific range.

Thank you
Balamurugan.S

1 Like
8

Hi @balupad14
This is my idea then , I hope you can update without issue

First Backup your DB
2. Backup your log table data
Into newly created table ( Above maintenance considerations) have script to copy the table

Then use following script to copy entire data in your log table in to your archive table

INSERT INTO table2
SELECT * FROM LOGS

so then you have all logs in your archive in case
Then you can delete your log table data via given script by Maintenance Considerations

DELETE FROM [UiPath].[dbo].[Logs]
  /*
0 = Verbose, 1 = Trace, 2 = Info,
3 = Warn, 4 = Error, 5 = Fatal
*/
where 1=1
and level = 2
-- and TenantId = 1 -- default tenant
and  DateDiff(day, TimeStamp, GetDate()) > 45

From this log get date (45)you can reduce the number then it will delete all data
And remember you have to delete all that levels(/*
0 = Verbose, 1 = Trace, 2 = Info,
3 = Warn, 4 = Error, 5 = Fatal
*/)

So then your log file will be clear out no issue you can go for the update

1 Like