Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Traceview Bundle

Traceview Bundle Laravel Package

appneta/traceview-bundle

AppNeta TraceView Bundle integrates TraceView (Tracy) application performance monitoring into Symfony apps, adding instrumentation and configuration to trace requests, database queries, and external calls for faster debugging and optimization.

View on GitHub
Deep Wiki
Context7

Additional integration with AppNeta TraceView for Symfony2 (or anything else using EventDispatcher/HTTPKernel).

Frequently asked questions about Traceview Bundle
Can I install appneta/traceview-bundle in a Laravel app?
No. It is a Symfony2 bundle constrained against symfony/framework-bundle 2.x, so composer require appneta/traceview-bundle fails dependency resolution before any boot logic runs. Even a forced install would be inert in Laravel because the Symfony kernel events it listens to never fire.
Does appneta/traceview-bundle support Laravel 10 or 11?
No. There is no supported version intersection between the bundle's Symfony 2.x constraints and the symfony/* component ranges required by Laravel 8 through 11. Treat it as incompatible rather than an untested edge case.
What does appneta/traceview-bundle actually do?
It is thin glue around the native TraceView PHP agent. The bundle adds roughly 30 to 60 lines of Symfony kernel event listeners that open and name transactions, for example AppBundle\Controller\OrderController::show, so requests and console commands appear readable in TraceView. The actual instrumentation comes from the native extension, not the bundle.
How would I add TraceView-style tracing to Laravel without this bundle?
Implement the pattern directly: a Laravel service provider plus global middleware that opens a transaction on each inbound request, tags it with route, controller, status and user, closes it in a finally block, and marks it errored from the exception handler. The assessment estimates about one engineer-day for this work, with none of the Symfony baggage.
Is appneta/traceview-bundle still maintained?
There is no evidence of active maintenance: zero stars, zero dependents, no visible CI, and no security-response path. It targets Symfony 2.x, which reached end of life in 2018. Treat it as abandoned and plan accordingly.
How do you install and configure it in a Symfony app?
Historically you would install the native TraceView PHP agent extension, require the bundle with Composer in a Symfony 2.x project, register it in AppKernel, and configure it through standard bundle configuration. That path is only relevant to legacy Symfony 2.x applications and does not transfer to Laravel.
Does the TraceView PHP agent work with modern PHP, PHP-FPM, and Laravel Octane?
That is unverified and high risk. The underlying PHP agent has not tracked modern PHP releases or long-lived-worker runtimes such as Octane, so you must confirm a supported agent build for your exact PHP version and runtime before relying on it. The repository provides no evidence of such support.
What data does TraceView capture, and are there PII or data-residency risks?
Trace payloads may capture PII, authorization headers, or query strings from live requests, and the repository does not answer this. Data residency and retention posture must come from the vendor. Treat these as open due-diligence questions before any production use.
Is there an OpenTelemetry or OTLP export path out of AppNeta TraceView?
The assessment found no OTLP escape hatch, meaning leaving later would be a re-instrumentation project rather than a configuration change. Confirm this directly with the vendor if exit strategy matters. Vendor-neutral instrumentation is the safer default.
What are the alternatives for Laravel application performance monitoring?
Use a maintained, vendor-neutral option rather than a Symfony 2.x bundle. OpenTelemetry-based APM gives you request timing and distributed traces without proprietary lock-in, and Laravel Telescope is useful for local debugging. The assessment notes a dozen maintained alternatives for the request-timing and APM capability.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console