Spray Framework monitoring with DripStat

We have released support for Spray Framework starting from DripStat Agent 6.1.15.

Monitoring Spray framework requires a little bit of extra work since the controller methods in Spray are inside a set of ‘Routes’ which are formed using Spray’s own DSL. Thus there is no real ‘method name‘ we can use to name your Transactions.

The recently released DripStat-API jar contains support for adding custom names to your transactions, which will need to be used here. Just add an extra line inside your routes to name the Transactions to your liking. Eg:

path("hello") {
        get {
          complete {
            DripStat.setCurrentTransactionName("hello")
            //code...
            "hi"
          }
      }
}

The current implementation of Spray support has similar limitations as Play Framework support. We are working to get over these asap.

Related Links:

Show Comments