Page-load transactions without result status

[Harm]

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.6.2

Elasticsearch version: 7.6.2

APM Server version: 7.6.2

APM Agent language and version: js-base 4.9.1

Browser version: Chrome 81.x

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

Fresh install or upgraded from other version? N/A

Is there anything special in your setup? APM-server connected via Logstash

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

Hi, if I understood correctly, the 'Transactions per minute' graph shows the number of transactions grouped by transaction.result. For the page-load transactions this data is not available. Is it intentionally like that?

Would it be possible to include a success (or failed) status, when for example all the spans (DNS, Load, Processing, etc) completed succesfully? Or when all the requests completed with a non error (4xx, 5xx)?

Steps to reproduce:

1. Select service
2. Transaction type: page-load

Errors in browser console (if relevant): N/A

Provide logs and/or server output (if relevant): N/A

[vigneshshanmugam]

Hi @Harm,

Apologies for the delay in responding.

For the page-load transactions this data is not available. Is it intentionally like that?

Yes you are right, we dont set the transaction.result for page-load transactions as its a browser event and would be always successful no matter what.

However, I have created an issue in the agent where we can do this for API transactions Reevaluate if API calls context can be added to transactions instead of spans · Issue #786 · elastic/apm-agent-rum-js · GitHub and annotate it correctly like how backends agent are doing at the moment.

Would it be possible to include a success (or failed) status, when for example all the spans (DNS, Load, Processing, etc) completed successfully?

These custom Spans are created based on the events in the browser load itself and would not make sense to annotate. Please do let us know if you have any ideas

Thanks,
Vignesh

[Harm]

Hi @vigneshshanmugam, thanks for adding the issue on the API transactions.

For the page-load transactions, would it be an option to set the
transaction.result (2xx, 4xx, ..) based upon the browser result for the transaction.page.url?

Just thinking.