Weave Code
Traceview Twig Laravel Package
appneta/traceview-twig
Twig extension for AppNeta TraceView that instruments template rendering, adding Twig template layers and render timings to PHP APM traces so you can see which templates are slow.
Additional Twig integration for AppNeta TraceView.
Frequently asked questions about Traceview Twig
- Is appneta/traceview-twig a Laravel package?
- No. It is a Twig extension that instruments template rendering for the AppNeta TraceView APM agent, and it has no Laravel-specific integration. Laravel renders views with Blade, so a standard Laravel application has no Twig environment for this package to hook into. The only realistic Laravel use case is an app that deliberately added Twig through something like rcrowe/twigbridge.
- How do I install appneta/traceview-twig?
- Install it with Composer using composer require appneta/traceview-twig, then register the extension against your Twig Environment. You also need the TraceView PHP agent installed and configured at the php.ini level, because the extension talks to that agent. There is no Laravel package auto-discovery or service provider here.
- Does appneta/traceview-twig work with Laravel Blade?
- No. Blade templates are compiled by Laravel's own engine and are not Twig, so the extension never sees them. It only adds spans around Twig render calls. If your app is Blade-first, this package has no insertion point and should not be installed.
- Which PHP and Laravel versions does appneta/traceview-twig support?
- There is no official Laravel support, because this is not a Laravel package. The code is PHP 5.x/7.x-era, and Twig 3 tightened interfaces that older extensions often violate, so expect deprecation noise or signature errors on PHP 8. Treat any compatibility patch as your own maintenance burden.
- Do I need the TraceView PHP agent for this package to work?
- Yes. The extension is a shim on top of the AppNeta TraceView PHP agent, which must be installed and loaded at the php.ini level. If the agent is missing or a different version, instrumentation libraries like this typically no-op silently or throw during template rendering. TraceView was retired after the SolarWinds acquisition, so the agent is effectively end-of-life.
- How do I register the Twig extension in my application?
- Create your Twig Environment as usual and add the TraceView extension to it, typically in the service provider or bootstrap code that builds the environment. That is the only supported integration shape. Once registered, the extension decorates template rendering with view-render spans that are sent to the configured TraceView agent.
- Is appneta/traceview-twig still maintained?
- There is no visible maintenance: the repository has zero stars and zero dependents and no active community. The backing TraceView product is no longer sold, so no one is patching this extension for new PHP or Twig versions. If you keep it, pin a commit SHA, vendor or mirror it internally, and treat it as frozen.
- What should I use instead of TraceView for template render timing?
- The recommended path is to retire TraceView and use OpenTelemetry PHP auto-instrumentation with your current APM, such as Datadog, New Relic, Sentry, or Tideways. If you only need coarse view-render timing, a generic span around your render call gives most of the value without an unmaintained dependency. Twig-level granularity is rarely worth owning a dead package.
- How can I test whether Twig template spans are being reported?
- First confirm the TraceView agent is loaded, for example with php -m or phpinfo, then render a Twig template in staging and inspect the APM trace for view-render spans. Do this with the real agent configured, because unit tests will not prove the extension is emitting data. If spans are missing, assume the extension is silently no-oping rather than trusting it.
- Is appneta/traceview-twig safe for production?
- It carries high risk: it is unmaintained, has no dependents or CVE review, and depends on an end-of-life APM agent. Instrumentation that silently no-ops can also give false confidence that template rendering is traced. Only keep it if TraceView is still your sanctioned APM, and then pin the commit, vendor it internally, and plan its removal.
Weaver
How can I help you explore Laravel packages today?