[Q] Access to http server pool events

[vasilevrv]

Hello!

I need to add event listeners to http server pool for observe faults and send to Sentry. For example https://github.com/UPDG/roadrunner-sentry

How can i do it in v2?

[rustatian]

Hey @vasilevrv . This part of the RR2 left the same as was in the RR1 (but will be reworked in the future versions). You can provide your listener directly to the https://github.com/spiral/roadrunner-plugins/blob/master/server/plugin.go#L143 NewWorkerPool method.

[vasilevrv]

@rustatian, ok, thanks!

[vasilevrv]

The easiest solution for you at the moment will be to fork the http plugin, add sentry DSN to its config and add your listeners to the pool here https://github.com/spiral/roadrunner-plugins/blob/master/http/plugin.go#L153 and here https://github.com/spiral/roadrunner-plugins/blob/master/http/plugin.go#L333.
Then replace our http plugin with your in the roadrunner-bundle.
In the near future, you'll be able to attach to the smt like central events bus for the particular event from any plugin.

is there an estimate date when it is planned to do?

[rustatian]

I guess 1-2 months. Here is the ticket: roadrunner-server/roadrunner#496

[vasilevrv]

thanks!

[rustatian]

HTTP will not expose any events anymore (and will not expose in the future). You may create a simple HTTP middleware w/o binding to the HTTP plugin directly. You may have a look at the different middleware here: https://github.com/spiral/roadrunner-plugins/tree/master/http/middleware.
As basic advice on how to create a sentry middleware:

• Create a configuration -> example: https://github.com/spiral/roadrunner-plugins/blob/master/http/middleware/static/config.go

http:
  sentry:
    dsn: ...
    user: ...
    other_options: ...

• Implement Middleware interface: https://github.com/spiral/roadrunner-plugins/blob/master/http/middleware/static/plugin.go#L99
• Create Init (mandatory), Name functions, and optional Serve/Stop.
• In the Middleware function, wrap the http.ResponseWriter interface, get all needed http codes, messages and build your logic based on this info. Wrapper sample: https://github.com/spiral/roadrunner-plugins/blob/master/http/middleware/new_relic/writer.go
  Wrapper usage sample (make sure you use a sync.Pool): https://github.com/spiral/roadrunner-plugins/blob/master/http/middleware/new_relic/plugin.go#L77

If you need help, please, file a detailed feature request and I'll implement this middleware in a generic way (for all users).