-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Elastic exporter not picking up DB queries #1961
Comments
Any update here? |
Thanks for the ping @andrewhsu! @bhupesh-sf can you please add a logging exporter to the traces pipeline, capture the output, and point out which spans are not being captured in Elastic APM? Providing a screenshot of a trace waterfall in Elastic APM may also be helpful. |
Hello @bhupesh-sf , friendly ping, can you provide more details as @axw asked? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
I am using elastic exporter and when I go to elastic it shows me trace and shows only one pg query whereas it has 4-5 queries. If I use elastic agent it shows me all.
Steps to reproduce
My flow is I call a facade from postman which calls a service which makes DB request 3-4 times and then calls another service which again calls db and then fails.
What did you expect to see?
I should be seeing everything logged in trace as its been with elastic agent.
What did you see instead?
DB queries are completely missing also no 40 not found badge which comes when I use elastic agent
What version did you use?
Version: v0.17.0
What config did you use?
Config:
`
receivers:
Environment
OS: Ubuntu 20.04
The text was updated successfully, but these errors were encountered: