Process in AppManager UI is shown as down while the process is up and running in the machine
Every time a server restarts, the PID of the processes get updated. So the processes added in the monitor will be shown as down. It is recommended that you have static contents alone in the process Commands and Args.
It is also recommended that you remove the dynamic elements in the command and Args field of the process once the process is added for process monitoring so that even if there are any process restarts, they won't get removed.
Note: There is no action to start the process when it is shown as down. Instead it is recommended that you create a script to start the application corresponding to the process which is down and assign it to the processes that you want to monitor (For availability).
New to ADSelfService Plus?
Related Articles
Azure Virtual Machine - FAQ
1. How is data collection happening for Azure Virtual Machine monitors? Microsoft Azure monitor discovery modes in AppManager: AD Application mode Organizational Account mode OAuth mode Azure VM monitor - Data collection methods: Azure Monitor Azure ...
Microsoft Azure VM - Enabling Diagnostics extension for Windows & Linux VMs
Diagnostic Extension is now considered a legacy approach and it is limited to some server distributions. It is recommended to switch to Azure Monitor Agent (AMA). From Applications Manager v171400, Azure monitor agent is supported. Refer here to know ...
Channel status is shown as STOPPED even after the channel is restarted
Below are the behaviours of IBM Websphere MQ and Applications Manager : If a channel is started, the status of the channel is not changed to RUNNING. It will be in INACTIVE state until a connection is made to the channel and a get / put is ...
How can I generate and import certificates into AppManager?
From v14260 : Option to create Certificate Signing Request (CSR) and import SSL certificate to Applications Manager are introduced in UI. Please refer Manage Certificates for detailed steps. Steps for Applications Manager below v14260 : 1. Open the ...
Why am I getting a troubleshoot link for the attributes shown in .NET monitor pages?
Reason: The WMI class is not available or not registered. Solution: 1. Execute the following command, in the remote machine where .NET is running : <wmiadap /f> This will reconstruct and register the WMI classes. 2. In Applications Manager, ...