Hacker News Reader

If I am POSTing logs to a thing, why would that thing be your program and not, say, Logstash's HTTP input or even direct to an Elasticsearch cluster?

Do I really want to POST logs? What if the logging endpoint is not available? Don't I want log delivery uncoupled from the application, so logging failures don't become application failures?

View on HN

Yes, you would, if that's the level of sophistication you need. If, on the other hand, you are looking for a simple way to log anything without having to set up, deploy, and maintain a plugin or library, Lazylog might be a better choice. It's particularly true when you think of logs as more universal messages, e.g., user visits (like an analytics tool) or email addresses (for a sign-up flow). Very good feedback, Jack. Thank you for taking the time.

> or email addresses (for a sign-up flow)

How does this comply with privacy laws/requirements (e.g. GDPR)? Storing PII is a liability and you expose yourself to legal risks.

Edit: Just to clarify: it's not an aggressive question, I'm mostly curious what is your strategy about this.

You're right. Email addresses aren't the best example of “universal messages” for the reason you mentioned. Thanks for bringing it up.

Reply on news.ycombinator.com