John White

**EDIT: don't rely on this, it's bugged, see after.** It also appears from my research that indexing anything from OTEL log resources as labels is pretty much impossible. In other...

Well, it appears that copying attributes from the log context to the resource doesn't always take the correct logs. I'm seeing values I don't expect, so maybe we shouldn't rely...

Check this out https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32080 I'm reading it now

@JoelDavidLang you're totally right on this, and after some more research I can confirm this is a deliberate choice by Loki to keep indexes to a minimum (and maybe potentially...

@JoelDavidLang considering how Loki is designed to index only the log context and bruteforce the search of all other attributes, contrary to (for example) elasticsearch which indexes everything, it sounds...

This is a pretty important resource leak, @natefinch can you please take a look? I'm experiencing the same issue, no matter if I close the logger or not. Also this...

Also this https://github.com/natefinch/lumberjack/pull/57 this https://github.com/natefinch/lumberjack/pull/80 and this https://github.com/natefinch/lumberjack/pull/90 among others, this is getting worrisome, is this library maintained?

We're also getting super confused by the communication about this library. There's production code using this, I think everybody needs to know better what's the long term plan before doing...

I don't think it's very versatile, indexes could have complex conditions, it's best to declare them as code rather than tags.

This is much needed otherwise schemas are overwritten if a file imports another one with the same namespace, and the error is misleading ("can't find type X" while what's happening...