General FAQs

General FAQs

While adding the Web Transaction Monitor I get the message 'Service is not running. Web Transaction Agent may not have been deployed’. This happens even when I have deployed the agent in my application server.

Check if the Web Transaction Agent is deployed correctly in the application server. Look for the message 'Problem while starting the agent web server' in the startup logs of the applications server. If this message is present it means that there was a problem in deploying the web transaction agent. The exception should provide the exact root cause of the issue.

The web transaction agent, by default, starts on port 55555. Check if this port is preoccupied. Refer the help for changing the default port.

The Web Transaction Monitor gets added successfully but in the details page I get the message 'No transaction data available'.
This is because no URLs were executed in the application server after deploying the web transaction agent. Execute few URLs in the application server and check if they appear in the details page.

Though there are repeated executions of URLs in the application server I don't find the data being updated in the Applications Manager client.
The Web Transaction agent uses a configuration parameter called 'Sampling Factor' to collect the metrics. By default this parameter is configured as 100. This means that for every 100 executions of an URL only one statistic is collected in the agent. Refer Help for more details on configuring sampling factor.
Also the agent does not maintain the history of the URLs executed. Only the latest execution of an URL gets stored in the agent.
          • Related Articles

          • RBM - FAQs

            1. I am unable to create a new RBM monitor. Go to  the Support tab and check the license Information. Verify if "EUM Add-on" option is enabled. If it is not enabled, contact sales@manageengine.com to purchase/trial the Add-on since RBM requires the ...
          • Nginx FAQs

            1. Errors faced while adding an Nginx server :  Unable to connect to the host / port :  This happens when AppManager is unable to connect to the Nginx server. Please check for the following : Are the specified host name and port correct?  Is the ...
          • AWS EKS Troubleshooting FAQs

            AWS EKS monitor can be configured only if you have already added an Amazon monitor in Applications Manager. Ensure that you have met the pre-requisites for the Amazon monitor before monitoring Elastic Kubernetes Service in Applications Manager. How ...
          • AWS Monitor Addition - FAQs

            During monitor addition :  Provide proper 'Display name' for the Amazon monitor. Select the 'Amazon Services'  you wish to discover in the drop box. By default, all the services will be selected. Currently as in version 15250, we support EC2, ...
          • General errors that occur during backup

            Here are some general errors that occur during backup and how to fix them: Error 1: “Initializing backup process" pg_dump: [archiver (db)] connection to database "amdb" failed: FATAL: no pg_hba .conf entry for host "::1", user "postgres", database ...