Feature Idea: Yii2 support as framework

+1 from me too. Would be great if we had this feature.

+1 vote for adding Yii2 support to newrelic PHP Agent. We have recently upgraded from Yii to Yii2 and server transactions are no longer automatically identified.

@bogdan_stoik and @sergey_tsivin

I’ve filed the feature requests individually for both of you.

+1 vote for Yii2 support

hey @mario1, I’ve filed a feature request for Yii2 support for you as well.

We are also using yii2 on production so would be great to have!

Please add us to this list.

Hi @spyros,
I have logged a request on your behalf :smile:

Are there any work-arounds you could provide to get more details information and in particular to name our transactions so they don’t all appear as index.php? I know the instructions are given here:

https://docs.newrelic.com/docs/agents/php-agent/troubleshooting/transactions-named-indexphp-or-unknown

However, it’s not explained where this block of code has to be inserted.

@eric_tucker

The best place to use the naming transaction API call is wherever your custom routing is taking place.

With Yii2 you should have a route and controller. These should help decide where the request is going to. This is the simplest place to start. If you name based on variable filling route and controller data, you should be able to create useful names.

http://www.yiiframework.com/doc-2.0/guide-runtime-routing.html#routing

I hope this helps.

Hi,

I’d also like to see support for Yii2 sometime in the near future.

Thanks.

That has been logged as a feature request in your name @laithz

Thanks for letting us know.

1 Like

Please, add my +1 for Yii2 support.

@vyants
Of course! Added just there. Thanks for letting us know :smiley:

Done this as a composer package

4 Likes

@bazilio

Awesome! How do you transaction namings look now you’ve deployed your own plugin? If you have a link to an active application using it I’d love to take a look. Great example of using the API to achieve your goal :smile:

Like this: $app->controller->id . '/' . $app->requestedAction->id or site/index

App: https://rpm.newrelic.com/accounts/981338/applications/6524805

1 Like

Looks really clean and functional. Like what you’ve done there. Excellent use of our API. I hope others find it as useful until we have baked in support for Yii2.

I would love native support for yii2 in NewRelic. We are slowly upgrading our yii1 apps to yii2 and it’s sad that each time, we lose the visibility of our app in NewRelic.

We have tried the https://github.com/bazilio91/yii2-newrelic solution and we are grateful for it but somehow we’re missing some things, in particular, the error reporting doesn’t seem to work.

2 Likes

Would be great to have a native yii2 support as it will improive teh usage in our app.

Is it planned for this to happen?

1 Like

I can’t speak directly to our roadmap plans, @tomfotherby but please vote above! Our Product Managers come here to check in on use cases and amount of interest. Thanks!