Logging too much

Logging is a fundamental tool for debugging. Like anything, you can do too much of it. And in different ways! It’s easy to forget about log messages you added, long after you actually needed them.

Logging too much: it becomes hard to sift through and find what you are looking for. This is “logspam.”

Logging too much: it can be a performance issue where you are using up I/O resources just for generating and writing logs. A bit of an extreme example but a real risk.

Logging too much: too expensive! When you’re working with cloud solutions, logging costs you money.

Logging too much: too much information. During development, you might log sensitive information (locally). Review your logging to make sure no PII or sensitive data is in there!

Logs can also fill up hard drives and take down web services as a result, so be sure to set up rotation.

Any fun logging stories?