Custom error properties not shown

Describe the bug Opbeat used to copy over error properties to custom or at least show the extra properties in the extra tab. Now they are being logged under error.exception.attributes but not shown in the custom tab on the errors page in Kibana. Is there a way to get this functionality back? This is super useful info when fixing errors.

To Reproduce

const error = new Error('oops');
error.usefulExtraProp = 'all the data';
apm.captureError(error);

Expected behavior see top

Environment (please complete the following information)

• OS: mac (any)
• Node.js version: 8
• APM Server version: don’t know
• Agent version: 1.5.4

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 Add any other context about the problem here.

• Agent config options

  Click to expand

  replace this line with your agent config options
  

• package.json dependencies:

  Click to expand

  replace this line with your dependencies section from package.json
  

[sqren]

@alvarolobato Let’s discuss it at the next APM weekly, and prioritise it there.

[watson]

Yeah, I agree it would make a lot of sense to show this data. I’m glad you found a workaround for now, but I’ll make sure to raise this with the UI team so we can look into what can be done.

cc @elastic/apm-ui