Kibana version: 7.6.2
Elasticsearch version: 7.6.2
APM Server version: 7.9.0
APM Agent language and version: PHP commit 8eccf0b4657533d1848d5541a250096d2f436482
Browser version: N/A
PHP version: 7.2.24-0ubuntu0.18.04.6
Original install method (e.g. download page, yum, deb, from source, etc.) and version: From source
Fresh install or upgraded from other version? Fresh install
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.
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant): I expect transactions created by extension should cover the entire execution. However, the transaction ends within a few ms while the API actually takes a few hundreds of ms. I tried to create a span inside a laravel middleware (using
captureChildSpan public API) and its time span makes much more sense than the transaction itself.
Steps to reproduce:
- Clone PHP agent from the source. Build, install, config
- Enable config for php-fpm and restart php-fpm service.
- Observe results in Kibana.
Errors in browser console (if relevant): N/A
Provide logs and/or server output (if relevant): N/A Let me know if anything is needed.
I am new to Elastic APM and APM in general. Please correct me if I am wrong.
Is the current behavior the expected behavior? Is it due to the fact that the agent is still under development (I don't see an issue related to this opened though)?
Not sure what's the expected behavior so I decided to open a topic in discuss first.