Talend Studio version 7.3 R2020-07 or later is installed but not running.
Talend Remote Engine
version 2.9.2 is created, installed, and paired in your Talend Cloud Management Console
account.
Procedure
Open the
<RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.observability.cfg
file to edit it.
Enable the following parameters by setting their value to
true:
omc.enabled=true
omc.re.enabled=true
omc.jobs.enabled=true
omc.oshi.enabled=true
omc.apm.enabled=true
omc.prometheus.enabled=true (for a Prometheus format)
omc.rest.enabled=true (for a JSON format)
Set the omc.push.frequency_ms parameter to the desired
value.
The push frequency parameter defines the frequency at which Remote Engine
components produce their metrics. Increase its value to send metrics to the APM less
often, or decrease its value for more precise monitoring.
Save the file.
Open the
<RemoteEngineInstallationDirectory>/etc/org.talend.observability.omc.cache.apm.cfg
file to edit it.
Set the timeToLiveMinMilliseconds parameter to the desired
value (in milliseconds).
The time to live limit of the metrics in the Observability Metrics Collector is
based on the push frequency.
The default value is 1000.
Increasing this value increases the time the metrics are available for, though it
must always be higher than the push frequency.
If needed, set the timeToLiveMargin to ensure there are no
gaps when a component encounters an unexpected error or lag.
The default parameter value, 5 milliseconds, can be edited
but it is recommended not to edit it for security reasons.
Save the file.
Optional: You can also activate contextual information about the Jobs in the
<RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.observability.jobContextConfig.cfg
file by setting parameters to true.
To validate that the monitoring feature is enabled,
enter bundle:list in the console. All Observability
Metrics Collector entries must be in Active
status.