OverOps features administrative functions for On-Premises environments to be carried out from the Command Line Interface.
- Command Line Arguments for On-Premises (Docker) Servers
- Command Line Arguments for On-Premises Servers
This section details the locations of the logs that can be associated with the On-Premises deployment.
All logs, by default, are written to
/opt/takipi-server/log/tomcat/, where you'll find multiple log files:
aws.log cache.log catalina.log (also includes netty and quartz logs) code-analysis.log pds.log push.log queue.log rdbms.log redis.log service-analytics.log storage.log tale-fail.log tomcat/catalina.log tomcat-access.log tomcat-server.log user-analytics.log
By default the only active logs are the following:
tomcat-access.log tomcat-server.log catalina.log (also includes netty and quartz logs)
When OverOps is deployed on-premises, the OverOps implementation cannot be monitored, so you'll need to follow the guidelines in this Best Practice guide to learn how to monitor the deployment's health.
Updated over 2 years ago