Enable service logging options when running as windows service

[xborder]

Description:

This PR partially addresses the issues described in #5300.

When running as a windows service, the collector's logger zapcore.Core is replaced by a customized zapcore.Core that writes the logs to the EventViewer ignoring what is configured in the yaml.
Instead of replacing it, the PR creates a Tee that preserves the original Core and its configuration, and adds the customized Core for EventViewer.
This way logs are duplicated and flushed by both Cores.
Since there isn't a specific telemetry configuration for windows the logging level is shared between both Cores.

As an example the following configuration:

service:
  telemetry:
    logs:
      level: warn
      output_paths: ["C:\\otel-collector.log"]

Would enable logs with a level equal or bigger to warn to be sent to EventViewer and the file otel-collector.log

This partially addresses this issue.

Link to tracking Issue:

• HowTo: Telemetry Logging to File when running as windows service #5300

Testing:

• Tested locally on a windows machine

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: xborder (a88ca9f)

[codeboten]

Will the existing testsuite for windows (https://github.com/open-telemetry/opentelemetry-collector/blob/main/.github/workflows/build-and-test-windows.yaml) be enough coverage to ensure this test solves part of the issue described?

Gaps in windows testing for this repo has historically caused problems.

[github-actions]

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

[xborder]

@codeboten From my understanding, there is not specific test suite for windows. The workflow you references just runs the tests on a windows container.

I only found 1 windows-specific test that tests the service change of status. In this PR case, it would require mocking the event viewer somehow and change the code to make stuff public in order to mock it.
Being something so specific to the OS and only when it runs as a window service, I find it somewhat hard to justify.

I'm not well-versed in the golang ways so let me know if I could improve it somehow.

[github-actions]

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

[codecov]

Codecov Report

Patch coverage: 96.70% and project coverage change: +0.63 🎉

Comparison is base (1af31a0) 90.36% compared to head (beac561) 90.99%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7025      +/-   ##
==========================================
+ Coverage   90.36%   90.99%   +0.63%     
==========================================
  Files         243      293      +50     
  Lines       14598    14271     -327     
==========================================
- Hits        13191    12986     -205     
+ Misses       1138     1017     -121     
+ Partials      269      268       -1     

Impacted Files	Coverage Δ
client/client.go	100.00% <ø> (ø)
cmd/builder/internal/builder/config.go	68.67% <ø> (ø)
cmd/otelcorecol/main.go	0.00% <0.00%> (ø)
component/config.go	87.50% <ø> (ø)
exporter/exporterhelper/logs.go	80.64% <ø> (ø)
exporter/exporterhelper/metrics.go	80.64% <ø> (ø)
exporter/exporterhelper/traces.go	80.95% <ø> (ø)
exporter/exportertest/nop_exporter.go	100.00% <ø> (ø)
otelcol/config.go	96.38% <0.00%> (ø)
pdata/internal/generated_wrapper_float64slice.go	100.00% <ø> (ø)
... and 132 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[github-actions]

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

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.