[ODLPARENT-268] Consider integrating Jetty/Dropwizard metrics Created: 09/Nov/17  Updated: 05/Oct/21

Status: Open
Project: odlparent
Component/s: Karaf
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Medium
Reporter: Michael Vorburger Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by INFRAUTILS-19 Coda Hale Dropwizard Metrics integration Resolved

 Description   

Once the basic new INFRAUTILS-19 metrics is fully done and dusted, it could be useful to see how hard it would be to use http://metrics.dropwizard.io/3.1.0/manual/jetty/ to get metrics for the ODL Jetty HTTP server used e.g. by RESTCONF.

Similarly, if we use Jersey for REST APIs in ODL (do we?) then http://metrics.dropwizard.io/3.1.0/manual/jersey/ looks interesting.

I expect with Karaf OSGi and all, this may be a little more challenging than in some plain Spring Boot or whatever environment.

It depends on how we actually do Web stuff in ODL.. do we rely on OSGi Web support, or directly use the Jetty APIs?

 Comments   
Comment by Robert Varga [ 05/Oct/21 ]

We are relying on pax-exam to launch our endpoints, hence this should live in odlparent for now. We need to revisit the HTTP/JAX-RS story anyway, and with OSGi R8 (Karaf 4.4.x) we should have a few more options.

Generated at Wed Feb 07 20:28:04 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.