Option to disable automatic error capturing

mohamed_jusail · April 26, 2022, 8:38am

Option to disable automatic error capturing

opened 02:38PM - 23 Apr 22 UTC

triage agent-nodejs community

``try { throw new Error('Method not allowed'); }catch(err) { apm.cap…tureError(err); res.send(500).json({message: err.message}); }`` Let's assume a scenario as above. In this scenario, there will be two errors logged in to the `Elastic Discover`. 1. Error captured automatically by apm agent 2. Error captured by `apm.captureError() `method In the Discover, those two errors will be logged as below. ![Screen Shot 2022-04-23 at 8 02 00 PM](https://user-images.githubusercontent.com/38158937/164910414-bf6bbe14-922d-4652-98fb-56e09ba40167.png) As displayed in this screenshot, there will be two errors logged. Among those two, one has the error message but other one doesn't. I think it would be better if there is an option to disable this automatic error capturing feature. If we capture the error using `apm.captureError()`method, there should be only one error logged in the Discovery.

trentm · April 26, 2022, 3:50pm

Hi @mohamed_jusail. I've replied to Dulajdeshan on the GitHub issue.

Topic		Replies	Views
APM nodejs agent Errors not Showing in Kibana APM nodejs	5	795	November 15, 2021
How to send error message to Elastic APM and show the error in Kibana tab APM nodejs , aws-lambda	9	2020	May 2, 2023
Elastic APM hides error message in log APM nodejs	2	652	October 4, 2019
Displaying custom errors in Kibana APM using java agent APM java , ui	6	1180	February 3, 2021
Errors are not logged to APM APM rum , server	7	855	July 13, 2020

Option to disable automatic error capturing

Related topics