Skip to content

Replace loggregator_emitter gem with gRPC V2 client#5043

Draft
serdarozerr wants to merge 2 commits intocloudfoundry:mainfrom
sap-contributions:fix-archived-logregator_emitter
Draft

Replace loggregator_emitter gem with gRPC V2 client#5043
serdarozerr wants to merge 2 commits intocloudfoundry:mainfrom
sap-contributions:fix-archived-logregator_emitter

Conversation

@serdarozerr
Copy link
Copy Markdown
Contributor

This PR replaces the deprecated loggregator_emitter gem (V1, UDP/beefcake protobuf) with a new LoggregatorEmitter::Client built on gRPC V2. The loggregator config key router is renamed to endpoint and internal_url is removed. Optional mTLS cert fields (ca_file, cert_file, key_file) are added to the api, clock, and worker schemas. The gRPC stub is initialized lazily on the first emit call to avoid conflicts with Puma's thread pool at startup.

  • Links to any other associated PRs

  • I have reviewed the contributing guide

  • I have viewed, signed, and submitted the Contributor License Agreement

  • I have made this pull request to the main branch

  • I have run all the unit tests using bundle exec rake

  • I have run CF Acceptance Tests

feat: replace loggregator V1 UDP emitter with gRPC V2 client

Remove the loggregator_emitter gem (V1, UDP/beefcake) and replace it
with a new LoggregatorEmitter::Client backed by gRPC V2. The client
uses lazy stub initialization to avoid gRPC background threads
conflicting with Puma's thread pool at startup. Config keys renamed
from `router`/`internal_url` to `endpoint`, with optional mTLS cert
fields added to all three schemas (api, clock, worker). Integration
and unit tests updated to use the V2 gRPC fake server.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant