[SOLVED] How avoid generating the stats.log and worker.log files?

Solved
1

I am using the Local Blynk Server
And my question is the following:
How can you completely avoid generating the stats.log and worker.log files on the local Blynk server?

Thanks in advance

2

There is no way to avoid this.

3

A work around would be writing a program that runs in the background and checks if theese files exist every 30s or so and delete them if it boughters you so :stuck_out_tongue:

4

I believe there are also different levels of verbosity and you can set it to the minimum amount of logging.

5

Okay Dimitri, understood and thank you.

On the other hand, the use I give to the local server is very basic, I do not use database, but since the files are being generated, what kind of information and analysis I could extract from these files and help me to optimize the server ?

I have observed that the records do not have a time reference.

Please, can you tell me how I could take advantage of these files, for now they only take up space on the hard disk

6

They will be useful if you start to notice any problems with your server, that is the essence of logs.

1 Like
7

@Costas correct. This files are used just for server monitoring. They are not necessary for local servers.

8

Understood, the log file that I see very useful is blynk.log, but until now, even when I have had problems, I have not found in the files stats.log and worker.log information to help me solve problems.

Thank you.

9

Just run a crontab every day to delete them. That way it won’t impact performance and you can always check logs for the previous day.

1 Like
10

can i just delete the log/archive folder?

mine is full with logs from 2017, 2018, 2019 etc…

11

Sure you can.

1 Like