Mikael Schirén
Mikael Schirén
The site we have the issue on would be regarded as a high traffic site. For low traffic instances, we don't see the issue at the moment.
I get more or less the same error: ``` 2021-06-09 20:34:19.318914+00:00 [ERROR] [Auto-Instrumentation] [TransactionForExtensionRequest.php:286] [getMandatoryServerVarElement] $_SERVER does not contain `REQUEST_METHOD' key. {"namespace":"Elastic\\Apm\\Impl\\AutoInstrument","class":"TransactionForExtensionRequest","stacktrace":[{"class":"Elastic\\Apm\\Impl\\Log\\Backend","function":"log","file":"EnabledLoggerProxy.php","line":80,"this":{"type":"Elastic\\Apm\\Impl\\Log\\Backend","object_ID":35,"object_hash":"0000000028b240760000000051a020ce"},"args":[2,"$_SERVER does not contain `REQUEST_METHOD' key",[],286,"getMandatoryServerVarElement",{"category":"Auto-Instrumentation","namespace":"Elastic\\Apm\\Impl\\AutoInstrument","fqClassName":"Elastic\\Apm\\Impl\\AutoInstrument\\TransactionForExtensionRequest","srcCodeFile":"\/opt\/elastic\/apm-agent-php\/src\/ElasticApm\/Impl\/AutoInstrument\/TransactionForExtensionRequest.php","inheritedData":null,"context":[],"backend":{}},null,1]},{"class":"Elastic\\Apm\\Impl\\Log\\EnabledLoggerProxy","function":"log","file":"TransactionForExtensionRequest.php","line":287,"this":{"type":"Elastic\\Apm\\Impl\\Log\\EnabledLoggerProxy","object_ID":32,"object_hash":"0000000028b240750000000051a020ce"},"args":["$_SERVER does not contain...
We also see much more need for RAM since upgrading our setups, with a lot of traffic.
My thinking is when you need to trace an application in a distributed environment, like in Kubernetes. And collect all the traces to the same endpoint. Personally - I prefer...
Yes I am aware this - though auto tracing is not yet possible with OpenTelemetry (what I know). The requests itself comes from some of our developers.
Nginx conf: ``` worker_processes 5; load_module modules/ngx_http_geoip2_module.so; # load_module modules/ngx_http_naxsi_module.so; events { worker_connections 768; } pid /tmp/nginx.pid; http { upstream backend { server matomo:9000; } include /etc/nginx/mime.types; geoip2 /usr/share/geoip/GeoLite2-Country.mmdb {...
Additional info: The interface runs on seperate URL than the tracking, that is why we are blocking access to tracking scripts from it.
No, errors shown:
Though, when I try to get the Install code for TagManager, I get: