Splunk AppDynamics

PHP agent: framework detected, but BT is still WEB, not correlating

CommunityUser
Splunk Employee
Splunk Employee

Can anyone explain the log message:

[correlation.CurlExecInterceptor] framework detected, but BT is still WEB, not correlating

Reporting is unaffected, but I'm wondering if I'm missing some detail while this error is being logged.

It's a Symfony 3.4 app on PHP 7.1.

Thanks in advance.

Steve 

Labels (1)
0 Karma
1 Solution

Kyle_Furlong
Contributor

Hi Steve,

This message is completely normal. What this is saying is that during the time before we've identified your Symfony transaction, we can't yet send out the information to a downstream agent. This means that these HTTP exit calls will not correlate. If you would like these calls to have correlation, you can disable the PHP MVC transaction detection. In that case you'd have the BT discovered based on URL.

Please let us know if you have any further questions or concerns.

Regards,

Kyle

View solution in original post

Kyle_Furlong
Contributor

Hi Steve,

This message is completely normal. What this is saying is that during the time before we've identified your Symfony transaction, we can't yet send out the information to a downstream agent. This means that these HTTP exit calls will not correlate. If you would like these calls to have correlation, you can disable the PHP MVC transaction detection. In that case you'd have the BT discovered based on URL.

Please let us know if you have any further questions or concerns.

Regards,

Kyle

Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...