On 2022-06-17 10:38:57 +0800, Abdul Qoyyuum wrote:
> Best if you just maintain the logs into a log file instead of a database
> table.
That depends on what you want to use those logs for.
If you just want to look at them when something goes wrong, I agree:
Logs files are simple, fast to write, take little space (and usually
compress well), can be trimmed with a text editor and attached to a
ticket or sent by mail ...
But if you want to process them further (generate statistics or other
reports, anonymize them, combine them with data from other sources,
...), it is useful to store them in some structured format (aka a
"database"). That doesn't necessarily mean a relational database, it
could be a nosql database (for example, ElasticSearch is very popular
for storing logs), but if you are already using PostgreSQL in your
project, using it for logs suggests itself.
hp
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp@xxxxxx | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
Attachment:
signature.asc
Description: PGP signature
