Skip to content

feat: otlp logger exporter#212

Closed
yuzurihaaa wants to merge 65 commits into
Workiva:masterfrom
yuzurihaaa:feat/otlp-logger-exporter
Closed

feat: otlp logger exporter#212
yuzurihaaa wants to merge 65 commits into
Workiva:masterfrom
yuzurihaaa:feat/otlp-logger-exporter

Conversation

@yuzurihaaa
Copy link
Copy Markdown
Contributor

Which problem is this PR solving?

  1. Continuation of feat: logger exporter ConsoleLogRecordExporter and InMemoryLogRecordExporter #211
  2. This PR is specific for OTLP log exporter.

Fixes # (issue)

Short description of the change

  1. OTLPLogExporter feature

How Has This Been Tested?

  1. Unit test

Checklist:

  • Unit tests have been added
  • Documentation has been updated

@yuzurihaaa yuzurihaaa force-pushed the feat/otlp-logger-exporter branch from d8369f7 to 6ed93bf Compare January 20, 2025 16:56
@yuzurihaaa yuzurihaaa mentioned this pull request Jan 20, 2025
2 tasks
@yuzurihaaa yuzurihaaa force-pushed the feat/otlp-logger-exporter branch from 6ed93bf to c28ad27 Compare March 3, 2025 02:54
@yuzurihaaa yuzurihaaa force-pushed the feat/otlp-logger-exporter branch 2 times, most recently from c075506 to 0969f7d Compare March 18, 2025 05:08
@evanweible-wf evanweible-wf removed their request for review April 25, 2025 16:18
@yuzurihaaa yuzurihaaa force-pushed the feat/otlp-logger-exporter branch from 83caa79 to 84931c5 Compare May 9, 2025 03:03
@dustinlessard-wf
Copy link
Copy Markdown
Contributor

Hi @yuzurihaaa
Thank you for taking the time to contribute to this project. We really appreciate the effort you put into opening this pull request.
I want to be transparent about the state of the repository: we have not been actively maintaining this codebase, and we do not currently have the bandwidth to properly review, test, and support external contributions at the standard they deserve.
For that reason, we’re going to close this pull request. This is not a reflection on the quality or value of your contribution. Rather, it reflects our current inability to responsibly vet and merge changes into the project.
We are also exploring a path to transfer ownership or stewardship of the project outside of our company, so that it can hopefully have a more active and sustainable future. Until that direction is clearer, we do not want to create a misleading impression that the repository is actively maintained or that we can support merged changes going forward.
Thank you again for your contribution and for your interest in improving the project. We’re sorry we were not able to engage with your pull request in the way it deserved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants