Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jaxrs-dev] Monitoring Statistics

Understood. Are you aware of other JAX-RS products besides Jersey which do support monitoring?

-Markus

 

From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of rawand takna
Sent: Freitag, 4. Januar 2019 11:56
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] Monitoring Statistics

 

A standard API for gathering monitoring statistics would be perfect, but JAX-RS does not define any.

All the monitoring statistics mechanisms are available as JERSEY extension modules.

 

that's why I thought that jersey would be able to add a such a feature on top of existing mechanisms already defined by the jersey project.

 

On Fri, Jan 4, 2019 at 9:48 AM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

I second that. As most JAX-RS stakeholders are MP committers, I do not see a majority for an additional JAX-RS-only solution. What we could do is to make the MP API mandatory to JAX-RS 3.x and define a set of default properties that all existing implementations can provide already.

-Markus

 

From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth
Sent: Freitag, 4. Januar 2019 07:30
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] Monitoring Statistics

 

I don't think that JAX-RS should build something JAX-RS specific for this. Instead, JAX-RS should integrate with a monitoring mechanism defined as part of the Jakarta EE platform.  MicroProfile Metrics would be a good candidate, but it is not part of the Jakarta EE platform (yet).

 

Am Do., 3. Jan. 2019 um 23:18 Uhr schrieb rawand takna <rawandtakna@xxxxxxxxx>:

Monitoring-Statistics gathering using jersey defined ways (Event Listeners, MonitoringStatistics, MXBeans with JConsole) is quite complex and hard to find what you are looking for easily.
 
My suggestion would be to add a feature that allows developers to annotate their resource classes and resource methods with @MStatistics("URI") annotation where the URI is a relative URI to the resource's URI and would correspond to the resources statistics after being invoked using a browser (or any other client type).
 
 
example:
 
 
@MStatistics("stats")
@Path("resource")
public class MyResource
{
      @GET
      public String getResource()
      {
             return "Hello World";
      }
}
 
 
 
then the statistics would be available at URI: http://{host}:{port}/resource/stats

_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev


 

--

_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev

Back to the top