Rules that should not affect the score

[jpkrohling]

My initial idea with the instrumentation score was to have rules that would affect the score in a way or another. However, there are rules that we might not be able to link to a service: if we don't have a service.name, which service should be affected? If we have a trace with missing spans (judged by a parent span ID we've seen but isn't there)?

For those cases, I believe we should have a way to flag the rule as (potentially) not be used for the score: if we parent span ID we are looking for is the parent of a span-kind=SERVER, then it's safe to say we don't know which service has the bad instrumentation (or OTel config). However, if it's internal, then we can "safely" attribute the problem to the service.name.

This issue is to sparkle a discussion around this topic.

[mmanciop]

I think there might be a misunderstanding here. To the best of my knowledge, not all OTel telemetry is required to have service.name set, just that the SDKs must set it. There are categories of telemetry that pretty much cannot have service.name set in the general case. Think for example of K8S events represented as log record: if your deployment has multiple services, say one per pod, which service.name should go on the event describing that deployment being changed?