Standardize Outcome vs Status for Internal Telemetry

[mwear]

Component(s)

No response

Describe the issue you're reporting

While reviewing #49128 we hit a small inconsistency: components don't agree on how to label whether an operation succeeded or failed in their internal telemetry. Some use outcome, one uses status. It would help to pick one convention and write it down at https://opentelemetry.io/docs/collector/internal-telemetry so new components follow it.

Here's a breakdown of what currently exists:

Component	Attribute	Values
receiverhelper	outcome	success, refused, failure
kafkaexporter	outcome	success, failure
kafkareceiver	outcome	success, failure
resourcedetectionprocessor	outcome	success, failure
elasticsearchexporter	outcome	success, failed_client, failed_server, timeout, too_many, failure_store, internal_server_error
k8sattributesprocessor	status	success, error

Here are links to the relevant portions of metadata.yaml for each component:

• receiverhelper
• kafkaexporter
• kafkareceiver
• elasticsearchexporter
• k8sattributesprocessor

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}