D
D
driverx182020-09-05 12:57:43
PHP
driverx18, 2020-09-05 12:57:43

Is logging to a file the norm?

I have a project, and, let's say, 30,000 requests per day are being made. I want to implement project logging, because now everything is done primitively there, and the question arose of where it is better to log. Some comrades say that on their working projects, logging is done to a file and is normal. There are a lot of tips about the ELK stack on the net, but I just don’t need it so newfangled and twisted on my volumes. Who can advise where you would choose to log? I have options:
1) MongoDB - so far I'm leaning towards it the most
2) File
3) there is a logs table in the database (but somehow I don't really lean towards this option)
4) Maybe a radish?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
N
Nikita Shinkevich, 2020-09-05
@domres

Log this oil into the database. I would do it in a file ... more precisely in files. It's easier to turn.

D
Dr. Bacon, 2020-09-05
@bacon

This is the norm. Sometimes there is a problem with concurrent writes, but it is solvable.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question