[exporter/logging] Remove logging exporter

[TylerHelmuth]

Description

It is September, which means we get to remove this deprecated component.

• The helm chart was updated to exclude the logging exporter already: https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-collector/UPGRADING.md#0840-to-0850.
• The Operator references have been updated: [chore] Remove references to the logging exporter opentelemetry-operator#3259.
• Opentelemetry.io site final references to update: [chore] Remove references to the logging exporter opentelemetry.io#5143

Link to tracking issue

Related to #7769

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.44%. Comparing base (9f57a55) to head (692bcfc).
Report is 13 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #11037   +/-   ##
=======================================
  Coverage   91.44%   91.44%           
=======================================
  Files         424      422    -2     
  Lines       20270    20202   -68     
=======================================
- Hits        18535    18473   -62     
+ Misses       1359     1354    -5     
+ Partials      376      375    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mx-psi]

There are a bunch of references on examples in language library repositories still that mention the logging exporter. This search has a lot of false positives, but it's a good start I think: https://github.com/search?q=org%3Aopen-telemetry+%22logging%3A%22+-repo%3Aopen-telemetry%2Fopentelemetry-collector+language%3AYAML+OR+language%3AMarkdown&type=code&p=1

We also have ~18% of survey respondents from the Collector survey raw data using the logging exporter so I think we need to do this very carefully.

At a minimum I feel like we need a migration page, and a very clear error message that tells you to use the debug exporter and links you to the migration page. Additionally, it would be great to have something like #7631 before we do this (not sure if it should be a hard requirement tho).

I am blocking this until we at least have no references to the logging exporter within examples in the OpenTelemetry org

[TylerHelmuth]

@mx-psi it has been another 4 weeks with an even louder warning and @codeboten has updated a majority of the loggingexporter references in language repos. I feel we should move forward with this removal.

[codeboten]

I've opened PRs to most of the remaining references to the logging exporter found in the query that were not in archived repositories.

I don't know that it's worth waiting for all of them to be merged before moving this forward.

Language repos have been updated

[mx-psi]

I don't think it should block this PR (we can do this in a separate one) but I feel like we should give a clearer error message when trying to use the logging exporter for a while.

For example, we can do the following: if a configuration file references a logging exporter and the logging exporter is not available, but the debug exporter is, then add a hint to the error message suggesting the usage of the debug exporter.

Based on the survey usage data, I expect this change to be quite disruptive for users and for us to get quite a few Slack messages and Github issues about this, so I would like to help users as much as possible

[TylerHelmuth]

@mx-psi added an additional warning:

receivers:
  otlp:
    protocols:
      grpc:
exporters:
  logging:
    level: debug
service:
  pipelines:
    traces:
      receivers:
        - otlp
      exporters:
        - logging

❯ ./bin/otelcorecol_darwin_arm64 --config ./bin/config.yaml
Error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):

error decoding 'exporters': the logging exporter has been deprecated, use the debug exporter instead
2024/10/01 08:55:31 collector server run finished with error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):

error decoding 'exporters': the logging exporter has been deprecated, use the debug exporter instead

[mx-psi]

IMO this is ready to merge once we remove the exporter from the opentelemetry-collector-releases manifests

[TylerHelmuth]

Releases PR: open-telemetry/opentelemetry-collector-releases#682

[mx-psi]

I pinned issue #11337 which we can use as the central place for any people that need help with the migration. We can keep it pinned and open for a couple weeks and close it after a while.

I think this has enough approvals to merge so I am merging, thanks everyone for the hard work, let's hope this goes smoothly!