- How do I install goatform/api-tracker-bundle?
- Install it with Composer using composer require goatform/api-tracker-bundle. Then register the bundle in your Symfony application's bundle configuration, typically config/bundles.php for Symfony Flex apps. After registration, add the bundle configuration and clear the cache. Check the repository README for the exact configuration keys and any required environment variables.
- What does GoatForm API Tracker Bundle actually track?
- It records API request and response activity so you can inspect outgoing calls made by your application. The overview describes structured API request tracking rather than scattered custom logging code. It is intended for debugging integrations, auditing traffic, and improving visibility into API usage. The exact fields recorded depend on the bundle's configuration and extensibility points.
- Is goatform/api-tracker-bundle compatible with Laravel?
- No. This is a Symfony bundle, not a Laravel package, and it integrates through Symfony bundle configuration rather than a Laravel service provider. Laravel applications would need a different package or a custom integration. If you are evaluating it for Laravel, treat it as a reference implementation rather than a drop-in dependency.
- How do I configure API tracking in a Symfony app?
- Configuration is handled through the bundle's Symfony configuration, usually in config/packages. You enable tracking and set options that match your logging or monitoring approach. Because the bundle is described as extensible, you can adapt it to existing logging stacks. Consult the README for the supported configuration tree and defaults.
- Which Symfony versions does this bundle support?
- The repository does not list supported versions in the provided overview, so check composer.json for its Symfony framework and component constraints. Confirm the constraints against the Symfony version in your application before installing. If you are on an older or newer Symfony release, test in a non-production environment first.
- Can I use goatform/api-tracker-bundle in production?
- It is designed to help maintain visibility into API usage in development or production. Before enabling it in production, consider the volume of API traffic, where records are stored, and whether any sensitive request data is captured. Review the bundle's configuration and your logging retention policies. Test with representative traffic to avoid performance or storage surprises.
- Does the bundle log API keys, tokens, or other sensitive data?
- The provided overview does not specify redaction behavior, so you must review what request and response data the bundle records. API tracking often captures headers and payloads that may contain credentials. Configure redaction or extend the tracker before using it with authenticated third-party APIs. Never enable verbose tracking on sensitive endpoints without a review.
- How do I test API tracking without calling real APIs?
- Use Symfony's HTTP client test utilities and mock responses so outgoing calls are simulated while the bundle records them. Keep tracking assertions focused on the data your application needs, and disable or redirect tracker storage during test runs if necessary. This lets you verify tracking behavior without external dependencies. Add tests around any custom configuration so later changes do not silently break tracking.
- What are alternatives to goatform/api-tracker-bundle?
- Alternatives include Symfony's HttpClient events, the Symfony profiler, Monolog channels, and API gateway or proxy logs. The bundle is described as fitting into existing logging and monitoring stacks rather than replacing them. Use it when you want structured visibility into outgoing API activity without scattering custom logging calls through your code. Laravel teams should look for Laravel-specific API tracking or logging packages instead.
- Is the bundle actively maintained and how do I extend it?
- Check the GitHub repository for recent commits, releases, and open issues before adopting it, because maintenance activity is not described in the provided overview. The bundle is described as extensible, so customization should happen through its configuration and extension points rather than editing vendor code. Keep customizations in your application or a small decorator so Composer updates remain safe. Pin a tested version in composer.json and add tests around any custom tracking behavior.