3 ms·

Thanks for this! This is really cool, I have a few questions. Can Lightrun prevent certain fields from being logged? Some fields shouldn't be logged such as cre

Thanks for this! This is really cool, I have a few questions. Can Lightrun prevent certain fields from being logged? Some fields shouldn't be logged such as credit card numbers, secrets, username etc. How can we prevent devs from accessing things they are not supposed to? Can this replace continuous profilers as well? Whats the reason this is not getting more adoptance? AFAIK most companies are either eating the cost of logging or managing it with sampling. This seems way better than either of those options, so whats the downside?

tomgs 4y ago
Per your first question - protecting sensitive information - we've got PII redaction and Blocklisting that cover a variety of potential cases of data leakage [0]. Regarding profiling - we're not actively a profiler, but we do offer a set of code-level metrics you can use to do performance analysis and detect bottlenecks [1]. Regarding adoption - we're doing OK:) I think this is a new approach, one that is quite different than what developers are used to. But it's also one of those things that - as you mentioned - make so much more sense than the alternatives, and with costs rising it's really even more evident than ever. If you're interested in the cost of logging specifically we've got it broken down in a study [2] we recently released. [0] https://docs.lightrun.com/data-security/ https://docs.lightrun.com/data-security/ [1] https://docs.lightrun.com/metrics/ https://docs.lightrun.com/metrics/ [2] https://lightrun.com/resources/lightruns-economic-impact-on-enterprise-logging-observability-costs/ https://lightrun.com/resources/lightruns-economic-impact-on-...