John Du Hart

> For systems that connect to many different databases, the current behavior generates a "name" value with a fairly high cardinality and no indication of what the operation being performed...

@gusemery The OpenTelemetry spec defines what should be included in the operation name, it's not open for creative interpretation by each client library. The underlying query can still be included...

@pimterry Thanks for replying, I'll try to tackle it this weekend.

The comment in the first method explains why ``` // Avoid the array allocation and any boxing allocations when the level isn't enabled ```

I've reported the NuGet package.

@sartan There is no official NuGet package, as the library hasn't been released yet.

I'm having a pretty similar issue, rbspy will detach thinking the process has ended. This is confirmed by setting `RUST_LOG=debug`, which gives me the following: ``` $ sudo RUST_LOG=debug ./rbspy...

Okay, so with some [additional error logging](https://github.com/johnduhart/rbspy/commit/eef3ed06008c2c3f908c8af398239eb1aea177c4), I'm now getting the following: ``` [2021-07-23T21:12:43Z WARN rbspy::core::initialize] Received a nix error Sys(ESRCH) [2021-07-23T21:12:43Z WARN rbspy::core::initialize] Other error: locking process during stack...

Just as a hint to others, we ended up solving this internally by creating a custom sampler that drops root spans for database operations (`db.system` attribute present)

Had to do this exact thing, hacky patch I came up with involved unmarshalling and marshalling each YAML document before calling `yaml.UnmarshalStrict`. ```go func objectivesFromFile(file string) ([]v1alpha1.ServiceLevelObjective, error) { b,...