Sweagle log filesIn order to monitor the proper functioning of the Sweagle platform, it is recommended to have a continuous log collection and monitoring in place. There is a myriad of tools available (both opensource and commercial) to collect logs, monitor, visualize, and alert. There is no specific requirement from the Sweagle point of view, so any log management platform is fine. As a suggestion, Sweagle provides information on how to use the Elastic stack (ELK) for collecting logs on the Sweagle components and providing monitoring and reporting - both for issues as well as overall usage of the Sweagle platform. See KB0854264 - Monitoring and log analytics for more information on using the ELK stack. Sweagle application components On a standard installation of Sweagle, all logs for each of the components are stored in /opt/SWEAGLE/logs. There is a rotating log for each of the components. The naming convention is the name of the Sweagle service name with a .log extension. Sweagle recommends using a log collection tool to centralize the log files for analysis and troubleshooting. Technology components NGINX (web server) We recommend monitoring the web server log files. If you use NGINX, the main log files to monitor are located in the /var/log/nginx folder (in case of default installation). ElasticSearch On a default installation of elasticSearch, logs are written to the /var/log/elasticsearch folder. there is a rotating log file which has the ElasticSearch cluster name. On a default installation, this is SWEAGLE_cluster.log MongoDB On a default installation of MongoDB, logs are written to the /var/log/mongodb folder. There is a rotating log file named mongodb.log. MySQL On a default installation of MySQL, logs are written to the /var/log/mysql folder. There is a rotating log file named error.log.