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.

error.exception.message not truncated

See original GitHub issue

Describe the bug Not sure if this is by design but error.exception.message is not truncated which creates problems when it’s too long (e.g. knex includes the whole SQL query in the message).

Expected behavior I’d expect it to be truncated like other fields.

Environment (please complete the following information)

OS: Linux
Node.js version: 8
APM Server version: 6.2.4
Agent version: 1.6.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

Issue Analytics

State:
Created 5 years ago
Comments:11 (7 by maintainers)

Top GitHub Comments

2reactions

jalvzcommented, Jun 8, 2018

my 2c: If we only had the dashboards, I’d say truncate in the agents. But some users might chose a different output (eg Kafka) and/or they might want to consumer the data differently, and they might not want us to truncate too aggressively. So I think we should truncate in the agents to something reasonable from a data processing perspective (a few Mbs is reasonable I think, but not a few Gbs) and truncate it further in the UI to something reasonable for displaying.

1reaction

watsoncommented, Jun 23, 2018

I’ve opened an issue in the APM Server repo (as that’s where the dashboards live) to make sure this gets fixed: https://github.com/elastic/apm-server/issues/1021

Top Results From Across the Web

Guzzle Error Message gets truncated - Laracasts

I am using a try/catch already - but strange, for both Exception and the \GuzzleHttp\Exception\ClientException there is no getBody() method. I have setup...

Error logging is truncated in Laravel of Guzzle http

Guzzle http is truncating exceptions with more than 120 characters, but I need to log the full exception message. How can I do...

Exception Message truncation isn't so friendly #2185 - GitHub

(truncated). I'm using Laravel and Bugsnag, so error handling and reporting is pretty much out of the box. I tried catching the Guzzle ......

Solving: Guzzle errors truncated - A Laravel and PHP Blog

use GuzzleHttp\Client; use Exception; try { $client = new Client; ... when there is an error returned from the API the errors are...

How do I get the un-truncated error message from dblog?

Drupal is using debug_backtrace() for displaying and Exception::getTraceAsString was added for logging in Drupal 8.2.x. See the change record.