When a FireDaemon Pro service is started, two processes are instantiated - firedaemon.exe and the program you are launching under FireDaemon Pro control. Both will be assigned different Process IDs (PIDs). You can obtain the PID of the program you are launching under FiireDaemon Pro control via the FireDaemon Services list in the GUI. Otherwise, you can type the following at an elevated Command Prompt:

tasklist /svc
Generic

The output will look similar to below where the first column lists the program name, the second column the PID and the last column the name of the FireDaemon Pro or Windows service(s) utilising the program.

Image Name                     PID Services
========================= ======== ============================================
System Idle Process              0 N/A
System                           4 N/A
Registry                       148 N/A
smss.exe                       588 N/A
csrss.exe                      828 N/A
wininit.exe                    616 N/A
csrss.exe                      604 N/A
services.exe                   936 N/A
lsass.exe                      960 KeyIso, SamSs, VaultSvc
winlogon.exe                   868 N/A
svchost.exe                   1128 BrokerInfrastructure, DcomLaunch, PlugPlay,
                                   Power, SystemEventsBroker
WUDFHost.exe                  1156 N/A
fontdrvhost.exe               1176 N/A
fontdrvhost.exe               1184 N/A
svchost.exe                   1288 RpcEptMapper, RpcSs
svchost.exe                   1352 LSM
dwm.exe                       1428 N/A
svchost.exe                   1640 EventLog
svchost.exe                   1656 NcbService
svchost.exe                   1664 ProfSvc
svchost.exe                   1672 TimeBrokerSvc
svchost.exe                   1680 Schedule
svchost.exe                   1804 CertPropSvc
svchost.exe                   1824 DisplayEnhancementService
svchost.exe                   1860 UserManager
svchost.exe                   1900 hidserv
svchost.exe                   1960 CoreMessagingRegistrar
svchost.exe                   2000 SCardSvr
svchost.exe                   2040 nsi
svchost.exe                   2164 Dhcp
Generic

FireDaemon Pro services appear in the list as as follows:

FireDaemon.exe                7772 Blackwake
BlackwakeServer.exe          15964 N/A
Generic

If you have FireDaemon Pro debug logging enabled, the firedaemon.exe PID will be logged at the start of the debug log file. For example:

Sat Jan  8 07:42:37 2022 [0x5614]: Service Process:
Sat Jan  8 07:42:37 2022 [0x5614]:   Process Id             : 5304
Sat Jan  8 07:42:37 2022 [0x5614]:   Running as service user: NT AUTHORITY\SYSTEM
Sat Jan  8 07:42:37 2022 [0x5614]:   Privileges of interest:
Sat Jan  8 07:42:37 2022 [0x5614]:     Administrator      : 1
Sat Jan  8 07:42:37 2022 [0x5614]:     SeTcbName          : 1
Sat Jan  8 07:42:37 2022 [0x5614]:     SeShutdownPrivilege: 1
Generic

A little further down in the debug log, you will find the firedaemon.exe PID and program PID are logged when you program is launched. For example:

Sat Jan  8 07:42:37 2022 [0x5614]: Event 1 [0x1]: The service has started with a process id of '5304'.  
Sat Jan  8 07:42:37 2022 [0x5614]: No schedules defined or enabled, subprocess start time point is due immediately.
Sat Jan  8 07:42:38 2022 [0x4734]: Event 17 [0x11]: The subprocess' scheduled start time has arrived.  
Sat Jan  8 07:42:38 2022 [0x4734]: Checking the program to run as a service: OK
Sat Jan  8 07:42:38 2022 [0x4734]: The application manifest requires: elevation=0, uiaccess=0
Sat Jan  8 07:42:38 2022 [0x4734]: Launching 'C:\SteamCMD\blackwake\BlackwakeServer.exe -batchmode -nographics' interactively as NT AUTHORITY\SYSTEM
Sat Jan  8 07:42:38 2022 [0x4734]: Event 18 [0x12]: 'C:\SteamCMD\blackwake\BlackwakeServer.exe -batchmode -nographics' has launched with a process id of 17252 in session 0.  
Sat Jan  8 07:42:38 2022 [0x4734]: Subprocess successfully launched: yes.
Generic