On the Metrics page, I thought I might find whether Pedestal exposes an endpoint (like prometheus) that I should be aware of, whether or not I am "using" Pedestal's metrics.

Just getting started there, I want to have a page that talks about setting up metrics, with lots of links to Open Telemetry’s docs. But the basic thing “put this in your pedestal project” and “start up a Docker instance running Jaeger” and “open this page and play around”. Also: download the OT Java agent, and here’s how you hook it into your app.

I think I’m slowing down on code changes for 0.7 and focusing one docs over the next period of time. I don’t know that Pedestal Netty is going to happen in 0.8. Some things in the 0.7 timeline may be shifted out a milestone.

The new home page is eloquent. One sentence is a little strange, "We wrote Pedestal to bring Clojure’s key attributes, Focus, Empowerment, and Simplicity, to the Clojure web development." --- I think it would be fair (and, although more grandiose, nonetheless accurate) to delete "the Clojure".

I would like to focus the cleverness of this august Forum on the "Late binding" section of the new Pedestal 0.7 home page... to strengthen "why" this is a good thing. (By the way, is it referring to interceptors modifying the interceptor chain?)

All good comments.

Thanks for reading.

This could all use some work. There were a lot of fingers in the pie before I showed up, but I’m gradually getting a more unified voice on the docs. Late binding: party, yes, the interceptor model … but also the fact that there all these core protocol (Router, RouterSpec, etc.) that have Pedestal-supplied implementations, but can be implemented in application specific ways if you have extraordinary needs of some kind.