How is the performance of a GRPC collection server in Java? Can it scale according to the load?

[JangCool]

I'm currently looking into agent instrumentation and plan to examine the collection server in detail next. On GitHub, there are only simple examples for running a GRPC server, and I am curious about the performance differences compared to a Go-based collection server.

I read the document titled "Scaling the Collector," and it seems to recommend scaling under heavy load. Is it the same for a Java GRPC collection server? It might also be a good idea to separate the log collection server, tracing server, and metrics collection server.

https://opentelemetry.io/docs/collector/scaling/

I'm wondering whether it would be better to implement the exporter with Netty and reconfigure the collection server with Netty, or if a GRPC server would be sufficient..

[laurit]

Could you elaborate what do you mean by Java GRPC collection server?

[laurit]

If performance is a concern I'd urge you to benchmark it yourself.

[trask]

https://github.com/open-telemetry/opentelemetry-java-examples/tree/main/grpc is not an otlp grpc server

[zerocooldog]

@trask Oh... I think there was some confusion.

I'm planning to implement a collection server using Java. I found an example of a gRPC server and wanted to ask if I can use that to implement the collection server.

Or, I was wondering if there are any plans to implement an OTEL collection server in Java language

[laurit]

For testing we use fake backend that accepts otlp/grpc https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/smoke-tests/images/fake-backend

[zerocooldog]

@laurit Thank you for the answer. I will take that into consideration.

And I think UDP communication might be necessary, so I should also look into implementing a custom exporter.