Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To me, GraphQL is a great base model for what logs should be.

The producer declares all possible data.

The consumer requests the specific data it wants, at runtime.

Because fundamentally, there's a mismatch of knowledge. Log consumers won't inherently know everything that can be in logs. Ergo, modern API-style ecosystem models are probably better approaches.



"The producer" is the world outside.

So this fails at point one - it is impossible to "declare all possible data".


When I'm reading logs, I don't know upfront what data I'm looking for, so I want to see all of it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: