Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Commit

Permalink
Document how the New Relic middleware works (closes #2)
Browse files Browse the repository at this point in the history
  • Loading branch information
Sam Stenvall committed Jan 24, 2018
1 parent df3f236 commit 591561d
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions README.md
Expand Up @@ -151,6 +151,16 @@ Synchronizing content of type "article"...
Done, synchronized 300 entries
```

### New Relic middleware

If you use New Relic to monitor your application you will probably notice that all Contentful webhooks are lumped
together as a single transacation (since they all use the same URL/route).

However, if you apply the
`Digia\Lumen\ContentfulSync\Http\Middleware\NewRelicMiddleware` middleware to your route, transactions will be named
`topic@contentType`, e.g. `ContentManagement.Entry.publish@article`. This allows you to single in on particularly slow
webhooks.

### Asynchronous processing

In your service provider implementation you can specify an instance of `Illuminate\Contracts\Queue\Queue` to inject
Expand Down

0 comments on commit 591561d

Please sign in to comment.