# Context parameters in metrics

Metrics are uniquely identified by their name and context fields. Context parameters provide additional information enriching the functional meaning of metrics, depending on the metric category or name.

Some context parameters can be enabled/disabled in the <RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.observability.jobContextConfig.cfg file by setting their values to true or false.

The values in the Example column correspond to the labels used on the example screenshots you can find in the [Context parameter examples](https://help.qlik.com/talend/en-US/remote-engine-user-guide-linux/Cloud/context-parameter-examples) section.

## JMX metric context parameters

The following table presents JMX metric context parametersThe following table presents JMX metric context parameters

| Parameter | Default status | Editable | Example |
| --- | --- | --- | --- |
| area | Enabled | No | heap / noheap |

## Business context parameters

Unless otherwise indicated, the context parameters below apply to all metric parameters in the Business metric categories. All of them are enabled by default and cannot be disabled.

The following table presents business context parametersThe following table presents business context parameters

| Context parameters | Metric category/name | Example |
| --- | --- | --- |
| stacktrace | component\_error | "NullPointer"Exception |
| job\_id | Components, Job | "\_Wbd\_QKHmEeuqob1gixsx-Q" |
| job\_name | Components, Job | - |
| job\_version | Components, Job | - |
| connector\_id | component\_start\_time\_seconds<br><br><br>component\_execution\_duration\_milliseconds | "tMongoDBInput\_2" |
| connector\_label | "tMongoDBInput\_2" |  |
| connector\_type | "tJavaRow" |  |
| connection\_name | component\_connection\_rows\_total | "row1" |
| component\_execution\_duration\_milliseconds |  |  |
| source\_connector\_type | component\_connection\_rows\_total | "tRowGenerator" |
| source\_label | "tRowGenerator\_1" |  |
| target\_connector\_type | "tLogRow" |  |
| target\_id | "tLogRow\_1" |  |
| target\_label | "tLogRow\_1" |  |
| connection\_type | component\_execution\_duration\_milliseconds | "output" |

## Common context parameters

The context parameters below are present by default or can be added to metrics in the following categories:

* Business - Components
* Business - Job
* JMX (Jobs only)

The following context parameters are enabled by default and cannot be disabled.

The following table presents default common context parametersThe following table presents default common context parameters

| Parameter | Details | Example |
| --- | --- | --- |
| account\_id | N/A | N/A |
| operator | User ID or service account ID | N/A |
| operator\_type | Indicates whether the operator is a user or a service account | "HUMAN" for a user or "SERVICE" for a<br>service account |
| deprecated\_id | Temporary solution to distinguish between Job and subjobs metrics (with<br>similar context)<br><br>Information noteNote: Removed from Talend Studio 7.3 R2021-05 patch and Talend Remote Engine v2.10.3 and later versions. | N/A |
| father\_pid | Unique identifier of the first direct parent Job<br><br>Information noteNote: Minimum<br>requirement is Talend Studio 7.3 R2021-02 patch and Talend Remote Engine v2.10.3. | "20210601200408\_aMgz4" |
| pid | Unique Job identifier for the current run<br><br>Information noteNote: Minimum requirement is<br>Talend Studio 7.3 R2021-02 patch and Talend Remote Engine v2.10.3. | <ul> <li>Main (root) Job: <span>"20210601200408_aMgz4"</span> </li> <li>Child Job : <span>"UIvFAe"</span> </li> </ul> |
| process\_id | JVM's UUID | "0fc8c24d-133b-36c7-b917-5e171cc28201" |
| remote\_engine\_id | N/A | N/A |
| remote\_engine\_name | N/A | N/A |
| root\_pid | Unique identifier of the first root Job if there are several<br>subjobs<br><br>Information noteNote: Minimum requirement is Talend Studio 7.3 R2021-02 patch and Talend Remote Engine v2.10.3. | “20210601200408\_aMgz4” |
| source | remote-engine/id or<br>remote-engine/id/task/id/execution/id | /remote-engine/bb733f36-f6ce-4771-8b46-86f7f77539ac/task/5f6cd065c3e872694f45c550/execution/eca2de79-5294-44e6-a573-3b8a6c33db70 |
| step\_execution\_id | Applicable for plans only | N/A |
| task\_execution\_id | N/A | N/A |
| task\_id | N/A | N/A |
| thread\_id | One of the JVM's thread UUID | "40bd2dfa-47cd-4856-a96e-9784aa93a531" |
| workspace\_id | N/A | N/A |

The following context parameters are disabled by default, but can be enabled if needed.

* artifact\_version
* artifact\_name
* cluster\_id
* cluster\_name
* compatibility\_version (Talend Studio compatibility)
* environment\_id
* environment\_name
* environment\_version
* plan\_execution\_id
* plan\_id
* plan\_name
* plan\_step\_id
* plan\_step\_name
* run\_type
* task\_name
* task\_version
* trigger\_timestamp
* workspace\_name

### In this section

* [Context parameter examples](https://help.qlik.com/talend/en-US/remote-engine-user-guide-linux/Cloud/context-parameter-examples)