pinkeen/api-debug-bundle
Composer 安装命令:
composer require pinkeen/api-debug-bundle
包简介
Allows easy API consumer debugging with web debug toolbar extension.
README 文档
README
This bundle adds a web debug toolbar tab which displays information about API consumer requests.
It aims to be universal and allow for easy integration with SDKs and HTTP client libraries.
Currently it supports Guzzle 6 out-of-the box.
It should be extremely easy to integrate with any http client using PSR-7 messages.
For Guzzle4-compatible version use the v1.0 tag.
For Symfony < 3.3-compatible version use the v2.0 tag.
Requirements
- PHP 5.5.9
- Symfony 3.3
Installation
The usual Symfony stuff.
The composer.json needs: "pinkeen/api-debug-bundle": "dev-master",.
The AppKernel.php needs: new Pinkeen\ApiDebugBundle\PinkeenApiDebugBundle(),.
Add the following to your app/config/routing_dev.yml if you want to be able to view raw body data:
_api_debug: resource: "@PinkeenApiDebugBundle/Resources/config/routing.yml" prefix: /_profiler
Services
New symfony approach
All services expect GuzzleClientFactory and RingPHPHandlerFactory are private, which means you cannot fetch services directly from the container via $container->get().
They are also automatically registered and set to autowire, all you need to do add type-hinted service to your class as an argument of contructor.
// src/AppBundle/Service/FooService.php // ... use Pinkeen\ApiDebugBundle\Bridge\Guzzle\Middleware\DataCollectorMiddleware; class FooService { private $dataCollectorMiddleware; public function __construct(DataCollectorMiddleware $dataCollectorMiddleware) { $this->dataCollectorMiddleware = $dataCollectorMiddleware; } // ... }
Usage
Integrate with your custom client
Firstly you have to subclass
AbstractCallData
which holds data from a single API request.
If you are using a PSR-7 comptible client then you can use PsrCallData
instead of writing your own data class.
Then every time your API consumer makes a request dispatch an ApiEvents::API_CALL event.
use Pinkeen\ApiDebugBundle\ApiEvents; use Pinkeen\ApiDebugBundle\Event\ApiCallEvent; /* ... */ /** @var $eventDispatcher \Symfony\Component\EventDispatcher\EventDispatcher */ $eventDispatcher->dispatch( ApiEvents::API_CALL, new ApiCallEvent( new YourApiCallData(/* your params */) ) );
Guzzle
You've got two options here, either:
Let the bundle create the client for you...
/** @var $guzzleClientFactory \Pinkeen\ApiDebugBundle\Bridge\Guzzle\Service\GuzzleClientFactory */ $guzzleClientFactory->create([ /* Guzzle client config (optional). * It is passed directly to GuzzleHttp\Client constructor. */ ]);
... or push the collector handler to your middleware stack.
$handler = new GuzzleHttp\HandlerStack(new GuzzleHttp\Handler\CurlHandler()); /** @var $dataCollectorMiddleware \Pinkeen\ApiDebugBundle\Bridge\Guzzle\Middleware\DataCollectorMiddleware */ $dataCollectorMiddlewareHandler = $dataCollectorMiddleware->getHandler(); $handler->push($dataCollectorMiddlewareHandler); $client = new GuzzleHttp\Client(['handler' => $handler]);
RingPHP
Let the bundle create the handler for you:
/** @var $ringPHPHandlerFactory \Pinkeen\ApiDebugBundle\Bridge\RingPHP\Service\RingPHPHandlerFactory */ $handler = $ringPHPHandlerFactory->create(new CurlHandler());
Use the collector_middleware service to create your RingPHP middleware and wrap it around your base handler:
/** @var $dataCollectorMiddleware \Pinkeen\ApiDebugBundle\Bridge\RingPHP\Middleware\DataCollectorMiddleware */ $ringPhpHandler = $dataCollectorMiddleware->createHandler(new GuzzleHttp\Ring\Client\CurlHandler(), 'apiname');
PS Nicely integrates with elasticsearch-php 2.0.
Production
For production environment you probably want to skip all of the data gathering.
You should take care of that yourself, unless you're using Pinkeen\ApiDebugBundle\Bridge\Guzzle\Service\GuzzleClientFactory or
Pinkeen\ApiDebugBundle\Bridge\RingPHP\Service\RingPHPHandlerFactory which skip it when not in debug mode.
Notes
I haven't found an easy way to get call duration out of guzzle6, so there's a regression here. If anybody has an idea please give me a shout.
pinkeen/api-debug-bundle 适用场景与选型建议
pinkeen/api-debug-bundle 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 702 次下载、GitHub Stars 达 1, 最近一次更新时间为 2014 年 04 月 01 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「symfony」 「debug」 「api」 「bundle」 「Guzzle」 「toolbar」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 pinkeen/api-debug-bundle 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 pinkeen/api-debug-bundle 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 pinkeen/api-debug-bundle 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Debug your SimpleBus EventBus and CommandBus
nice output for debug functions for PHP 5.3
The bundle for easy using json-rpc api on your project
Analysis module for finding problematical shop data.
Twig extensions for Tracy Debugger
A PSR-7 compatible library for making CRUD API endpoints
统计信息
- 总下载量: 702
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 1
- 点击次数: 11
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2014-04-01
