Log the name of the component that failed to start

[yurishkuro]

Describe the bug
I have a component (processor) that fails to start due to misconfiguration of the pipeline.

Steps to reproduce
A processor whose Start method returns an error.

What did you expect to see?
An error logged indicating which component failed.

What did you see instead?

Error: cannot start pipelines: <<my error message here>>
2024/06/17 22:11:03 cannot start pipelines: <<my error message here>>

What version did you use?
v0.102.1

Additional context
I am forced to enrich the error myself with the name of the component. I think instead that should be coming directly from the framework that initializes the pipeline.

[terakoya76]

This may have been resolved by #10440 ?

[rogercoll]

#10440 did improve the component's error visibility but service's returned error does not contain the component ID yet:

2024-12-10T08:54:05.084+0100    error   graph/graph.go:426      Failed to start component       {"error": "start function error in processor", "type": "Processor", "id": "geoip"}
2024-12-10T08:54:05.084+0100    info    service@v0.115.0/service.go:303 Starting shutdown...
2024-12-10T08:54:05.084+0100    info    extensions/extensions.go:66     Stopping extensions...
2024-12-10T08:54:05.084+0100    info    service@v0.115.0/service.go:317 Shutdown complete.
Error: cannot start pipelines: start function error in processor
2024/12/10 08:54:05 collector server run finished with error: cannot start pipelines: start function error in processor

If telemetry logging level is set to fatal, there will be no way to tell which component produced the error:

Error: cannot start pipelines: start function error in processor
2024/12/10 09:02:25 collector server run finished with error: cannot start pipelines: start function error in processor

[rogercoll]

Ongoing PR to fix this issue #11837