disableInstrumentations for route-change

[Kartheek_Mannepalli]

If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text

Kibana version: 7.4.0

Elasticsearch version:7.4.0

APM Server version:7.4.0

APM Agent language and version: apm-rum-angular: 0.3.0

Browser version: Chrome 78

Original install method (e.g. download page, yum, deb, from source, etc.) and version:

Fresh install or upgraded from other version?

Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.
NO

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
I have this configured with my APM agent.

disableInstrumentations: ['page-load', 'route-change']

The page-load transaciton no longer show up but the route-change still show up. Is this a bug on your end or is there something I need to change?

[Hamidreza (Hamidreza Jahtalabziabari)]

Hi @Kartheek_Mannepalli,

Thanks for reaching out.

Currently, disableInstrumentations doesn't support disabling route changes, instead you should add disableInstrumentations: [history] to your config and remove the angular integration. You can instead use the base package @elastic/apm-rum to instrument your application.

I've also created this issue to make the configuration easier.

Cheers,
Hamid

[Kartheek_Mannepalli]

@Hamidreza Thanks for the response. The route-change is kind of helpful for us so we might keep the angular integration. I wanted to see if we have the option of disabling it in the future.