innmind / profiler
App profiler
5.0.0
2026-03-21 15:57 UTC
Requires
- php: ~8.4
- innmind/foundation: ~2.1
- innmind/framework: ^4.0.1
- innmind/url-template: ~4.0
- ramsey/uuid: ~4.7
Requires (Dev)
- innmind/black-box: ~6.5
- innmind/coding-standard: ~2.0
- innmind/static-analysis: ~1.3
Provides
Conflicts
- innmind/xml: <9.1
This package is auto-updated.
Last update: 2026-03-21 15:58:33 UTC
README
App profiler to help profile any kind of applications (http or cli).
This package can be integrated in an existing app (using innmind/framework) or run as a standalone app
Installation
composer require innmind/profiler
Overview
The profiler contains 2 types of entities: a profile and sections.
A profile contains a name (usually the http path called or the cli), the point in time the profile started, the status (succeeded, failed or pending) and an exit message.
A section is a part of a profile. By default there are 9 sections:
- Http: the request and response (if the app didn't crash) the app received
- Exception: the stack trace represented as graph (see
innmind/stack-trace) - App graph: the object graph representing the application (see
innmind/object-graph) - Call graph: a flamechart
- Environment: the list of environment variables
- Processes: the list of commands run on the machine
- Remote
- Http: all the http requests issued by the application
- Processes: all the commands run on a distant machine
- Sql: all the SQL queries issued to a database
Documentation
All the documentation can be found in the docs folder.







