feat(metadata/otc): upgrade to v0.50.0-sumo-0

[sumo-drosiek]

Description

• Upgrade otc version to v0.49.0-sumo-0
• Remove usage of metadata_attributes
• Stop moving out record attributes for systemd
• Move _collector to resource attributes for containers
• remove k8s.pod.uid for vagrant
• update docs for using containerd and fluent-bit
• remove http_listener_v2_path in routing processor instead of exporter for metadata/metrics

---

Checklist

• Changelog updated

Testing performed

• Redeploy fluentd and fluentd-events pods
• Confirm events, logs, and metrics are coming in

[swiatekm-sumo]

We also need to get rid of annotations: blocks from k8s_tagger configurations. These were unnecessary before, but now they're going to cause us to send more metadata than we need.

[sumo-drosiek]

We also need to get rid of annotations: blocks from k8s_tagger configurations. These were unnecessary before, but now they're going to cause us to send more metadata than we need.

isn't this a breaking change?

[swiatekm-sumo]

We also need to get rid of annotations: blocks from k8s_tagger configurations. These were unnecessary before, but now they're going to cause us to send more metadata than we need.

isn't this a breaking change?

It is if the user added them to their metadata_attributes. In that sense, almost all changes in this PR are breaking.

[sumo-drosiek]

We also need to get rid of annotations: blocks from k8s_tagger configurations. These were unnecessary before, but now they're going to cause us to send more metadata than we need.

isn't this a breaking change?

It is if the user added them to their metadata_attributes. In that sense, almost all changes in this PR are breaking.

I was thinking rather that we have been sending pod annotations and we stop sending them with this change

[swiatekm-sumo]

I was thinking rather that we have been sending pod annotations and we stop sending them with this change

We haven't, though. We didn't have the annotations in metadata_attributes anywhere, so it didn't get sent.

[sumo-drosiek]

I was thinking rather that we have been sending pod annotations and we stop sending them with this change

We haven't, though. We didn't have the annotations in metadata_attributes anywhere, so it didn't get sent.

We are using json, so if the annotations were in the any of the attributes, they were send as part of log

[swiatekm-sumo]

I was thinking rather that we have been sending pod annotations and we stop sending them with this change

We haven't, though. We didn't have the annotations in metadata_attributes anywhere, so it didn't get sent.

We are using json, so if the annotations were in the any of the attributes, they were send as part of log

If metadata_attributes were defined, then only attributes that matched any of the entries were sent, to my best understanding. See: https://github.com/SumoLogic/sumologic-otel-collector/blob/9923b89a506617689fcec94c1f85c0a3e7770c86/pkg/exporter/sumologicexporter/exporter.go#L292.

[swiatekm-sumo]

Ok, you're talking about record attributes, makes sense. In that sense it is a breaking change and quite annoying to deal with, as I don't think there's a processor to move attributes from the resource level to the record level.

[sumo-drosiek]

also we use pod_annotations in sourceprocessor in order to overwrite _source* configuration

[sumo-drosiek]

also filtering needs to be fixed as "" regexp catches ecerything

[swiatekm-sumo]

also filtering needs to be fixed as "" regexp catches ecerything

I'm pretty sure that's the same behaviour as exclusion in sourceprocessor. Both use MatchString:
https://github.com/SumoLogic/sumologic-otel-collector/blob/a825c0c60c4bf37e1abbdb42952eccdeaa6d397f/pkg/processor/sourceprocessor/source_processor.go#L344
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/033bc949bec36233c6c4a050a951f119dd00b16d/internal/coreinternal/processor/filterset/regexp/regexpfilterset.go#L64

[sumo-drosiek]

@swiatekm-sumo for source_processor we iterate over empty list, so we do not execute any regexp

https://github.com/SumoLogic/sumologic-otel-collector/blob/a825c0c60c4bf37e1abbdb42952eccdeaa6d397f/pkg/processor/sourceprocessor/source_processor.go#L140-L145

https://github.com/SumoLogic/sumologic-otel-collector/blob/a825c0c60c4bf37e1abbdb42952eccdeaa6d397f/pkg/processor/sourceprocessor/source_processor.go#L97-L101

[swiatekm-sumo]

I added dropping the Pod annotation from resource attributes in fix: drop Pod annotation attributes for container logs, the rest looks good to me.