Add support for filtering attribute keys for streams via an exclude list

[codeboten]

Changes

This change adds details around supporting the creation of a stream with a set of excluded attribute keys. This functionality is supported in the Go implementation via the use of filters. The proposal in this PR is to address an issue in the configuration working group: open-telemetry/opentelemetry-configuration#112

Please provide a brief description of the changes here.

For non-trivial changes, follow the change proposal process.

• Links to the prototypes (when adding or changing features)
• CHANGELOG.md file updated for non-trivial changes
• spec-compliance-matrix.md updated if necessary

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[cijothomas]

LGTM, but one note before merging:
I'll let maintainers comment if there is a need to mark this section as experimental, and wait for 2-3 implementations before marking as stable. This PR right now makes no explicit call out, so this is by default treated as stable spec, though just 1 language has it implemented.

[jack-berg]

I'll let maintainers comment if there is a need to mark this section as experimental, and wait for 2-3 implementations before marking as stable. This PR right now makes no explicit call out, so this is by default treated as stable spec, though just 1 language has it implemented.

Its already possible to do this in the stable java implementation. I think the same is true for go. I think this is safe / benign enough to merge as stable without an experimental period.

[codeboten]

Don't think the failure is related to this pr:

  ERROR: 1 dead links found in ./specification/compatibility/prometheus_and_openmetrics.md !
  [✖] https:/prometheus/prometheus/commit/d9d51c565c622cdc7d626d3e7569652bc28abe15#diff-bdaf80ebc5fa26365f45db53435b960ce623ea6f86747fb8870ad1abc355f64fR76-R83 → Status: 406

[trask]

ERROR: 1 dead links found in ./specification/compatibility/prometheus_and_openmetrics.md !
[✖] prometheus/prometheus@d9d51c5#diff-bdaf80ebc5fa26365f45db53435b960ce623ea6f86747fb8870ad1abc355f64fR76-R83 → Status: 406

(re-run resolved for now)

[jack-berg]

@cijothomas since you approved this and you're involved in dotnet / rust, is it safe to say that you don't see this as a problem for dotnet / rust?

@open-telemetry/javascript-maintainers / @open-telemetry/python-maintainers can you comment on whether or not it would be problematic to extend view stream configuration as described in this PR?

[cijothomas]

@cijothomas since you approved this and you're involved in dotnet / rust, is it safe to say that you don't see this as a problem for dotnet / rust?

Correct.

[JamieDanielson]

This seems reasonable. In JS we already have an allow-list, so it would just need to be extended for a deny-list.

[pichlermarc]

This seems reasonable. In JS we already have an allow-list, so it would just need to be extended for a deny-list.

It's already implemented on the next branch and will ship with SDK 2.0 🙂