Hi and thanks for the question
We are not capturing SQL statement parameters as of yet. As a matter of fact, we did not get a lot of requests for that so far, so it is not currently planned.
Based on your experience, did you find it valuable for identifying root cause of problems? Any other ways you found it very useful?
Thanks,
Eyal.
i found it very usefull, bcs i wasnt able to track down the root cause of a problem with elastic APM.
Then with glowroot i saw that this statement was in a transaction which caused the exception. And the Problem was that the exception message was "null" (bad lib..). So with the complete Query-Statement i was able to reproduce the problem.
Bcs. the Exception was only triggered with one specific ID in one specific Usecase...
It would be awesome when this feature would find its way to the agent. I get it when this can cause performance impacts, but maybe it can be added as a optional feature which can be enabled when needed.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.