Turn off metrics

Camunda 7 Topics Discussion & Questions
1

Hi All ,

I am new to using camunda and trying to turn off metrics (Table ACT_RU_METER_LOG).
I added <property name="metricsEnabled">false</property> to bpm-platform.xml file.

    <properties>
      <property name="history">none</property>
      <property name="databaseSchemaUpdate">noop</property>
      <property name="authorizationEnabled">true</property>
      <property name="jobExecutorDeploymentAware">true</property>
      <property name="historyCleanupBatchWindowStartTime">00:01</property>
	  <property name="metricsEnabled">false</property>
    </properties>

I tried to do this in version 7.13 and 7.14 and always got an exception like this:

29-Oct-2020 11:57:04.048 SEVERE [pool-2-thread-2] org.camunda.commons.logging.BaseLogger.logError ENGINE-16004 Exception while closing command context: null
	java.lang.NullPointerException
		at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupSchedulerCmd.reportMetrics(HistoryCleanupSchedulerCmd.java:117)
		at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupSchedulerCmd.execute(HistoryCleanupSchedulerCmd.java:54)
		at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupHandler$1.execute(HistoryCleanupHandler.java:49)
		at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupHandler$1.execute(HistoryCleanupHandler.java:42)
		at org.camunda.bpm.engine.impl.interceptor.CommandExecutorImpl.execute(CommandExecutorImpl.java:28)
		at org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:110)
		at org.camunda.bpm.engine.impl.interceptor.ProcessApplicationContextInterceptor.execute(ProcessApplicationContextInterceptor.java:70)
		at org.camunda.bpm.engine.impl.interceptor.CommandCounterInterceptor.execute(CommandCounterInterceptor.java:35)
		at org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)
		at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupHandler.execute(HistoryCleanupHandler.java:42)
		at org.camunda.bpm.engine.impl.cfg.standalone.StandaloneTransactionContext.fireTransactionEvent(StandaloneTransactionContext.java:84)
		at org.camunda.bpm.engine.impl.cfg.standalone.StandaloneTransactionContext.commit(StandaloneTransactionContext.java:71)
		at org.camunda.bpm.engine.impl.interceptor.CommandContext.close(CommandContext.java:197)
		at org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:119)
		at org.camunda.bpm.engine.impl.interceptor.ProcessApplicationContextInterceptor.execute(ProcessApplicationContextInterceptor.java:70)
		at org.camunda.bpm.engine.impl.interceptor.CommandCounterInterceptor.execute(CommandCounterInterceptor.java:35)
		at org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)
		at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobHelper.executeJob(ExecuteJobHelper.java:57)
		at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobsRunnable.executeJob(ExecuteJobsRunnable.java:110)
		at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobsRunnable.run(ExecuteJobsRunnable.java:71)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
		at java.lang.Thread.run(Thread.java:748)

I would be grateful if anyone in the group has experience in this topic and can provide an answer.

Thanks
Mario

1 Like
2

Can you take a look at the Style Guide? It’ll help you understand how to format code correctly and also help you create questions that are easy to understand and also easier to answer :slight_smile:

3

After adding to bpm-platform.xml file <property name = "historyCleanupmetricsEnabled"> false </property> is ok.

1 Like