WIP: log to span exporter

[gramidt]

Description:
This exporter receives logs, converts them to trace spans, then exports the spans via OTLP over gRPC.

NOTE: This has been migrated from a PoC in a private distribution, and will be split up into multiple PRs once a more robust implementation is finalized.

Link to tracking Issue:
#3071

Testing:
Unit Tests

Documentation:
Code + README.

[codecov]

Codecov Report

Merging #3003 (69c46a6) into main (9a981e3) will decrease coverage by 0.22%.
The diff coverage is 49.61%.

❗ Current head 69c46a6 differs from pull request most recent head 7ab49b2. Consider uploading reports for the commit 7ab49b2 to get more accurate results

@@            Coverage Diff             @@
##             main    #3003      +/-   ##
==========================================
- Coverage   91.61%   91.38%   -0.23%     
==========================================
  Files         486      478       -8     
  Lines       23519    23299     -220     
==========================================
- Hits        21546    21291     -255     
- Misses       1463     1510      +47     
+ Partials      510      498      -12     

Flag	Coverage Δ
integration	68.96% <ø> (+5.29%)	⬆️
unit	90.37% <49.61%> (-0.24%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
exporter/logtospanexporter/log_to_span_pusher.go	11.42% <11.42%> (ø)
exporter/logtospanexporter/factory.go	94.11% <94.11%> (ø)
exporter/logtospanexporter/config.go	96.00% <96.00%> (ø)
processor/k8sprocessor/config.go	0.00% <0.00%> (-100.00%)	⬇️
...urcedetectionprocessor/internal/system/metadata.go	0.00% <0.00%> (-57.15%)	⬇️
receiver/carbonreceiver/factory.go	68.42% <0.00%> (-31.58%)	⬇️
receiver/receivercreator/factory.go	71.42% <0.00%> (-28.58%)	⬇️
exporter/elasticexporter/config.go	71.79% <0.00%> (-28.21%)	⬇️
receiver/windowsperfcountersreceiver/factory.go	88.23% <0.00%> (-11.77%)	⬇️
exporter/elasticexporter/factory.go	90.32% <0.00%> (-9.68%)	⬇️
... and 51 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9a981e3...7ab49b2. Read the comment docs.

[clhain]

Would it make sense to treat SpanName like the others and derive it from a specified attribute (maybe with an optional default)?

[gramidt]

That's exactly what it is; however, the comment is incorrect. haha

I also thought about having a default, but I'm not sure a default would ever be used...

[clhain]

haha sorry that was obvious from context I just didn't catch it. Agreed probably no need for default.

[gramidt]

No need to apologize. It helped catch the terrible comment :)

[github-actions]

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

[github-actions]

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

[github-actions]

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

[github-actions]

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

[jriguera]

It seems this PR got abandoned. We have an use case where access logs from a PaaS (Cloudfoundry) have the tracing headers like x_b3_traceid:"12cf43fd0b6842067e45edca9c881012" x_b3_spanid:"7e45edca9c881012" x_b3_parentspanid:"-" and we would like to process those log lines as spans.