> Logs are there for ignoring. You need them precisely twice: once when you are developing, and once when the thing's gone to shit good logs are very valuable

> Logs are there for ignoring. You need them precisely twice: once when you are developing, and once when the thing's gone to shit good logs are very valuable both when things are still working and when there is an outage. E. g. I with nginx even on a loaded servers error.log is small and it is possible to skim it from time to time to ensure there are no unexpected problems. access log is useful for ops tasks to - when possible I use tab separated access log which can be queried using clickhouse-local. Sometimes software write bad (useless) logs, but this is not a problem with logs in general. Also it may be useful to collect metrics for number of messages on different levels (info/warn/error/crit) - sudden changes in rate of errors is something which should be investigated.