4 ms·
Yep, you never know what logs you need until you need it. If there’s an economical factor coming into play (because proper telemetry will cost a noticeable amou
by stingraycharles 7y ago
Yep, you never know what logs you need until you need it. If there’s an economical factor coming into play (because proper telemetry will cost a noticeable amount of money), you can always choose to sample the more verbose logs.
- ignoramous 7y agoHonest Q: Isn't that's where tracers like AWS XRay and Google Dapper come in? And somewhere down the line, solutions like Envoy/istio try to make the whole ordeal manageable?
- gbuk2013 7y agoNothing cloud is relevant when your production network has no outbound access to the internet due to PCI. ;) Not sure about the other two (will check it out) but we have have apps in 4 programming languages across several teams. Structured (JSON) logging is the easiest way of sending data to one place from literally everywhere.
- dropofwill 7y agoYou can implement distributed tracing with logs if every player in the system is propagating the headers appropriately. Tools like NewRelic APM and XRay will take care of that bit mostly for you. Service mesh data planes have a wider scope, but they do make it much easier to implement distributed tracing (I think Istio includes this out of the box). In the end though these tools can’t replace app logs because they only let you reconstruct what happens in between services, not internal to them.
- gbuk2013 7y agoAgree 100% - logging is expensive, in terms of performance hit and storage, but it is totally worth it.
- QuickToBan 7y agoIn the medium to long term, the absence of logging is always more expensive than its presence.