question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Version 3.32.0 regression database statement

See original GitHub issue

Describe the bug

With the new version 3.32.0 I don’t see the database statement in the Kibana APM dashboard

image

It seems also that the span is doubled :

image

With 3.31.0 I have the statement

image

To Reproduce

Upgrade to 3.32.0

Expected behavior

I should see the database statement in the APM Panel

Environment (please complete the following information)

  • OS: Linux
  • Node.js version: 14.18
  • APM Server version: 8.1.2
  • Agent version: 3.32.0

How are you starting the agent? (please tick one of the boxes)

  • Calling agent.start() directly (e.g. require('elastic-apm-node').start(...))
  • Requiring elastic-apm-node/start from within the source code
  • Starting node with -r elastic-apm-node/start

Additional context

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:8 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
astormcommented, May 23, 2022

@ddolcimascolo @descampskGood news – I spent some quality time with the specs and our implementation and the loss of the span.db.statement field appears to be a bug in our implementation and not something inherent to compressed spans. I’ve opened an issue with more information here:

https://github.com/elastic/apm-agent-nodejs/issues/2715

Until we land a fix for #2715 the best path forward is disable span compression. Once a fix for #2715 lands you should get those useful queries back, even when compression is enabled.

0reactions
ddolcimascolocommented, May 27, 2022

Thx!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Ensure Database Context is Sent for Compressed Spans #2715
This results in the statement field not being captured, and the Database statement ... Version 3.32.0 regression database statement #2671.
Read more >
SQLite Release 3.32.0 On 2020-05-22
INSERT and UPDATE statements now always apply column affinity before computing CHECK constraints. This bug fix could, in theory, cause problems ...
Read more >
Practical Regression and Anova using R
Students are expected to know the essentials of statistical inference like estimation, hypothesis testing and confidence intervals. A basic knowledge of data ......
Read more >
Generalized Linear Model (GLM) - H2O.ai Documentation
Use this parameter for logistic regression if the data has been sampled and the mean of response does not reflect reality.
Read more >
Using Stata for Logistic Regression - University of Notre Dame
Stata has various commands for doing logistic regression. ... 11 or higher is with the margins command (with older versions of Stata you....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found