86d2f6ec9d
Annotates the routing tree with a middleware that instruments each endpoint in your servant application. For each endpoint we will keep track of a histogram with request latency + request count Captures are automatically filtered; such that /users/13813 and /users/24774 get mapped to the same metric. Unfortunately the name of the capture is not preserved; as we throw away that data when we're at the point of routing. We could perhaps change this but it's more significant change. |
||
|---|---|---|
| .. | ||
| example | ||
| src | ||
| test | ||
| CHANGELOG.md | ||
| LICENSE | ||
| README.md | ||
| servant-server.cabal | ||
| Setup.hs | ||
servant-server
This library lets you implement an HTTP server with handlers for each endpoint of a servant API, handling most of the boilerplate for you.
Getting started
We've written a tutorial guide that introduces the core types and features of servant. After this article, you should be able to write your first servant webservices, learning the rest from the haddocks' examples.