Skip to main content Skip to complementary content

Collecting OSGi metrics

When an artifact is deployed, every metric from its execution is collected in Talend Remote Engine and accessible from the GUI.

Before you begin

You must provide the metric_path context parameter in your data service or Route design in Talend Studio, and provide a value for it in Talend Management Console when deploying the task. The value of the metric_path parameter is used to look up the MBean of the data service or Route.

Use the name of the Route or data service as the value of the metric_path parameter.

About this task

For data services, the following metrics are captured:
  • OneMinuteRate
  • FiveMinuteRate
  • FifteenMinute
  • Count
For Routes, the following metrics are captured:
  • Context_ExchangesCompleted
  • Context_ExchangesFailed
  • Context_ExchangesTotal
  • Context_MeanProcessingTime
  • Context_LastProcessingTime

Metric collection is enabled by default. When the Remote Engine is restarted, metric collection starts again automatically. However, the metric values above, for example, Count for Service Calls or Context_ExchangesTotal, will be 0, as the JMX metric represents the number since the last start operation, not the total number over time.


  • To configure the JMX connection to Talend Runtime, edit the org.talend.ipaas.rt.dsrunner.talendruntime.client.cfg file in the <RemoteEngineInstallationDirectory>/etc folder.
  • To change the polling interval (in seconds), edit the metric.collection.interval property in the org.talend.ipaas.rt.dsrunner.metrics.collector.cfg file.
    Values of the metric.collection.interval property
    Value Description
    60 Default value.
    0 The metric collection is disabled.
    10 Minimum value.
    900 Maximum value.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!