[ 
https://issues.apache.org/jira/browse/TIKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824496#comment-17824496
 ] 

ASF GitHub Bot commented on TIKA-3353:
--------------------------------------

lewismc commented on PR #429:
URL: https://github.com/apache/tika/pull/429#issuecomment-1984126967

   Hi @tballison 
   
   > ...would you have any time to help with this?
   
   Yes once I’ve finished an upgrade to JUnit Jupiter for Nutch. This would be 
a great feature for Tika 3.X server.




> Tika Server Production ready monitoring (Prometheus and JMX)
> ------------------------------------------------------------
>
>                 Key: TIKA-3353
>                 URL: https://issues.apache.org/jira/browse/TIKA-3353
>             Project: Tika
>          Issue Type: New Feature
>          Components: server
>    Affects Versions: 2.0.0, 1.26
>            Reporter: Subhajit Das
>            Priority: Major
>              Labels: features
>
> Tika Server only has Server status (/status and it's MBean).
> The MBean, in conjunction with JMX exporter can be used for Prometheus 
> exporting. But it will be oblivious to details, such as time taken to process 
> a request and so on.
>  
> New standard metrics collection system to be implemented, with help 
> [Micrometer|https://micrometer.io/] metrics system, with [CXF 
> pluggability|https://cxf.apache.org/docs/micrometer.html].
> The metrics data can be exported to most of industry standard monitoring 
> tools format (such as Prometheus/Grafana, Gangila etc).
>  
> Prometheus and JMX metrics can be implemented with core metrics collection.
> Choice metrics reporting and nature of metrics can be configured by user.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to