[jira] [Commented] (TIKA-3353) Tika Server Production ready monitoring (Prometheus and JMX)

[ https://issues.apache.org/jira/browse/TIKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17329163#comment-17329163 ] ASF GitHub Bot commented on TIKA-3353: -- tballison merged pull request #429: URL:

[GitHub] [tika] tballison merged pull request #429: [TIKA-3353] Prometheus and JMX monitoring over micrometer

tballison merged pull request #429: URL: https://github.com/apache/tika/pull/429 -- 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

[GitHub] [tika] tballison commented on pull request #429: [TIKA-3353] Prometheus and JMX monitoring over micrometer

tballison commented on pull request #429: URL: https://github.com/apache/tika/pull/429#issuecomment-824905053 @Subhajitdas298 , let's hold off on this for main/2.x for now. I'd like to upgrade to log4j2, and I'd like to make these extra dependencies loaded only if the user selects

[jira] [Commented] (TIKA-3353) Tika Server Production ready monitoring (Prometheus and JMX)

[ https://issues.apache.org/jira/browse/TIKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17329165#comment-17329165 ] ASF GitHub Bot commented on TIKA-3353: -- tballison commented on pull request #429: URL:

[jira] [Commented] (TIKA-3353) Tika Server Production ready monitoring (Prometheus and JMX)

[ https://issues.apache.org/jira/browse/TIKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17329204#comment-17329204 ] Hudson commented on TIKA-3353: -- SUCCESS: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #119 (See

[RELEASE] tika-helm 1.26 and 1.26-full

Hi user@ and dev@, I'm happy to announce the release of tika-helm [0] 1.26 and 1.26-full charts which are based off of the corresponding tika-docker [1] images of the same versions. *What is tika-helm?* A Helm chart to deploy Apache Tika

[jira] [Created] (TIKA-3363) Have tika-docker artifacts start in spawn mode (configurable)

Lewis John McGibbney created TIKA-3363: -- Summary: Have tika-docker artifacts start in spawn mode (configurable) Key: TIKA-3363 URL: https://issues.apache.org/jira/browse/TIKA-3363 Project: Tika

[jira] [Commented] (TIKA-3312) Support Log4j2 jar in Tika-app.jar

[ https://issues.apache.org/jira/browse/TIKA-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17329377#comment-17329377 ] Hudson commented on TIKA-3312: -- UNSTABLE: Integrated in Jenkins build Tika » tika-main-jdk8 #204 (See

[GitHub] [tika-docker] philipsoutham commented on pull request #4: Running as non-root user

philipsoutham commented on pull request #4: URL: https://github.com/apache/tika-docker/pull/4#issuecomment-825372518 While going through the docker-compose samples in the repo I ran into a case or two where running as a non-root user breaks some things. For example, the compose file for

[GitHub] [tika-docker] philipsoutham opened a new pull request #4: Running as non-root user

philipsoutham opened a new pull request #4: URL: https://github.com/apache/tika-docker/pull/4 Adding a configurable UID:GID for the tika process to run as so it doesn't run as root. The following tests still pass after this change. ``` $ ./docker-tool.sh build 1.26 $