[
https://issues.apache.org/jira/browse/TIKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327069#comment-17327069
]
ASF GitHub Bot commented on TIKA-3353:
--------------------------------------
Subhajitdas298 commented on pull request #429:
URL: https://github.com/apache/tika/pull/429#issuecomment-824499807
@tballison Please review the PR and let me know, if anything has to be
modified.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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.3.4#803005)
