Skip to main content Skip to complementary content

Collecting microservice metrics

When an artifact is deployed, a limited set of metric data from its execution is collected in Talend Remote Engine - Data Service Runner and accessible in Talend Management Console.

Before you begin

You must provide the metric_path context parameter as part of your task definition in Talend Management Console, and provide a value for it in when deploying the task. The value of the metric_path parameter is used to look up the JMX-MBean/Jolokia URL of the data service or Route specific metric.

Use the name of the REST data service artifact as the value of the metric_path parameter. For microservice Routes, this parameter is optional, but it is recommended to set within each data service and Route task you want to collect and view metric data for in Talend Management Console.

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 start 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.

Procedure

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 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 – please let us know!

Leave your feedback here