Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for grpcio-aio (Async gRPC) #330

Open
synackSA opened this issue Aug 24, 2021 · 6 comments
Open

Support for grpcio-aio (Async gRPC) #330

synackSA opened this issue Aug 24, 2021 · 6 comments
Labels

Comments

@synackSA
Copy link

Is your feature request related to a problem? Please describe.

We're currently in the process of moving from our PHP based Legacy/Monolith system to a Python based Micro-services environment with a React Micro-frontend. We've been using New Relic for our performance monitoring, logging, alerts, profiling, problem debugging, etc. We've been noticing that we're having performance issues with our services at high traffic load and have been looking at ways to improve performance. One of the things that was identified that would improve performance, would be switching from using synchronous grpc to asynchronous grpc (https://grpc.github.io/grpc/python/grpc_asyncio.html). During the process of prototyping and testing grpcio-aio and trying to debug and profile, we found that no data was being sent to New Relic APM. We were able to see the container and see it's CPU/Memory usage and such, but no info regarding requests was being captured at all.

This is obviously a huge problem for us, since we're heavily integrated into New Relic at the moment and moving to grpcio-aoi is something we definitely want to move toward as not doing so means, we can't start migrating customers from the legacy enviroment to our new Micro-services environment, so not being able to use grpcio-aio with New Relic is huge road block for us and something we need to resolve ASAP.

Feature Description

The same support we have for gRPC to be replicated Async gRPC

Describe Alternatives

N/A

Additional context

I have logged this via New Relic support too, feature request: PYTHON-I-151. They said it would be beneficial to post the request here too.

Priority

Blocker

@stale
Copy link

stale bot commented Oct 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 24, 2021
@synackSA
Copy link
Author

synackSA commented Mar 8, 2022

I mean, it would still be nice it it was supported...

@stale stale bot removed the stale label Mar 8, 2022
@stale
Copy link

stale bot commented Jun 13, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 13, 2022
@GabrielCappelli
Copy link

GabrielCappelli commented Oct 11, 2022

I've also migrated from sync gRPC to async gRPC and instrumentation no longer works 😞

@stale stale bot removed the stale label Oct 11, 2022
@stale
Copy link

stale bot commented Dec 24, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 24, 2022
@MrBeeMovie
Copy link

Is anyone going to look at this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants