What's the status of Feast's metrics system?

Is your feature request related to a problem? Please describe. When diving into Feast’s serving module(java), I found a Metrics class, it seems we have implemented a metric reporter for Prometheus. However, I did not find any usage of it. Just found a monitor section that statement Feast integrates with the StatsD ecosystem. But still do not find more documentation.

Any more information?

Describe the solution you’d like A clear and concise description of what you want to happen.

Describe alternatives you’ve considered A clear and concise description of any alternative solutions or features you’ve considered.

Additional context Add any other context or screenshots about the feature request here.

[adchia]

Hey! yeah there is no usage of that Metrics class today in Java and that documentation is a bit misleading (though I think it used to be used back when the Java library was Spring based and also exposed an HTTP endpoint). AFAICT, the metrics are still being populated, just not exposed via an endpoint. Should be not too bad to incorporate it though (e.g. expose a Jetty server and add the MetricsServlet)

The python feature server doesn’t yet use any StatsD client to push metrics.

[creativedutchmen]

Got it. To provide one extra data-point in how I’d like to consume the metrics: the feature server is a long-lived instance, so having a prometheus /metrics endpoint would be great. I’d really only need to see some basic things like timings and request stats - that would already help a great deal.