I don’t have any update yet. Our developers are working on trying to get something out for this in an upcoming release.
If the patch stops being a functional solution, instrumentation can be done manually using the newrelic_name_transaction(), the most convenience place to do such if the patch isn’t an option is in the Controller/Route section to name transactions based on its routing.
To disable automatic instrumentation (the reason you’re seeing an error with Laravel 5.2 is because this new version moves the location of files we use to instrument transactions and entry points to requests, so if you set in your newrelic.ini
newrelic.framework = "none"
This will stop our agent from detecting Laravel 5.2 temporarily, the error thrown for not found file will go away, but so will automatic naming. The above API function used in the right place passing the right values could solve the problem too.
Best place to keep an eye for a new agent release and if it contains a fix for the 5.2 issue is to keep an eye on our PHP Agent Release Notes.