# How to find the Token for Remote Capture?

This post is intended to explain the 'Token' field in the 'Remote Capture' feature. 'Remote Capture' feature facilitates you to capture the troubleshooting artifacts (i.e., GC log, thread dump, heap dump, netstat, ...) of a specific process on a remote device. On a device, multiple processes will be running. 'Token' field is used to uniquely identify a particular process on the device.

You can pass one of the following values to the 'Token' field, to uniquely identify a process:

  1. Process ID

  2. Unique argument of the process

  3. PROCESS_HIGH_CPU

  4. PROCESS_HIGH_MEMORY

  5. PROCESS_UNKNOWN

Let's review these options.

# 1. Process ID

Operating systems assign a unique Process Id to each process. If you know the Process Id of the target process, then you can specify it in the 'Token' field. Say if the process Id of the target process on which you want to capture the troubleshooting artifacts is '6132', then you can pass the following value in the 'Token' field: 6132.

However, if you don't have SSH access to the remote device in which this process is running, it might be tricky to identify the Process ID. In that circumstance, this option will not work for you. If you have SSH access to the device and still not sure how to find the process id, then refer to How to identify process? (opens new window).

# 2. Unique Argument of the process

You can pass a unique argument with which the target process is launched. For more information, visit What is Unique Token in Process? page.

# 3. PROCESS_HIGH_CPU

Suppose you want to capture troubleshooting artifacts on a process that is consuming the highest CPU, then you pass 'PROCESS_HIGH_CPU' to the 'Token' field. When you pass this pre-defined token, yc-360 script will find the highest CPU-consuming process and trigger the capturing on it.

# 4. PROCESS_HIGH_MEMORY

Suppose you want to capture troubleshooting artifacts on a process that is consuming the highest memory, then you pass 'PROCESS_HIGH_MEMORY' to the 'Token' field. When you pass this pre-defined token, yc-360 script will find the highest memory-consuming process and trigger the capturing on it.

# 5. PROCESS_UNKNOWN

There is another pre-defined token 'PROCESS_UNKNOWN'. When you pass this token, yc-360 script will find the highest memory-consuming process and highest CPU-consuming process. It will trigger capturing on both processes. When you pass this token, you will end up getting two root cause analysis reports in the dashboard, one for the highest CPU consuming process, other for the highest memory consuming process.

← Why GC Report Was Not Generated? →