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

Latency handling for concurrent calls per transaction is not handled #20

Open
priyamgoenka1 opened this issue Sep 5, 2024 · 0 comments

Comments

@priyamgoenka1
Copy link

priyamgoenka1 commented Sep 5, 2024

Hey,
Facing an issue using new relic for micro-service external call monitoring. What expected is if an external call takes 10ms time and there are 100 concurrent calls in a transaction the latency of a single transaction shouldn't add up this value to increase the final latency on the monitoring by 1s.

Because of this I am unable to get actual latency for my requests and adding alerting on this is quite dicey as concern for me is to raise an issue if the latency is affected, not if the number of batch calls are increasing. Supposing a case where I call external service in loop of go routines.

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

No branches or pull requests

1 participant