This is a feature request: Can we have the on-prem agent run as a service rather then an application. If ever the host is restarted and the application closes, it seems to be quite a pain to get it to start up again in Site24x7. Also for it to work an application has to be running which doesn't seem ideal, especially if the host is being shared with other applications and engineers.
We understand the pain involved in starting the Linux On-Premise poller every time the server is restarted. We have already started working towards making the poller run as a service. You can expect the feature to be out by our next release.
We will update you when the feature gets released.
Happy monitoring.
Dear Johny Jacques,
Meanwhile you can also achieve such functionality (auto starting linux onpremise poller on server restart) by editing the server's crontab using the folllowing command.
crontab -e
Add the following line
@reboot <path_to_linux_onpremise-poller_start_server.sh> &
Hope this finds helpful. Please feel free to contact our support team support@site24x7.com for any assitance. We would be glad to assist you anytime.
Regards,
Krishna.
Question to extend this request....
When we monitor the poller run it spawns a java process that we
can monitor, however, if the poller is restarted for some reason like
during an upgrade then it spawns another instance that will cause the
current one to alert because it does not exist anymore.
Any workaround for that?
currently I am monitoring only the StartServer.sh process
The Java process shows:
Name: java
Path: /opt/Site24x7OnPremisePoller
Arguments:
/opt/Site24x7OnPremisePoller/jre/bin/java
-XX:OnOutOfMemoryError=/opt/Site24x7OnPremisePoller/onOutOfMemory.sh
/opt/Site24x7OnPremisePoller -Xmx512M -cp
/opt/Site24x7OnPremisePoller/lib/jars/EumExtn.jar:/opt/Site24x7OnPremisePoller/lib/servlet-api.jar:/opt/Site24x7OnPremisePoller/webapps/monitoragent/WEB-INF::/opt/Site24x7OnPremisePoller/lib/jars:/opt/Site24x7OnPremisePoller/lib/jars/QEngineWTFramework.jar:/opt/Site24x7OnPremisePoller/lib/jars/AdvCoreLogging.jar:/opt/Site24x7OnPremisePoller/lib/jars/AdventNetFramework.jar:/opt/Site24x7OnPremisePoller/lib/jars/Framework.py:/opt/Site24x7OnPremisePoller/lib/jars/jython.jar:/opt/Site24x7OnPremisePoller/lib/jars/Mail.jar:/opt/Site24x7OnPremisePoller/lib/jars/activation.jar:/opt/Site24x7OnPremisePoller/lib/jars/QEngineTools.jar:/opt/Site24x7OnPremisePoller/lib/jars/QEngineWCT.jar:/opt/Site24x7OnPremisePoller/lib/jars/QEngineWTFramework.jar:/opt/Site24x7OnPremisePoller/lib/jars/commons-beanutils.jar:/opt/Site24x7OnPremisePoller/lib/jars/commons-collections.jar:/opt/Site24x7OnPremisePoller/lib/jars/commons-lang-2.2.jar:/opt/Site24x7OnPremisePoller/lib/jars/commons-logging-1.1.1.jar:/opt/Site24x7OnPremisePoller/lib/jars/ezmorph-0.9.jar:/opt/Site24x7OnPremisePoller/lib/jars/json-lib-2.2.2-jdk15.jar:/opt/Site24x7OnPremisePoller/lib/jars/AdvWmsCommon.jar:/opt/Site24x7OnPremisePoller/lib/jars/json.jar:/opt/Site24x7OnPremisePoller/lib/jars/AdventNetCLI.jar:/opt/Site24x7OnPremisePoller/lib/jars/AdventNetCLIClient.jar:/opt/Site24x7OnPremisePoller/lib/jars/AdventNetJta.jar::/opt/Site24x7OnPremisePoller/lib/jars/httpclient-4.0.jar:/opt/Site24x7OnPremisePoller/lib/jars/httpcore-4.0.1.jar:/opt/Site24x7OnPremisePoller/lib/jars/httpmime-4.0.jar:/opt/Site24x7OnPremisePoller/lib/jars/commons-codec-1.3.jar:/opt/Site24x7OnPremisePoller/lib/jars/bcprov-jdk15on-147.jar:/opt/Site24x7OnPremisePoller/lib/jars/xmlunit-1.6.jar:/opt/Site24x7OnPremisePoller/lib/jars/jsoup-1.9.1.jar
-Dcatalina.home=/opt/Site24x7OnPremisePoller
-Deum.home=/opt/Site24x7OnPremisePoller
-Dtest.dir=/opt/Site24x7OnPremisePoller -Dagent.probe=true
-Dserver.stats=10000 -Dlog.dir=/opt/Site24x7OnPremisePoller
-Ddb.home= -Dcheck.tomcatport=true -Dport.autocheck=true
-Dfile.encoding=utf8 -Djava.awt.headless=true -Djavaagent=true
-Dsecurity.overridePropertiesFile=true
-Djava.security.properties=/opt/Site24x7OnPremisePoller/conf/override_java_security.prop
-Dsun.net.inetaddr.ttl=900 -Dhc=4 -Dprobe.agent=true
-Dagent.allowedips= <bunch of ips removed>.
-Dftp.download.dir=/opt/Site24x7OnPremisePoller
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/opt/Site24x7OnPremisePoller/heapdumps
-Dtraceroutegenerator.port=7777 -Dnetwork.sanity=false
-Duser.timezone=PST -Dtraceroutegenerator.port=7777
-Dnetwork.sanity=false -Duser.timezone=PST
-Dtraceroutegenerator.port=7777 -Dnetwork.sanity=false
-Duser.timezone=PST com.manageengine.eum.agent.startup.Starter
Hi Francisco,
Our apologies for the delay in responding to your post. When the On-premise poller is restarted or upgraded, it kills the existing java process and starts a new java process, because of which an alert might be triggered, as the process arguments are changed.
Recently, we added support for configuring 'Regex' for Arguments in our Process Monitoring, so that even if the arguments change, the new process arguments are matched with the configured Regex and alerts because of changes to arguments could be avoided. In this case, you can edit the monitored Java Process and update the Arguments field as below:
/opt/Site24x7OnPremisePoller/jre/bin/java.*
This will avoid similar alerts, which are triggered when arguments change, in the future. Please let me know if this helps.