Discover service name automatically

[SergeyKleyman]

As step 1 we should define what is expected result for each use case (where use cases can be grouped by used web framework - WordPress, Laravel, etc.)

Consider when we can discover service name automatically:

• Investigate if developers already provide this information to some frameworks (Laravel, etc.)
• Investigate if we can extract service name from Apache/NGINX
• Investigate if we can extract service name from application location at the file system
• Investigate if there are other approaches

[philkra]

addendum: provide a manual override on the app level that trumps all previous investigations

[SergeyKleyman]

@philkra By "on the app level" do you mean by using agent's API in addition to configuration (I've added #70 to follow up on configuration part)?

[science695]

When thinking about this, keep in mind that some people may run multiple services as virtualhosts on the same server, or different php-fpm pools, etc...

Possible sources of data: composer.json or other package managers

[SergeyKleyman]

@science695 Great point. The challenge will be to find the application's composer.json file... Maybe we can instrument spl_autoload_register and get path to application's vendor directory when composer registers its autoload handler... It's going to be interesting :)