You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using inline comments in MySQL queries, the APM span name only shows /* instead of the actual SQL query. This makes it difficult to identify and monitor specific database operations in the APM UI.
To Reproduce
Steps to reproduce the behavior:
Configure Elastic APM Node.js agent and set up MySQL connection
Execute a query with inline comment like:
/* GetUserProfile */ SELECT * FROM users WHERE id = 1
Check the transaction in APM UI
Transaction name is shown generically as '/* ', ignoring the inline comment 'SELECT * FROM users' Expected behavior
The span name should display the actual SQL query (e.g., "SELECT * FROM users") rather than just showing /*. This would provide proper visibility into the database operations being performed and make it easier to monitor and debug database queries.
Environment (please complete the following information)
OS: macOS 14.3
Node.js version: 22.7.0
APM Server version: 8.12.0
Agent version: 4.11.0
How are you starting the agent? (please tick one of the boxes)
Describe the bug
When using inline comments in MySQL queries, the APM span name only shows /* instead of the actual SQL query. This makes it difficult to identify and monitor specific database operations in the APM UI.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The span name should display the actual SQL query (e.g., "SELECT * FROM users") rather than just showing /*. This would provide proper visibility into the database operations being performed and make it easier to monitor and debug database queries.
Environment (please complete the following information)
How are you starting the agent? (please tick one of the boxes)
agent.start()
directly (e.g.require('elastic-apm-node').start(...)
)elastic-apm-node/start
from within the source code-r elastic-apm-node/start
Additional context
Agent config options:
Click to expand
package.json
dependencies:Click to expand
The text was updated successfully, but these errors were encountered: